I made a tax calculator mainly for IT contractors in Poland.

IT professionals earn from 4k - 7k EUR/month in Poland, where the cost of living is quite low compared to other Western EU countries.

See how much of tax you would pay as an IT contractor in EU, Poland

&gt; "There will be no programmers in five years.” -Emad Mostaque, founder and CEO of Stability AI (Stable Diffusion)

I agree with this, except I’d put the timeframe more conservatively around 10 years.

I think in 5 years, most software development will be done by computers. Humans will prompt AIs that generate the code. AI at that point will be able to work within existing codebases and implement trivial feature requests on its own, detect and fix bugs, and debug itself.

In 10 years, AI will unquestionably be superior to humans in software development – just like AI is already better than humans at chess and Go. Handwritten code will not only be considered useless, but writing code by hand will be considered bad practice because humans will be considered less reliable and more error-prone than the machine.

A “software engineer” in 2033 will be more of a CTO-like managerial position where that person is in charge of the tech of an organization, but they’re delegating the tasks to AIs. Companies will need less and less software engineers as the AI advances and ultimately displaces humans. Of course there will be engineers building and maintaining the AI, researching, and working at the bleeding edge, but overall there will be significantly less demand for human engineers. What few jobs remain will be higher demanding since AI will only improve – and a human has to be able to do what an AI can’t in order to be useful – a bar that will only get higher and higher until it is eventually unattainable.

With humans rendered economically obsolete to machines, governments will have no choice but to implement a universal basic income in order to prevent mass poverty and chaos. Unfortunately a lot of workers will be displaced and people will suffer before governments implement UBI due to the enormous capitalistic brainwashing against UBI.

### Why this time is different

The reason technological advancement will actually result in net job destruction this time is because technology is getting better than humans and approaching Artificial General Intelligence (AGI). Large Language Models (LLMs) like ChatGPT can reason, and thus solve problems it hasn’t specifically been programmed to. In the past, technology had to be built to solve a specific problem in order for the human to be rendered obsolete (eg. the loom), but AGI can solve any problem. As we approach AGI, the only value that humans can provide will be that which AGI is not yet capable of solving. There is no upper bound on how smart AIs can get, but humans have a clear biological ceiling.

### AI will beat humans at software development

Just like AI is superior to humans at games like chess and Go, there’s no reason that AI won’t reign supreme when it comes to programming. AI can already pass Google’s coding interview, the bar exam, MCAT, etc. at a speed that no human could even come close to – like a flashlight competing with a sloth.

Humans look at ChatGPT now and laugh at its often nonsensical answers and hallucinations. Yes, but you’re looking at the equivalent of one of the first computers in the 1950s, or dialup internet in the 90s, a floppy disk with 1MB capacity, or mobile in 2007. Remember, ChatGPT was only released November 30, 2022. OpenAI’s Code Interpreter was released in beta last week to ChatGPT Plus users, an AI that can execute Python code and that you can upload files to. We’re in the first inning of an AI arms race, and at the speed at which things are progressing, it’s pretty clear that AI will be drastically more developed even just another 6 months from now.

As a software engineer, I have full awareness that most of what I know that makes me valuable will be obsolete within a decade because AI will be able to do it faster, cheaper, and better.

The stages of AI progress in software engineering look something like this:

1. Chatbots tell you the answer, for example by giving you code, which you then need to copy & paste in the right files – adjusting to fit within your codebase.
2. AI assistants write the code directly inside your codebase (eg. like “autocomplete” except with a task more complex than simply predicting the end of the word you’re typing)
3. AI assistants/agents execute the code, and debug itself to correct any errors

The reality is that the vast majority of dev work has already been done before, and thus is very trivial to replace with AI.

Humans basically get paid by arbitraging knowledge and producing some output. Software engineers have knowledge of tools, libraries, frameworks, commands, version control, infrastructure, data structures & algorithms, networking, APIs, etc. and use this to write computer programs and create software.

Search engines, Stackoverflow, open source, internet forums, tutorials, Youtube, books, etc. democratized much of this knowledge – but still require a human to research and utilize this information to create software by writing computer code.

AI can do all of this far superior to humans because AI has all of the world’s knowledge, and can execute at the speed of light.

