2,220 karma · joined October 30, 2018
You might be thinking "hey, wait a minute, that sounds like negotiating!". Well... You have to have something to negotiate with.
So the question is how can you generate leverage?
This is very colorful. He should have written thriller novels. Shame he wasted his life doing "something with computers".
Isn't this the basis for the prediction that every app that can be written in JavaScript will eventually be rewritten in JavaScript.
By virtue of not being born there I'm better off than the vast majority. Sure, I work hard at what I do. I'm also lucky a series of lucky and unlucky events transpired the way they did in order for there to exist an opportunity for me to work hard at something and do well.
Luck is 90% of it for pretty much everyone.
No, it simply makes good systems brutally improbable.
Re: Surgeons - precisely the point. A perfect result demands a high level of skill which the average developer has nowhere near. As a result there are lots of casualties.
I have three philosophical perspectives that help me better frame the software industry.
Number one: People aren't stupid. Rather, things are hard.
Number two: Writing software is like doing a trillion piece jigsaw puzzle.
Number 3: Software Engineers are like Surgeons, except the twelve years of training is received on the job.
Can I ask what stack? What does the production infrastructure look like? How many years of experience you have? And was it 2 months full-time or the equivalent of or just 2 months calendar time hacking nights and weekends?
I swear some people are really, really fast builders. I'm trying to improve my speed and I keep coming back to the answer of keep it as simple as possible and study your stack to know it backwards.
That's the worst feeling.
I think the magic could really come when you have full headless component libraries and full sets of libraries that skin them. You can always roll your own skin. But that's better than having to roll your own entire component library just to get around last-mile issues.
We are slowly but surely working towards higher and higher levels of code reusability at all levels of the stack. Reusable UI is massively important to productivity.
C sounds like one hell of a ride.
Tbh if you are an expert in X and I need you for Y and Y is analogous to X and there is time allowed for ramp up, then it's all the same to me.
Stuff that has an incredibly long half life like SQL/Database internals, or OS fundamentals, networking fundamentals, CS fundamentals will serve you well basically your whole career. So even a little bit of time dedicated to these over the long run is time pretty well invested.
A larger portion of learning goes on to the treadmill of technological churn, but that's either stuff you are learning now in order to get your next job working with it or are learning now as a result of getting a job that gave you the opportunity to work with it.
The middle ground is getting deeply familiar with libraries/frameworks that have a medium term half life. Usually that's some form of data access.
Under the right circumstances, anything I tell you could be wrong. Including this.