If you think his writing is any of what you posit,

It does. Most of us don’t go around writing essays rationalizing how we treat others like shit, and framing basic decency in daily interactions as “expending of energy”, and then make it believe everyone else should just be ok with this.

It’s a colossal red flag. Then the racist rants make it all the worst.

Don’t take my word for it. Perhaps take the hiring managers’ word?

Sauce? I read through several posts on the blog and didn’t find what you’re talking about

You must have done a poor job reading them.

I’ll leave you with this facepalm read.

https://www.jacky.wtf/essays/2026/nice-for-what/

In the spirit of offering some constructive feedback/raise awareness,

Developers are not the only ones using AI. Nowadays recruiters use AI ao automatically filter potential good fits for a position based on whatever signal they can gather. This means CV but also cover letters, portfolios,etc. sites such as LinkedIn even started offering a quick fit assessment based on the metadata you provide in your profile.

What this means is that, from a candidate perspective, it’s crucial that you start your application with a CV that you create specifically targeting the position you’re applying to. Your first barrier to entry is the AI assistant that is tasked with assessing fit.

You can still create your CV by hand, but your CV must be created with the express purpose of being parsed and evaluated by AI assistants, and you need to present yourself in a way that ticks the boxes that the position want to tick.

Nowadays, 95% of the job adverts don’t represent a position that will be filled. In those 5% that do, you need to make your application count. I had recruiters reach out to me for positions that I am clearly not a good fit just because my profile ticks the right boxes, and I had FANG recruiters reach out to me and let me know that they literally don’t read past the first page of a CV. To get them to pay attention, you need to make your case that you are the ideal candidate for that very specific position. Otherwise, others will.

so it’s natural to think something is odd here.

I glanced over a few other blog posts from the blog. The guy is describes himself as a troublemaker and has a whole blog post on how it is hard to be nice to people.

And the guy has a track record of posting highly racist comments to boot.

This is from the last half a dozen blog posts.

Perhaps the guy is going through a mental breakdown. Perhaps not. But I’d be hard pressed to pick this guy over any other candidate.

But you will not have learned much, if anything, by copy/pasting the answer.

Your ignorance is showing. The whole point of using SO to help troubleshoot problems is avoiding the troubleshooting stage and all the iterative work of cross-checking docs with parametric tests. The main deliverable of SO is not a magical code snippet but a root cause analysis on a particular failure. You end up with a nice summary of someone else’s prior work troubleshooting the same issue, and a clear indication that X causes Y because of Foo.

And you do not get that by reading official docs documenting the happy flow. You’d know that if you had any relevant experience developing software.

Your comment shows some ignorance mixed with lack of experience. Errors do happen due to many reasons, and there is no project on earth that is nearly as documented as you pretend them all to be. This is one of the reasons why googling for error messages ended up being a very basic and mundane technique in software engineering.

What makes your comment stand out is the fact that you are completely unaware that some projects even use Stack Overflow to help users troubleshoot issues, with project maintainers taking the lead in providing answers. But here you are, pretending that reading docs is a silver bullet

I (and other actually competent devs I’ve talked to about it) have always gone straight to official documentation first.

This is silly posturing. Anyone that is troubleshooting a problem tends to start by googling the error message, and more often than not Google will return SO hits, not official documentation.

No left at the company even knows how to work the erp properly. Because the person who set it up and customized it didn’t document or train anyone and then left…

That’s not technical debt. That isn’t even the definition of legacy code. That’s a mess and a whole set of problems, but technical debt ain’t one of it.

Is it really unethical if it benefits the organization? Even if that’s not really the goal.

The blogger acknowledge that the use of the word “unethical” as a hyperbole ton drive engagement.

The real-world issue is that we need to get stakeholders on board with the idea of having to do extra work that is not required to deliver a feature. If you tell a manager that you need to spend a month rewriting a system that was just launched, they will laugh at you.

Technical debt is very real and can complete fuck companies.

Even though the situation you described is unfortunate, I don’t think it has any relationship with the concept of technical debt.