Even if AI code were to be inferior to human code – which by the end of the decade certainly won’t be the case (just like AI beats humanity’s best chess and Go players), humans are still going to be rendered mostly obsolete. Businesses don’t care about code, they want solutions that improve their bottom line. If an AI can solve the problem with half the performance and code quality in a couple minutes, is available 24/7, and only costs pennies/dollars, vs. a team of engineers with $200k/yr salaries taking a month, only available during business hours, and with vacation time, maternity/paternity leave, and other liabilities – who do you think is going to win out? Remember the AI is only going to get better, faster, and more knowledgeable, while humans are biologically limited in work output, and there will be a point where humans no longer have the edge.

I think it’s fairly obvious at this point that AI will supplant humans, but **most people are drastically underestimating how quickly this is all going to happen because most humans struggle to understand exponential growth.**

I don’t have a crystal ball, but here are some rough conservative predictions I’ll make off the top of my head:

- 2024-07-14 – AI agents can create codebases, write code in existing codebases directed by prompts (eg. “add this feature”, “create this API endpoint that does this”), and debug itself (eg. detect compilation/runtime errors and patch them). The tech will be slow and awful at first so engineers will initially laugh at it claiming they’re not worried about their jobs.
- 2025-7-14 (2 years from now) – These AI agents will start becoming reasonable enough to where they’ll automate the more mundane / trivial work. People will still have to know what to prompt to get the right results, and modify and fine tune the resulting AI-generated code, but AI will start to take the driver’s seat. Instead of the default being for the human to start tackling the problem and ask the AI for help when in need of assistance, it’ll start to become expected to let the AI tackle the problem, and bring in a human when that fails.
- 2026-7-14 (3 years from now) – AI agents start becoming competent enough to where their belonging is no longer questioned. Everyone is using them in some capacity. AI is the driver, but humans are still necessary to direct them and handle the edge cases where they fail. Typical dev work like building trivial web apps and APIs is a commodity at this point and nobody is doing that by hand.
- 2027-7-14 (4 years from now) – AI is the norm. At this point as an engineer you’re either working on building the AI itself, or you’re using the AI. The job of an engineer has evolved from less hand-writing code, to more of a managerial CTO type position, except instead of delegating to other managers and engineers, one is delegating to AI agents.
- 2028-7-14 (5 years from now) – So much human work has been made obsolete by AI that all governments in the modern world have implemented universal basic income.

### How to position yourself

Tech was always a rapidly evolving field that required constantly staying on top of the latest advancements, but that’s only going to exponentially increase.

- Stay ahead of the curve on AI advancement. Ensure you’re leveraging the most advanced tools.
- Don’t be overly married or emotionally invested in any one programming language, library, framework, or technology. Assume it will get displaced sooner than you think.
- Learn architecture and systems design. As we move up the ladder of abstraction, an engineer’s focus and responsibility will be more on deciding *what* to implement, rather than actually implementing the thing. Individual contributors (ICs) will become more like managers directing AIs.
- Stay humble. Assume that everything you know will be irrelevant in a few years.
- Either seek to become more of a CTO-like generalist, entrepreneur, or pick a specialty/niche (eg. machine learning, distributed systems, product, etc.) to stay at the forefront of. If you specialize, realize that you’re competing with AI.
- Get your government representatives to implement a universal basic income so that AI advancement can become unquestionably a good thing for society, instead of the current system where it results in the masses losing their livelihoods and an arms race for an ever-dwindling pot of human jobs as robots overtake us. This can either result in the freedom and leisure utopia that Keynes envisioned, or mass poverty coupled with enormous wealth inequality – and inaction will lead to the latter.

Human Programmers Will be Mostly Obsolete in 5 Years

