Earlier quoted context omitted.
I went the whole nine yards on that project. I had white (black font) for my own machine, green for development, blue for integration test, yellow for system test, and red for production. I liked the green / white text theme the most with blue being my second favorite to write code in so those got the ones I would use the most. I was never a lover of the old amber terminals and red is just plain painful to write on.…
Was it automated? If so, how?
The tech world is rallying around a young developer who made a huge mistake
41–50 of 62 posts
Re: The tech world is rallying around a young developer who made a huge mistake
#42This article clearly missed the point. He didn't make a huge mistake, he made a very tiny one. The company/CTO made the huge mistakes.
Re: The tech world is rallying around a young developer who made a huge mistake
#43Did anyone ever confirm it wasn't a hoax? Or find the actual company?
I mean, wasn't the crux of this story a plot point in Silicon Valley? Either its a hoax or Silicon Valley is truly uncannily realistic.
Silicon Valley and Veep are both disturbingly prescient.
Re: The tech world is rallying around a young developer who made a huge mistake
#44Did anyone ever confirm it wasn't a hoax? Or find the actual company?
I mean, wasn't the crux of this story a plot point in Silicon Valley? Either its a hoax or Silicon Valley is truly uncannily realistic.
A rule of thumb is that the really ridiculous stuff in Silicon Valley like the "three commas" or the "blood boy", actually happened.
Re: The tech world is rallying around a young developer who made a huge mistake
#45When I'm fully in control I engineer things in a way that make disasters unlikely and easily recoverable. But that is not always possible. I tend to avoid touching any production DB but again that is not always possible.
I always believed I have a developer mindset more than an operational mindset and worked more in roles compatible with the former than the larger. When looking at the devops culture I always wonder whether the lessons of strict control of production environments are getting enough attention. There is value is closing the gap between the two world but please leave a gap.
Re: The tech world is rallying around a young developer who made a huge mistake
#46This article clearly missed the point. He didn't make a huge mistake, he made a very tiny one. The company/CTO made the huge mistakes.
A old supervisor of mine told me that "You treat a new developer like a duckling near a pond with Northern Pike". There is no way you let them have access to production (or frankly, anything past a development environment) until they have been there a while and gotten the hang of it. On a tangent, I was paranoid enough in one position to have all my production terminal windows have a red background with yellow text.…
I had a job where we would often sudo as other users and ssh into other boxes. I kept trying and trying to find a way to change the terminal when sudoed as someone else because occasionally I would execute something in the first terminal I could grab. At the time I couldn't find anything or think of a way.
Re: The tech world is rallying around a young developer who made a huge mistake
#47Unrelated to the story, but I've had a similar experience as to some of the stories described in the article - where a cascade of unseen problems landed on my lap and I took the blame even though little of it was my doing. (Note, this was many years ago and mildly traumatic, so some details might be fuzzy) In 2001 I was working for one of the larger internet server co-location companies in the US as a dedicated custo…
I really don't want you to think I'm criticizing your actions - you were a true hero to the customer in a crazy situation. I think its truly unfortunate that they terminated you for this. Best of luck!
Re: The tech world is rallying around a young developer who made a huge mistake
#48Unrelated to the story, but I've had a similar experience as to some of the stories described in the article - where a cascade of unseen problems landed on my lap and I took the blame even though little of it was my doing. (Note, this was many years ago and mildly traumatic, so some details might be fuzzy) In 2001 I was working for one of the larger internet server co-location companies in the US as a dedicated custo…
Wow, incredible story. I used to be a Sun SSE, so I can feel for you. I know hindsight is 20/20, but this was my approach when replacing failed hardware like memory DIMMs remotely (when the client wasn't there in the datacenter): - I always asked them to do a full shutdown,"init 5", and would wait until the server physically powered off before working. That would verify I was on the right server. If the server didn't…
Re: The tech world is rallying around a young developer who made a huge mistake
#49Earlier quoted context omitted.
That's not paranoid! That's a fantastic thing to do and one that I highly recommend for anyone. It's terribly easy to forget which environment you're working in when you get distracted for a moment and that's how mistakes happen.
I went the whole nine yards on that project. I had white (black font) for my own machine, green for development, blue for integration test, yellow for system test, and red for production. I liked the green / white text theme the most with blue being my second favorite to write code in so those got the ones I would use the most. I was never a lover of the old amber terminals and red is just plain painful to write on.…
[0] https://biology.stackexchange.com/questions/3871/which-shade...