Regrets as a programmer: 1. Every piece of unpolished, unfinished code that management decided should ship to the customers regardless 2. Ever using node and npm. 3. Seeing and living through the train wreck of J2EE and the XML horrors that ensued. 4. Not seeing the beauty in simple functions early on. Not everything needs to be a class or module. 5. Most business problems are political/social - regret every time we…
My Biggest Regret as a Programmer
501–510 of 634 posts
Re: My Biggest Regret as a Programmer
#502Earlier quoted context omitted.
This is pretty ridiculous. Lawyers, Bankers, and Doctors get to play in intellectual sandboxes, and they get paid really handsomely for it, even if they are completely anti-social people. The reason we get paid less is that we don't have any of their safeguards: - Lawyers aim to become partner. It's very socialist-y this way. The goal working in a firm is to become an owner of the firm and share in its successes. - D…
Yep, this leads me to my biggest regret as a programmer: going into engineering instead of medicine. I really should have become a doctor or some other kind of hospital worker instead: the money would have been at least as good, and I would have gotten to work in a place with lots of women.
Re: My Biggest Regret as a Programmer
#503Earlier quoted context omitted.
I'm in my late forties and have been a professional developer for 25+ years. I agree with what you said in your comment, but this stood out: "You might be dead tomorrow; you might as well enjoy today." This is not a bad way to live, but as I get older I am increasingly aware that there will be a day when I'm dead tomorrow. And for that reason I'm increasingly less interested in spending time in the state where "time…
I'm about the same age as you. The passage of time is shockingly fast unless I do things to slow it down. I remember moments from my college days that I can pinpoint to the year they happened. That thing that happened sophomore year? I know it happened sophomore year because I did it with my roommate at the time. But nowadays I'll watch a movie on Netflix thinking it came out just in the past year or two, only to dis…
Re: My Biggest Regret as a Programmer
#504He would have been unhappy with the other choice as well, because then it is the programming side he would be missing out on. I would advise everyone to read The Road Not Taken by Robert Frost. http://www.poetryfoundation.org/poem/173536 You chose one option out of many, and the others may no longer be a possibility. However, the writer's unhappiness does not spawn from his inability to be successful at what he does,…
> I just have to say this: So typically american. The attitude presented in the article is indeed typically American -- but not for the reason I think you intended. The quintessential American quality is the belief that every person has the right to control their own destiny. Fuck, it's right there in the first sentence of the first document declaring this country's independence. Americans are often seen as greedy re…
... and then took nearly a century to getting around to the idea of not owning people. There are a lot of caveats to that American belief.
Re: My Biggest Regret as a Programmer
#505Earlier quoted context omitted.
> No integers. Fair enough. > Assignment is declaration. Not exactly. You can declare variables separately, if you want. In fact, a "var x = 42" statement will actually be split into "var x;" at the top of the scope and "x = 42" wherever you actually wrote it by the interpreter. The specified behaviour is a little weird and non-obvious, but once you know it, you know it. > Prototypes. That's a matter of taste (plus t…
> and of course we have class syntax now anyway Even using Class syntax you're still locked into prototypical inheritance model. There is no classical inheritance in JS. (Probably a backward step in UX to call it "Class")
Re: My Biggest Regret as a Programmer
#506My friend has gone from engineer to product manager, marketing manager and in "business development" now. He has tried to explain to me what the latter two jobs entail (I understand product manager), but I just do not get what it is he does all day. He hates his job, but really really gets off on how successful society says he is (between management title and salary) such that it seems to compensate for the daily misery.
I am, however, waiting for the day he becomes a CEO and I can be his admin assistant or some other low-key, lower-stress helper (we are still good friends). Beyond a good salary, I really don't care about status or title. I think I would be happier as a janitor if it paid 120K+.
TLDR: Different strokes for different folks.
Re: My Biggest Regret as a Programmer
#507Regrets as a programmer: 1. Every piece of unpolished, unfinished code that management decided should ship to the customers regardless 2. Ever using node and npm. 3. Seeing and living through the train wreck of J2EE and the XML horrors that ensued. 4. Not seeing the beauty in simple functions early on. Not everything needs to be a class or module. 5. Most business problems are political/social - regret every time we…
Can't believe this comment made it to the top.
Re: My Biggest Regret as a Programmer
#508I faced this same decision (for very similar reasons) about 15 years ago, and decided to go the management track (I'd been a back-seat manager before that too). I enjoyed helping "underlings" succeed, was well-respected (not always popular) by those people I managed, had some good mentors, and had some good success moving up the ladder. I was reluctantly getting used to the fact that I spent most of my time in meetin…
How do you recognize these types of good companies?
The executives do things that directly make money (e.g CTO still codes, CEO still closes deals), even as the company grows (and tend to outsource/offload things that would normally give them more power, but don't contribute to the bottom line). Coders probably work directly with Support and Sales staff and sometimes customers to understand customer problems. On the higher end of revenue/employee and productivity/employee ratio. Company is probably frugal, spending money on things that actually make the company successful, not just look/feel successful.
The company will behave like its small even as it gets bigger. More focused on getting to profitability without raising more money, than on "higher" rounds of funding. Will probably live by "something decent that works now is better than perfect in the future". They will probably be using a boring technology stack because they can't afforce to waste time proving out newfangled stuff (that customers usually don't care about anyways, and certainly won't pay for).
If you think you've found such a company, compare them to the characteristics in "Getting Real" by 37Signals[1], it captures a lot of things that I've seen in these companies. If they even get close to hitting 1/2 of those, good chance it's such a company.
Re: My Biggest Regret as a Programmer
#509Regrets as a programmer: 1. Every piece of unpolished, unfinished code that management decided should ship to the customers regardless 2. Ever using node and npm. 3. Seeing and living through the train wreck of J2EE and the XML horrors that ensued. 4. Not seeing the beauty in simple functions early on. Not everything needs to be a class or module. 5. Most business problems are political/social - regret every time we…
Granted, in a decade, if you'll still be in this profession, you'll remember J2EE and XML and Node and npm and pip and git and Golang and JavaScript and code polish and functions-vs-methods debate as tiny specks on what actually constitutes you career. The author of the linked article tries analyzing his entire life from a standpoint of being a programmer, and your comment analyzes last few years of your life staring…
Re: My Biggest Regret as a Programmer
#510Earlier quoted context omitted.
Depends on how you define success and failure. I've had 7 failed startups (#8 is in the process of failing at the moment). I consider them all failures because I didn't end up with FU money. Funny thing is startup 6 & 7 really got me close. Although, even if I won a billion dollar lottery, I'd still move on to startup #9. Half the fun is in the building anyway :-)
Agree that fun is in building the companies. But how long can you afford keep doing it (assuming you have family/commitment)? Success is what i call, you can keep doing what you like, not dependent on money, etc - iow, financial independence. BTW, would be interesting to know the geographies of people who comment in this thread - say SF Bay Area, TX, MA, etc. That really adds new perspective to this discussion. My 2c…
You make choices in life and there are tradeoffs. I don't have kids nor do I anticipate having any. If they come, so be it. I partially left the Bay Area because I couldn't see even raising a hypothetical family there. That, the sticker shock never completely wore off and I never donned my rose colored glasses either :-)
I can afford to do it until the day I die. I've set myself up rather nicely in that regard. I'd be retired already if it weren't for my startups & first marriage. But being retired in your mid 30s sounds boring as well (I'm in my 40s now). However, I waffle on that position, so take it with a grain of salt.