81–90 of 634 posts
Earlier quoted context omitted.
10X the assets => retire 10 times sooner => program when you're retired => no missing out
When one retires, there are lots of more interesting things to do with your life than spending the remaining days of your life in front of a computer screen.
Management has always politics involved. And politics get ugly fast, strange personalities fighting over small stuff with minimal importance. Now exchange "Management" in the first sentence with "Programming in a team" ;)
Earlier quoted context omitted.
Buying the newest laptop every two years is what like $2000 every two years? That's only $1000 per year, hardly a dent in a programmer's salary.
That's almost a month's salary for a junior/mid-level programmer in this corner of Western Europe.
Earlier quoted context omitted.
I'm still coding after almost 20 years in the job, and have no intention of stopping. I tried some other options - teacher, artist, entrepreneur. None of them give me the thrill that I get from programming. I still get locked into a flow where time shifts, and before I know it hours have passed. The only other activity that does that is Civ, and no-one is going to pay me to play that ;) If 10x assets is what drives y…
Same here, but it is a big fight to convince the others why you want to stay that way. Right now I get the feeling that long term, going consulting might be the only option left as regular companies tend to only keep juniors coding. > You might be dead tomorrow; you might as well enjoy today. Just for this remark I wish I could have upvoted you more than once. This is something that those that live for the job, witho…
And yes, Ican relate to the article; I've seen (I still see) junior managers who can barely tie their shoes make more money than excellent engineers with 25y experience, but that's the way the world is...
Basically 'engineer'/'programmer' is a calling for some; it is for me. People for whom this is not a calling will never be /really/ good at it (for one thing, they don't spend their spare time doing it!) and eventually gravitate out of it.
But the ones for whom it is a calling, well, sod the money, give me some nice project/people to work on/with and I'm happy.
Or, do that but also get the money by going consulting. That's what I do for the last few years. It's quite exciting being a 'mercenary' in a way, and you can dissociate yourself from the companies/products and focus on the engineering.
He 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,…
At the risk of being "that guy", this actually misses the point of the poem. Quoting: "Though as for that the passing there/Had worn them really about the same/And both that morning equally lay" The poem states that the two roads are basically the same. Further points of interest... "I shall be telling this with a sigh/Somewhere ages and ages hence:/Two roads diverged in a wood, and I—/I took the one less traveled by…
> "No matter which road you take, you'll always sigh, and wish you'd taken another."
There's no disagreement here. It's the same interpretation of the poem.
Also keep in mind that it commonly happens that one of the first few programmers become a CTO? .That is not only because of the requirement of such a position but also a genuine care for the product which leads to him shouldering responsibility for the same.
So now if you were doing this responsibility shouldering and people management for 10 years,you cannot expect yourself to up-to-date and be tech savvy forever. Some people move to that position to also ensure relevancy. -It is much harder to remain relevant as a programmer in comparison to being in a managerial position.
TLDR;It all depends on how much you like to code in comparison to see through a finished product which sells.Both are symbiotic fields which need specialists in each area.
Earlier quoted context omitted.
JavaScript is actually an incredibly flexible and effective language.
> JavaScript is actually an incredibly flexible and effective language. == vs === No integers. Assignment is declaration. Prototypes. Curly brackets & semicolons. Semicolon insertion. It may be flexible (in the sense that an Alfa Romeo driven into a telephone pole at 120 mph is flexible), but it sure as heck ain't effective. JavaScript is the great shame of the computing industry: that it exists, and that it is used,…
And that is good.
With things like rust and go backing us up in places where more verbose and static code is beneficial (for performance?) we are finally entering new age which leaves closed corp-controlled "enterprise" things (java, net - looking at you) behind.
He 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,…
While that's entirely possible I don't think one can conclude it with certainty from his post. You say he'd be missing the programming side if he went the other direction but the only reason he listed for choosing programming was because he considered it easier. Looking at what he has achieved in his life and career as a programmer doesn't do much if those achievements aren't aligned with his values. Picking the wron…
My experience is that companies (many, perhaps most) are falling all over themselves to give senior programmers a shot at managing people.
Earlier quoted context omitted.
When one retires, there are lots of more interesting things to do with your life than spending the remaining days of your life in front of a computer screen.
Like what? The more I know about things outside programming, the more I see how interesting it is and how much boring, repeating stuff you have to go through to have fun in other parts of life.
Of course, you could just be repeatedly implementing the same thing with slight variations for years so minimal repetition in learning but maximal repetition in doing.
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…
> 5. Most business problems are political/social - regret every time we were called in to try and provide a "technical" band aid to those same problems. Why? Social and political problems are really hard to solve. If you can use technology to sidestep them, that's exactly the right way to do it.