I removed all recruiters and similar, leaving only people I know and (mostly) other engineers... And even then I basically only check the notifications anyhow.
So I consider myself fortunate; by not taking LinkedIn that seriously, I've avoided a lot of... awkwardness, to put it nicely.
In that case then the service will just hang as it won't handle the requests caused by even a simple malfunction (not even an actual attack) like the one mentioned by GP.
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.
I agree but with one caveat: If the difficult to integrate tool/library is open source, then one probably shouldn't ask likely already overworked maintainers for even more work. In those cases, one should probably be the change one wants to see by contributing the features, refactoring or documentation needed to ease integration.
The way I see it is that Linus already left his mark in history twice over (so far). I don't know how he feels about it[1], but if I were given the choice between being a billionaire and being remembered for a great thing I did, I'd certainly pick the second.
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.
What a wise words and comments to say regarding the matter. I won't be surprised if he had one of the craters on the Mars named after him in the future.
It also seems that in the interview Linus' wisdom really shining through. This perhaps due to the interviewer and interviewee were communicating through email, not in real-time, so both of them have ample time to reason and articulate their questions and answers properly. He who has been given wisdom, has been granted abundant good [1].
I think the interviewer missed the opportunity to ask Linus regarding one of his most popular quotes, “Only wimps use tape backup. REAL men just upload their important stuff on FTP and let the rest of the world mirror it.” The fact that he mainly contributed to the OS and the Git, both are essential components in doing online sharing. Thus it seems that he really took his conviction to be a REAL man, by his definition at least. And to be REAL man is one of the main purposes of life, according to Rudyard Kipling's poem, "If".
Nobody knows who Linus is..in all the "most admired" polls, even those computing down to #500 he doesn't appear.
If you want to be remembered you have to make an effort to put yourself out there...that's the reason why Musk is so shamelessly self promotional in the social arena. Same for Larry Ellison
This presents a strong case, IMO. And taking in account that studies have been made suggesting that language choice has little to no correlation with number of bugs[1], it would make sense that recency bias plays a part in, well, preference in technologies.
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.
htmx by itself is so good—when paired with discipline in the backend in creating proper fragments anyway—that so far I haven't needed hyperscript. But then again, htmx is so good that any project by the author has my vote of confidence by default.
Still, I oughta try this to make a proper judgement.
Not that the article itself didn't already have some odd takes, to say the least, but I find it a bit ironic that they talk about design with seeming authority when that site has a very strange anti-feature where every few minutes eyeballs pop up on screen—sometimes over the text, making it more difficult to read—and you have to hover the pointer over them to make them go away. It was absolutely terrifying the first time, and quickly got annoying after that.
In hindsight, the eyeballs act like an unintentional warning not to bother reading. And that's despite my agreeing with the initial premise that these flat rebrandings are getting way too common.
Well, as an avid movie watcher who absolutely loves the theater experience, I truly do hope they never go away, and that my hypothetical children get to experience them too.
> It turns out Kubernetes is actually perfect for small teams
As long as at least one of them is an expert on kubernetes. In this case, the one person in the team is that person, and as he points out in the article, he's using it because it's what he knows.
That should be the takeaway, I think. The "trope" remains pretty sensible IMO; I've seen it first-hand, jumping on kubernetes without the know-how is a foot-gun factory, and that team ultimately gave up on trying to implement it.
Probably, the best answer to the "programming is easy" mindset I've read is this article[1] about whether software engineering is actually engineering. Turns out we are engineers, and we're not even that special as far as engineering goes.
And it's funny, because the article has nothing to do with whether programming is hard or not. Not idea what Wayne thinks of the matter.
So I consider myself fortunate; by not taking LinkedIn that seriously, I've avoided a lot of... awkwardness, to put it nicely.