211–220 of 270 posts
Earlier quoted context omitted.
You drink 5L of water a day? (assuming 180lbs, 28ml Oz that's 5.04L)
No no, so it's half your weight in lbs, in oz. So for a 200lb man, it'd be 100oz. Just under a gallon. It seems like a lot at first, and for the first few days I peed a lot, but now it seems normal. Granted, I'm doing myself a small service by saying 200, but that's just a few covid pounds.
Earlier quoted context omitted.
This works up util a point. If the code is owned by 4-30 people, its good. If the code is owned by 120 people, then it takes way to long to tell what the quality standard is. > The standard you scroll past is the standard you accept. The challenge is how to get work done without spending 60 hours a week pointing out or solving code quality problems. To overcome this challenge requires accepting some standard of crapp…
I think it is worth it in the lo g run. In best case your team grows and the original hurdles are fixed. It's always problematic for bad colleges which just do the same mistakes over and over and over again but what do you wanna do? Accept a potential security bug because it is too much effort? If your code is so complex or big that you have 120 people on it, you should have enough people in governance positions and…
Yes. It is important to have the serenity to accept the things you cannot change.
In the choice between
A. Burning out on a fool’s errand of attempting to fix/prevent all the security bugs.
B. Giving up as you accept that people write security security bugs and as an individual contributor you have insufficient power to stop all of them.
C. Accepting the existence of bugs all around you and focusing on changing the small bits of code that you can.
The latter is preferable.
I think when I try to objectively look back at my career, I was at times the best colleague, and at other times the worst colleague. I regret looking back at my worst moments.
Best: Decisions don't get made in meetings. Tailor your communication to your audience. Be diligent and ethically consistent and people will respect you for it. Worst: Stay in your lane.
Decisions get agreed upon in meetings. The actual decisions have been made in the days, weeks, sometimes months leading up to the meeting. And the amount of human input going into them can vary from very little to gargantuan. I believe there is even a saying that before an important meeting takes place the people required to attend it will hold one or more unofficial meetings to make up their minds about the topics o…
Earlier quoted context omitted.
Please don't play it emotionally and report it to HR. Folks from HR are there to take care of the manager and employer. Such a step could be suicidal.
That is such a bullshit meme that needs to die. HR's exact goals vary between companies, but unless the company culture is toxic all the way to the top, part of their job is usually to reduce staff turnover (which is very expensive for the company), and in pretty much any company their job is to protect the company against lawsuits. Abusive managers are not well liked by HR.
Best: tactical diplomacy can be learned and is very valuable Worst: The people who talk about others will talk about you
From good colleagues - Be someone that improves your environment whatever you're put into - code, team dynamics, communication whatever. - Be relentless in pursuing something that you're convinced is worthwhile. Things and times change. If you feel something is good for you and the org, do it. Don't waste time "thinking". - Orgs have reputation inflation. If you're the same as you were last year/month/week, you've ac…
Good managers are largely similar, but bad managers are each bad in their own way (with apologies to Tolstoy). From my good managers I have learnt the value of shielding working employees from excessive meetings and bureaucracy, and trusting people to work out their own solutions while assiting and supporting them. However, I have learnt so much more (direcly and indirectly) from my bad managers. A couple of examples…
From my worst colleague: This man thought things were funny, and they weren't. I bicycle commuted to work, and he thought it funny to buzz me, passing just a few inches away from me, doing about 60mph on his street motorcycle. Another time, I was a bit stressed and needed some downtime so on my way out of the office, I said as much and added "so don't call me unless something is on fire." So, he called me, on my lunc…
Vindication is morally questionable, but someone could be tempted to it to attach consequence to the offending behavior. After deciding not to take the low road, how did you handle these situations in the future?