2,220 karma · joined October 30, 2018
Today a recruiter crashed one of my mental containers when she made an API call to me telling me she had an opportunity for me and I responded with 200 "I've got a new role now that I'm happy with" then she fired a GET request for the company I am currently working. I don't implement that method on the social contract (I commented it out recently) and instead just returned a 404. She then immediately fired another GET request for the same information and my mental container just crashed. Just hung up and ended the call. That isolation is great though because I went straight back to enjoying my beer.
Long story short it became problematic pretty quickly and I ditched it. You need to also be able to reply as that email address too etc. It's been done a bunch a times I understand.
This in my experience is the most important factor.
I think in an abstract sense control theory is a reasonably good bet.
https://en.wikipedia.org/wiki/Control_theory
I can't say I know it deeply, but a lot of the ideas resonate when I think about software engineering. If you think of everything as basically an n-dimensional vehicle with an interface to control it and the control mechanism is used to set all the parameters relevant to the system then a few things follow:
every system has a safe operating envelope
parameters are usually linked to eachother such that turning one up turns another down
I find there is a lot of mileage to be had about thinking about which parameters are linked to eachother and when you get excited about turning one of them up (ie you bring in TDD or a Kubernetes type solution) what is the effect you are having on the other parameters? That's where a new source of pain is going to come from. The biggest mistake I see in reasoning about these kind of things is being blind to the negative side of the trade-off due to the overwhelming excitement of finally being able to jump on the bandwagon and join the cargo cult. You have to train yourself to hunt for the parameter that is being affected indirectly as that's the most important side of the trade-off. You need to reason about whether or not the indirectly affected parameter's new value would take you outside of the safe operating envelope.With every decision we make about systems we build and run we are essentially trying to steer them, albeit clumsily, in this manner.
Good times.
Then again seniority has many dimensions. I often see a lot of senior devs who have mid level skills or mindset but they have become domain experts or experts in the product and seniority is conferred that way. I don't necessarily think that is wrong or undeserving either. I guess if we are talking absent any business/domain knowledge then seniority is judged more closely off raw technical familiarity. For me it's about system design/architecture. Having a strong set of principles that guide your decisions etc.
The other is the "Octopus". An octopus has reasonable skills at fullstack dev, customer development, business development, business analysis, marketing, sales and accounting.
I've always felt relatively underpaid compared to what I wind up bringing to the table, but I would say there have been subtle but noticable perks in other ways and it's definitely translated to comp over time too.
It clicked for me a while back that the vast majority of devs just working on line of business applications have never and will never put together an entire enterprise grade system end to end by themselves in their career. So all you really have to do is (a) have a relatively good head on your shoulders and (b) just hack away at building out a fully fledged system end to end in your own time. A sort of reference architecture of your own. Then when you need to implement stuff at work, you've already solved the problem once before so instead of taking a day to wrap your head around how a particular part of it works, you just whizz through it relatively quickly. It looks like magic from the outside, but it's nothing more than being prepared ahead of time.
It typically just means front-end, back-end, database. Not networking? I know it says "full" but it's not that full.
I truly do wonder exactly how much software you could produce if you had 2.2 billion dollars to do it.
Governments are getting taken for a ride.
Software is art, fashion and politics.
That hasn't change in the last few decades and it won't change in the next few decades either.
Entropy. It's not our friend. It's why we can't have nice things. Code bases suffer from bit-rot over time.