|
. . . or my women.
I'll teach and share the code - but (and only partially in jest) - thinking and planning is private and intimate. There's a degree of potentiality that cannot be performed with an audience, let alone a critique.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
COVID procedures would require sterilizing the keyboard anytime a different person typed. Too much time wasting. (Even for a virtual swap)
|
|
|
|
|
Even outside of the COVID realm, there are some things you just don't want to share.
Let's just say I don't want anyone else to have sprayed my territory and leave it at that
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I hate big teams.
I hate pair-programming as a rule.
I prefer working solo on a small team. I still like to collaborate and bounce ideas off of other devs, etc.
Big teams, IMHO, have proven to be highly ineffective.
|
|
|
|
|
Similar preferences here.
I prefer smaller, simpler projects and coding on my own, less toes to trample on. With a recent and current project I'm definitely glad to have had someone else on the project, I wouldn't have been able to finish it on my own within time. We work on separate features though in a full stack manner (from db through to ui).
|
|
|
|
|
I love coding solo, but sometimes I just really miss a sparring partner.
Especially one that's smarter than me (they'd have to be really smart ).
I think coding in (small) groups can make everyone better as you can learn from each other.
On the other hand, most groups tend to have at least one toxic person.
If the group has toxic people then I prefer solo all the way.
Nothing's worse than toxic people on the team
Also, if there's a huge gap in knowledge between team members, and I'm not talking about a junior who's there to help and learn, but "equal" members of the team, things can get rather frustrating as well
Or when team members have completely different views on coding and/or process (best) practices.
Or when... You know what, people suck, I'll stay solo!
|
|
|
|
|
The Internet (StackOverflow) is really all we need.
You need an answer you go look it up and get the answer.
If you don't like a particular answer you move on to the next post.
IRL the person giving the answer begins feeling like they own you or something so I'll just check StackOverflow and go solo.
|
|
|
|
|
I have an outstanding C++ question on stack overflow. Been that way for days.
Of course I ran into this issue in meatspace too. Sometimes good questions simply have no answers.
Real programmers use butterflies
|
|
|
|
|
I agree with pretty much all of this. Except for the smart part. Even idiots can code with me, I'm pretty dim, but I'm good at magic.
Real programmers use butterflies
|
|
|
|
|
I don't consider myself an idiot and even I can't follow half of what you say (especially the parts that aren't about code)
|
|
|
|
|
That would be the magic. Some people call it crazy.
Real programmers use butterflies
|
|
|
|
|
But there are times (less so for me these days though) when "buddy programming" or whatever you want to call it, has helped us steam through some work - plus the benefits of peer-review on the fly.
I've also been put into the position of being "forced" to double-up when it was inappropriate - don't you just love it when management get hold of new ideas
Just as one programming language is not "the best" for all scenarios, one technique is not the best either. But there is a worst - "coding as a team"? You'll never sell me that one.
|
|
|
|
|
CHill60 wrote: "buddy programming" or whatever you want to call it
about 15 years ago, they called it "extreme coding". I don't know how it got that name.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
same reason nerds like to call it DevOps. Sounds cool like SpecOps.
|
|
|
|
|
Because it invoked extreme responses from those of us unfortunate to have to do it?
|
|
|
|
|
I had to do it once.
My boss decided it would be a good thing to try out, so he sat with me while i was coding. Every 20 minutes or so, he'd ask if i wanted to compile, and i told him, "not yet".
After almost 4 hours, and 1000 lines of code, I said, "Okay, I'm ready".
Not only did it compile, but it ran with a couple of minor issues the first time.
He threw up his hands and said it was the most impressive thing he'd ever seen, and left my office. I was never saddled with extreme programming again.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
CHill60 wrote: don't you just love it when management get hold of new ideas You made me realize something with that statement at this time. Not that it's a new idea to most of us but sometimes it just clicks.
Until now, I never realized the perks of being amongst the programmers of a business who's product is not software. Aside from one jerk of a director (who's since been fired) that told me I must code a project in Visual FoxPro, no one ever tells me anything more than what they want something to do when the dust settles. I've gotten enough of a reputation that even some pretty big management will accept a "No" from me on things - at least to the point of listening to why I say that something is a bad way to do something - particularly when they understood that it's easier for me to code it then to argue against it: that I really mean there's a problem and I'd rather do it right the first time.
Although there are project managers dripping from the walls, no one bothers us in our little world of coding.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos, GHB wrote: no one bothers us in our little world of coding. I am so jealous right now
|
|
|
|
|
I can make you feel better (and me, worse):
I have near total autonomy at this point - BUT I'm seriously underpaid. The extreme autonomy is what they gave me when I demanded a raise. I was going to walk, but my (real) boss (who doesn't have any power of the pay checks) pointed out that they pretty much gave me the Golden Ticket (as in Willy Wonka). He's been a real solid colleague and I'm staying around pretty much for him.
At this point, between pensions, SSA, interest and dividends, I make more money as so called "unearned income" then from work. I could turn my back, phart, and slam the door as I leave.
Meanwhile, although I code alone I'm a very willing teacher. My heir-apparent, unfortunately, had been kept too busy by the mighty managers to even come once/week for lessons and insight on what he's going to work with when he replaces me - at this point there's no-one. The code, as it is, will run and cover their needs for year - but no one to cover.
So - I have autonomy, but not much of a paycheck (we're talking a shortfall of something like US$25-30K/yr). Obviously, since I'm still here, I value the autonomy and a good 'boss' more than the money and am blessed to be able to afford to do so.
It'd make a good survey - "how much money is it worth to you to be how autonomous?"
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I had a situation like that 8 years ago.
Then the team started to get disbanded, the new co-workers were way less in my wave. My boss knew what he had with me, but I got the impression of getting stuck and...
when I decided to move in with my girlfriend into another city... I started to search. 90 Km one way conmute everyday was not for me.
Now I miss some things from back then, but my live quality is much better now.
Before I was 80% of the time on the way, now I have slept two nights in a hotel in 26 months.
Before I was doing 10 to 12 hours a day, I now make 7 to 8,5 hours
I get paid more, I don't have to travel, I have more free time to be with my family in my daily routine...
But on the other hand... burocracy and big OEM PITA in some things have come over to stay. At least what I have to do is mostly fun and the other programmer is in the same wave as me.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: when I decided to move in with my girlfriend and
Nelek wrote: my live quality is much better now.
Ah ha. Ah ha. Ah ha.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
Coding is 20% of the job, rarely more. I am a professional, usually more experienced in coding than my coworkers, so I prefer going solo.
For the remaining part of the job? Teamworking whenever possible. Design, testing, validation, troubleshooting, patch planning are best done in a team.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
+1
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|