The following is my current go-to tech stack that powers my sites like [zsync.xyz](http://zsync.xyz) and [mindgarden.app](http://mindgarden.app)

Article: <https://www.jbernier.com/p?id=my-tech-stack>

Youtube video: <https://www.youtube.com/watch?v=Dz4VIJkA59M>

Twitter: <https://twitter.com/jeremybernier/status/1692236854907789666>

My Tech Stack (2023)

Hi I'm Jeremy. I'm building this site because I'm not satisfied with other online community type websites and their lack of innovation (see the /about page). The goal is to make a superior, more open, and more decentralized online community.

The site is still in early stages in active development (see the dev masterthread here: https://zsync.xyz/p/zsync-dev-update-masterthread)

Join us if this sounds interesting! Feel free to send me any feedback or reach out directly!

HN: <https://news.ycombinator.com/item?id=37137110>

Rama - Reducing the cost of building Mastodon at Twitter-scale by 100x

Show HN: <https://news.ycombinator.com/item?id=36813086>

GitHub: <https://github.com/primocms/primo>

Primo - Visual CMS with Svelte blocks, code editor, and SSG (open source)

TypeChat uses the type definitions in your codebase to retrieve structured AI responses that are type-safe.

TypeChat

Show HN: <https://news.ycombinator.com/item?id=36958731>

Magic Loops – Combine LLMs and code to create simple automations

No-GIL mode coming for Python

Chidori – Declarative framework for AI agents (Rust, Python, and Node.js)

"Hi HN, we’re Nate and Ty, co-founders of Continue, an open-source autopilot for software development built to be deeply customizable and continuously learn from development data. It consists of an extended language server and (to start) a VS Code extension.

Our GitHub is <https://github.com/continuedev/continue>. You can watch a demo of Continue and download the extension at <https://continue.dev>

— — —

A growing number of developers are replacing Google + Stack Overflow with Large Language Models (LLMs) as their primary approach to get help, similar to how developers previously replaced reference manuals with Google + Stack Overflow.

However, existing LLM developer tools are cumbersome black boxes. Developers are stuck copy/pasting from ChatGPT and guessing what context Copilot uses to make a suggestion. As we use these products, we expose how we build software and give implicit feedback that is used to improve their LLMs, yet we don’t benefit from this data nor get to keep it.

The solution is to give developers what they need: *transparency, hackability,* and *control*. Every one of us should be able to reason about what’s going on, tinker, and have control over our own development data. This is why we created Continue.

— — —

At its most basic, Continue removes the need for copy/pasting from ChatGPT—instead, you collect context by highlighting and then ask questions in the sidebar or have an edit streamed directly to your editor.

But Continue also provides powerful tools for managing context. For example, type ‘@issue’ to quickly reference a GitHub issue as you are prompting the LLM, ‘@[README.md](http://README.md)’ to reference such a file, or ‘@google’ to include the results of a Google search.

And there’s a ton of room for further customization. Today, you can write your own

\- slash commands (e.g. ‘/commit’ to write a summary and commit message for staged changes, ‘/docs’ to grab the contents of a file and update documentation pages that depend on it, ‘/ticket’ to generate a full-featured ticket with relevant files and high-level instructions from a short description)

\- context sources (e.g. GitHub issues, Jira, local files, StackOverflow, documentation pages)

\- templated system message (e.g. “Always give maximally concise answers. Adhere to the following style guide whenever writing code: {{ /Users/nate/repo/[styleguide.md](http://styleguide.md) }}”)

\- tools (e.g. add a file, run unit tests, build and watch for errors)

\- policies (e.g. define a goal-oriented agent that works in a write code, run code, read errors, fix code, repeat loop)

Continue works with any LLM, including local models using ggml or open-source models hosted on your own cloud infrastructure, allowing you to remain 100% private. While OpenAI and Anthropic perform best today, we are excited to support the progress of open-source as it catches up (<https://continue.dev/docs/customization#change-the-default-l>[...](https://continue.dev/docs/customization#change-the-default-llm)).

When you use Continue, you automatically collect data on how you build software. By default, this development data is saved to `.continue/dev_data` on your local machine. When combined with the code that you ultimately commit, it can be used to improve the LLM that you or your team use (if you allow).

You can read more about how development data is generated as a byproduct of LLM-aided development and why we believe that you should start collecting it now: <https://medium.com/@continuedev/its-time-to-collect-data-on->[...](https://medium.com/@continuedev/its-time-to-collect-data-on-how-you-build-software-197d12a020d5)

Continue has an Apache 2.0 license. We plan to make money by offering organizations a paid development data engine—a continuous feedback loop that ensures the LLMs always have fresh information and code in their preferred style.

— — —

We’d love for you to try out Continue and give us feedback! Let us know what you think in the comments : )"

Show HN: Continue – Open-source coding autopilot

Node.js vs Fastify vs Express.js vs Deno vs Bun vs Go

The looming demise of the 10x developer

"AutoChain takes inspiration from LangChain and AutoGPT and aims to solve both problems by providing a lightweight and extensible framework for developers to build their own agents using LLMs with custom tools and [automatically evaluating](https://github.com/Forethought-Technologies/AutoChain#workflow-evaluation) different user scenarios with simulated conversations. Experienced user of LangChain would find AutoChain is easy to navigate since they share similar but simpler concepts."

Programming

t/Programming