The term “technical debt” conveys the idea that a resource is invested in a way that requires to be repaid later. The whole concept revolves around the idea that taking shortcuts doesn’t eliminate the need to actually do the work to make things then right way. Rushing to a deliverable can leave a mess in your wake, but cleaning up that mess is also work that needs to be done and doesn’t magically go away.

Consistency is NOT the most important thing. Correctness is.

What point do you think you’re making? I mean, do you think anyone looks at a PR and says “this PR is clearly wrong, but it’s so consistent that I must approve it.” That’s obviously not the point, is it?

You’ve never met an average ASP.NET developer?

OP is right. For web development with JavaScript frameworks (React, Angular, etc) with Node and even Typescript, you either use vscode or you haven’t discovered vscode yet.

They’re really not. As much as I hate commercial licensing for any dev tools, if you want to talk about superior there’s nothing quite as good as Visual Studio (not code) on Windows.

It really depends on what kind of project you’re working on. For .NET projects that might be true, but for other languages such as anything involving C++ then Visual Studio lags way behind CLion, which is multiplatform to boot.

Your comment feels half-baked at best. You start to talk about “best editors” but you proceed to present your two best examples and neither has anything remotely related to editors.

CLion is undoubtedly the absolute best IDE for C++ projects, and it’s multiplatform on top of it. It’s not even a competition, specially if you’re using CMake. Using Git integration as your best and single example to refute this is extremely puzzling by how silly it is.

i interpreted the “trend” correctly, “devops” was bastardized away from its original meaning to now mean “sysadmin”, at least in most cases.

I don’t think I agree. The role of a sysadmin involved a lot of hand-holding and wrangling low-level details required to keep servers running. DevOps are something completely different. They handle specific infrastructure such as pipelines and deployment scripts, and are in the business of not getting in the way of developers.

And Gallup claims that 29% of Americans have been diagnosed with depression at one point:

That really doesn’t mean anything. The only requirement for succumbing to a depression is being alive, because all it takes is something bad happening in your life (loss lf friend, loved one, even pet, etc) to fall into a pit of despair.

Every job lately seems to have been infected by Meta/google “data driven” leadership. Its so painful and wasteful sometimes.

It’s cargo cult mentality. They look at FANGs and see them as success stories, and thus they try to be successful by mimicking visible aspects of FANG’s way of doing things, regardless of having the same context or even making sense.

I once interviewed for a big name non-FANG web-scale service provider whose recruiter bragged about their 7-round interview process. When I asked why on earth they need 7 rounds of interviews, the recruiter said they optimized the process down from the 12 rounds of interviews they did in the past, and they do it because that’s what FANGs do. Except FANGs do typically 4, with the last being an on-site.

But they did 7, because FANGs. Disregard “why”.

In the 2010s, the mindset at tech giants seemed to be that they had to hire the best developers and do everything they could to keep them.

Not really. The mindset was actually to hire skilled developers just to dry up the market, so that their competitors would not have skilled labour to develop their own competing products and services.

Then the economy started to take a turn for the worse, and these same companies noted that not only they could not afford blocking their competitors from hiring people but also neither did their competitors. Twice the reasons to shed headcount.

It was not a coincidence that we saw all FANGs shed people at around the same time.

A comment on the YouTube video makes a good point that we already have a better word for the concept of dealing with multiple things at once: multitasking.

I don’t think that’s a good comment at all. In fact, it ignores fundamental traits that separate both concepts. For example, the concept of multitasking is tied to single-threaded task switching whereas concurrency has a much broader meaning, which covers multi threaded and multiprocess execution of many tasks that may or may not yield or be assigned to different cores, processors, or even nodes.

Meaning, concurrency has a much broader meaning that goes well beyond “doing many things at once”. Such as parallelism and asynchronous programming.

Do we really need a video about this in 2024? Shouldn’t this be already a core part of our education as software engineers?

I’m not sure what point you tried to make.

Even if you believe some concept should be a core part of the education of every single software engineer who ever lived, I’m yet to meet a single engineer who had an encyclopedic knowledge of each and every single topic covered as a core part of their education. In fact, every single engineer I ever met only retained a small subset of their whole curriculum.

So exactly what is your expectation?