451–460 of 668 posts
It sucks being that person today because everything is about optics and that person will get purged. I know from experience. Team players, mentors, software architects; they tend to be tossed aside to make room for coders who can churn out large amounts of code, even as the company's capacity to deliver and maintain features declines over time due to tech debt. Managers always love a developer who can consistently wr…
Earlier quoted context omitted.
must’ve been Tommy’s first rodeo lol
And how would an experienced cowboy handle this situation?
Then leave, become an outside contractor and you can be the benefactor.
Save exceptional work for small companies that will reward it or your own startup.
Earlier quoted context omitted.
must’ve been Tommy’s first rodeo lol
And how would an experienced cowboy handle this situation?
2. Start a consultancy company and overcharge clients to do this work.
3. Realize that many companies will not reward you for your efforts as you expect and go back to 1
Reminds me of an anecdote about Bell Labs. Someone calculated who the most productive employees were (based on things like patents received), and found that many of them would eat lunch with the same person. That person wasn't individually very productive, but he would always ask thoughtful, compelling questions that in turn made his coworkers measurably more productive.
It might be from the great book The Idea Factory by Jon Gertner (p 135). 'In the midst of Shannon’s career, some lawyers in the patent department at Bell Labs decided to study whether there was an organizing principle that could explain why certain individuals at the Labs were more productive than others. They discerned only one common thread: Workers with the most patents often shared lunch or breakfast with a Bell…
I always remember as “questions are harder than answers”.
I wish I could pair program more. I have so much knowledge to give other members of my team. Domain knowledge, programming knowledge, common pitfalls, etc. You get a code review pass at the time of writing the code, and it means you have more opportunity to change things for the better. Once it's written there's not much appetite for drastically changing working code during code review unless there's a really good re…
Pair programming sounds so stressful and unproductive to me. You can't read someone's mind. Any interjections while someone is in the middle of coding can't be more than distracting noise most of the time. And I would constantly feel self conscious that I'm taking too long to write something, googling or asking Copilot stupid questions, etc. Reviewing after the programmer believes it's ready to review makes much more…
Copilot is as much a pair programmer as stack overflow is... So not at all
I was assigned to help team members on the lowest rungs of "performance" metrics. My stats went to shit.
Some teammates smashed it, others didn't. My influence and pay increased and nothing felt right.
Ended up leaving the best org of the company because I couldn't (at the time) understand what was happening.
IMO, looking back, as amazing and 'right' as this scenario feels (OP and myself), it needs the full support of the entire company to make it work.
It sucks being that person today because everything is about optics and that person will get purged. I know from experience. Team players, mentors, software architects; they tend to be tossed aside to make room for coders who can churn out large amounts of code, even as the company's capacity to deliver and maintain features declines over time due to tech debt. Managers always love a developer who can consistently wr…
Earlier quoted context omitted.
Yes, that is what was written. Would you like to say something about it?
[flagged]
[flagged]