A formal degree and algorithmic problem-solving is the answer. Always has been. | zaksa<br>A formal degree and algorithmic problem-solving is the answer. Always has been.<br>22 Aug, 2026<br>Have you ever handled a surgical scalpel? It&rsquo;s an incredible tool - small, light and sharper than anything of its size and purpose. It takes thousands of hours of practice before someone is authorized to use it on human skin, and mastering it takes a lifetime.<br>You don&rsquo;t want to give this tool to the wrong person. No matter how motivated, open to learning, well-meaning and hard-working they are, they will mess things up. They might be a chef, a hairdresser or any other professional handler of a cutting tool. Despite their adjacent experience, they will mess up. Handling a scalpel for the purpose of surgery is a difficult job with high responsibility.<br>I like to use this analogy when thinking about the current state of software. We need a hard filter for people who want to use AI on a computer for the purpose of programming it. It&rsquo;s a bittersweet statement to make from someone who is both qualified and not qualified to make such an argument:<br>For the majority of my career, I neither had a formal, rigorous computer science education, nor I bothered to invest time in &ldquo;leetcoding&rdquo;. I did well nevertheless. I was and still am a person who builds software to solve problems. I don&rsquo;t always do it for money, I do it because I always wanted to do it. At the same time, I&rsquo;ve got a wealth of experience working with bootcamp developers, former physicists, engineers who either never finished or never got particularly far in their education. Experience has shown that, things rarely work out in the long-term if you aim to have a successful career without a degree or by skirting coding interviews. Lacking these skills in the current conditions might be career-ending.<br>Some anecdotes:<br>I once worked at a startup where there was a senior engineer who&rsquo;d force everyone on the team to order their file imports alphabetically. He also had the craziest linting rules ever, and whatever he could not codify in linting, he&rsquo;d make up with comments in pull requests. Ironically, that same startup had zero unit or e2e tests for the application layer, and a small bunch of smoke tests for the backend services. Testing and deployment was absolute hell that took weekends. They sure had their priorities straight.<br>At another gig, there was a person who&rsquo;d spent hours arguing about the length of the maximum symbols before wrapping text in an IDE, had a strong opinion on the &ldquo;tabs versus spaces&rdquo; debate, and also had custom-built everything, including an email service that would always hang and lose scheduled emails once we started onboarding more customers. Accept that your magnus opus of software is garbage and use a third-party service that doesn&rsquo;t churn customers.<br>I&rsquo;ve also endured language and framework experts. They&rsquo;re the type of developers who&rsquo;re relatively good in a very small subset of technologies, but completely lost in anything adjacent to them, and also are completely clueless about the fundamentals. These are the people who live in constant paranoia that the company they work for will make the framework they&rsquo;re expert in obsolete, and force them to learn something new. It is honestly tiring to hear a hour-long tirade of how great Angular in comparison to the mediocrity of React, or the inferiority of Kotlin in comparison to Java. Just suck it up and use whatever solves the problem best.<br>There are also completely clueless people who somehow slip through cracks, mostly in corporate environments. There was this person who touted to be a Linux expert who I asked for advice on my homelab setup. His initial spiel was good, explaining me a bunch of fun facts about the different distros and systemd, but after a few weeks of discussions, his suggestions stopped adding up, so I became suspicious. After prodding him with some fundamental questions about operating systems and networking, it turned out that he has a very surface-level knowledge and my homelab setup was the most complicated thing he&rsquo;d ever seen. There was also a similar situation where a particular piece of functionality wasn&rsquo;t working, and since I didn&rsquo;t consider myself good at the particular piece of technology stack, the person who wrote it and owned it turned out not being able to read and debug his own work.<br>Most of the people mentioned above held more senior positions than me at the time I worked with them, and all of them considered a formal education and computer science and skills in algorithmic problem-solving to not be important for a successful career. That mindset was either condoned or celebrated at many places I worked in. The people I wrote above weren&rsquo;t considered bad performers.<br>If I had to categorize the &ldquo;no need for education, no need for algorithms&rdquo;...