I learned how to type with this, at the age of 22 as a full time software engineer! I never knew how to touch type, but then I somehow landed a software engineering job. I figured I needed to learn, so I downloaded this and played it so much. Good times.
Ah yes, that would make sense.
I’m over here thinking like a firefighter trying to ventilate a roof, not like a contractor trying to install a window.
Chainsaw and a skylight. A big one too, like one of these
And yeah, yeah, I’ve heard they are a pain to maintain and break easily. I don’t care, I’ll fix it every week if that means I get a balcony and fresh air every day.
I suppose this is a hot take, but I’d never intentionally select a closed source paid database or programming language. Your data is the most valuable thing you have. The idea that you’d lock yourself into a contract with a third party is extremely risky.
For example, I’ve never seen a product on Oracle that didn’t want to migrate off, but every one has tightly coupled everything Oracle so it’s nearly impossible. Why start with Oracle in the first place? Just stay away from paid databases, they are always the wrong decision. It’s a tax on people who think they need something special, when at most they just need to hire experts in an open source database. It’ll be much much cheaper to just hire talent.
Meanwhile I’ve done two major database shifts in my career, and you are correct, keeping to ANSI standard SQL is extremely important. If you’re on a project that isn’t disciplined about that, chances are they are undisciplined about so many other things the whole project is a mess that’ll be gone in ten years anyway. I know so few projects that have survived more than fifteen years without calls for a “rewrite”. Those few projects have been extremely disciplined about 50% of all effort is tech debt repayment, open source everything, and continuous modernization.
I don’t think it’s going away until ECMA supports native types. Until then it’s the best game in town.
If a team decides to move away from it, it’s only few hours work to entirely remove. So even if it’s going away, it’s risk free until then.
But I cannot imagine why any team would elect to remove Typescript without moving to something else similar. Unless it’s just a personal preference by the developers who aren’t willing to learn it. It removes so many issues and bugs. It makes refactoring possible again. I think teams that want to remove all types are nostalgic, like a woodworker who wants to use hand tools instead of power tools. It’s perfectly fine, and for some jobs it’s better. But it’s not the most efficient use of a team to build a house.
Makes me think of this amazing recent SNL skit
Thanks you made me laugh so hard I woke up my partner
I’M FILLED WITH SEARING AGONY
Illuminating manuscripts on vellum November
This is fantastic
It’s hard to remember that not that long ago it was super rare to eat any food not from within a hundred miles. The idea of this unusual canned soup was probably pretty wild.
You definitely described it perfectly: total chaos.
Titles are just “how valuable you are to that team”.
Every team has different needs, so a senior engineer in one team might be a junior on another team that has a totally different set of needs. There is also no standardized titles, so it mostly is just “whatever they want to call it”.
This is absolutely cursed and brilliant. Bravo!
Now I just need to find a place to use it.
Quite a phancy phallus
Definitely include a graph of shareholder value overlayed on top.
Sarcasm aside, maybe we should have a graph that also shows:
And see that by basically all metrics we are working more, paid less, more depressed, more stressed, and unhappy.