luord
In the future, I'll just link to this piece.
And now I'm not one of those people who think that everything PG writes is gold, but it's hardly "insight porn". In fact, if that particular essay is "advice", it's the advice to not even try as it's likely just not for you, so it almost seems like Greenfeld misrepresented it just because of a single sentence.
Fibery 2.5 hours downtime post-mortem. The Drama
- On type checking, I like type hints and gradual typing, but am not big on strict static typing.
- I'd like to do A/B testing, but only for fun and for learning/applying data analysis.
I post articles on what (I think) I know. Just a static blog generated by Pelican.
Feliz Navidad a todos!
Then I read articles like this and I remember why I like it: it gets the job done, and quickly (for the developers at least). It's why it's so widely used and keeps climbing. Of course, nothing wrong with learning other languages and I do try to keep up, but Python will remain my go-to for the time being.
Better to follow standards anyway.
But back to the idea of many applications being emergent and/or not at all (or not entirely) what their creators intended. Maybe there's room for both approaches depending on the situation.
Avoiding the pitfalls of iteration-based development, in 5 pull requests
Latency Sneaks Up on You
Strange domain names that developers bought
Latency sneaks up on you
Conti ransomware goes rogue, leaks “gang data"
The difference between software and hardware projects
Encoding Events for Neural Networks
How to start up (Accidentally)
So, assuming I understood correctly, treating them like tents is infinitely the better choice.
Modify HTTP request headers with transform rules
How to prevent scope creep when managing a project from home
So I consider myself fortunate; by not taking LinkedIn that seriously, I've avoided a lot of... awkwardness, to put it nicely.
Mind you, I see your point and I generally don't like the captchas either, but it is definitely a trade-off and I won't blame webmasters that use the DDoS protection.
If possible anyhow.
The Ball and Supply Chain
And sure, many people have achieved both, but they didn't take their money with them once they were gone. As long as you have enough to live comfortably, everything else is at most an incidental bonus IMO.
[1]: Though I haven't heard anything suggesting he's anything but pretty okay with his lot in life.
Tips for DevOps workflows: JSON formatting with jq and CI/CD linting automation
I'm interested in the outliers though: Both the ones among the loved brownfield languages, and the ones present in both loved and dreaded lists. I feel like programming language designers, people in charge of choosing the stack for new projects, and people considering renovating legacy codebases can learn a lot about what to do and what not to do from those.
[1]: Though that one ended up in a flame-war, like discussion on programming languages tend to do. Apparently not even academia is safe.
Still, I oughta try this to make a proper judgement.