Your email address is your identity. So why is it tied to a big provider?
I'm building a mail service that lets you use YOUR domain.
Own your identity, control your communication.
Follow along as I build it. #Email#IndieWeb
I was fortunate to learn coding in the pre-AI era and implement it during the peak AI era.
From my perspective, I can share some insights.
This will be a long post, so I suggest enabling reader mode.
First, I want to talk about my college years and even before that, in 11th and 12th standard.
The narrative at the time was simple.
> Learn to code.
> Get a job.
> Secure a stable career.
> Switch companies.
> Build a net worth of a million dollars.
That was the roadmap everyone was promised.
I was also excited about it but before pursuing any field, I decided to try it first.
Many already know this journey, so I will skip the details. You can read about it on my portfolio linked in my bio.
The plan was straightforward.
Get settled through engineering.
Then the pandemic hit.
We got GPT.
Then Claude.
Opus.
Countless coding models.
Agentic AI.
Then came harnesses for coding, AI tools, and much more beneath the surface.
Now the problem is that many people are entering the economy through coding using no-code tools and building systems.
I am not denying that software engineering was difficult and now it has become comparatively easier, which is true.
But the nuances of the field remain.
A coder can create an app.
An engineer can create an app.
Even a less technical person can create an app.
Previously, only someone proficient in software engineering or with some experience could build apps or websites.
Those who did not know how to code could not create anything.
That was the entry barrier.
Now the barrier is shattered.
So what remains?
Those who do not know how to code, plus those with less knowledge of how code works and less experience, are trying to create meaningful software.
This brings a fundamental issue.
These people do not understand:
> How software works internally
> What tradeoffs they should make
> How security should be handled
> How to deploy to production
Code was not the only hard part.
The other hard parts were:
> Tech Tradeoffs
> Structure of code writing code
> Security
> Computation
I have been through many legacy codebases and I can tell you that even AI does not even write the amount of slop code I have seen in some legacy codebases.
Speed is not the problem.
The problem is context.
We are shipping at light speed and forgetting the context of how things happen.
This has become one of the fundamental issues for security.
Previously, many people worked on software and had enough time to think about:
Tradeoffs
Structure
Security
Many had read programming books and knew what to do and what to avoid.
Now anyone can code and deploy to production but they do not know:
How to preserve user data
How to handle security
How to debug a production bug when AI models are down
Many will say we can hire someone, but the context you need to give to an AI, you also need to give to a human.
Humans are not superhumans who can do many things with just one instruction.
We have fundamentally made one step easier and many think the whole montain is super easy.
No.
If you want to climb the mountain, you need to:
Learn to walk
Then run
Then climb
Then ascend the mountain
Hypothetically, that is engineering.
About layoffs and companies not hiring due to AI, it also makes sense to me.
During the pandemic, many companies overhired because cash was flowing from investors and SaaS and mini software were peaking.
Everyone was working from home and technology was the only thing connecting everyone.
Companies hired many times beyond capacity.
Once the pandemic ended, funds hit the real world.
Everyone realized they had overhired.
They started laying off people.
They did not want to devalue their stock by laying off because usually layoffs cause stocks to drop.
But now that does not happen if they say they are restructuring because of AI.
Internally, everyone knows it is not because of AI but because of the overhiring during the pandemic.
These companies are trying to protect their stock value by naming it AI restructuring.
We are currently in an AI bubble and the bubble will not break.
Once a lion tastes blood, it can never be a vegetarian.
The same happened with software engineering and with everyone around the world.
AI is not going anywhere.
If you think it will, you are really stuck.
I would highly suggest you upskill yourself with the current stack.
There is no stop to learning.
You should learn:
How code works
How to write raw code
What kind of code is good
What kind is bad
The entry to software engineering is harder than ever because low-quality apps and low-quality software are no longer good enough for entry.
Previously, if you knew a language, you were qualified.
Then it became harder.
If you knew a language and could create some projects, you could be hired.
Then it became:
If you knew a language, could build a project, and knew a framework, you would be hired.
Now it has become:
> Do you know the language?
> Can you create a project?
> Do you know a framework?
> Have you created a full stack?
> Have you deployed to production?
> Have you fixed security vulnerabilities?
That is how hard it is nowadays to get a job.
My take is that AI is going to stay here.
Companies will be mass laying off people now and then and calling it AI restructuring.
The entry barrier is shattered but if you are experienced and have gone through the depth of software engineering, no one is going to replace you.
Actual engineers are not replaceable.
There is still a need for good engineers everywhere.
Good engineers are rare.
You should be a good engineer and keep learning because you want to do it.
If you are just doing it for money, you probably will only survive a couple of years.
If you only want to be an engineer, then become an engineer.
Do not become an engineer if you are just here for money.
Since my 11th standard, I started tinkering with Arduino, low-level programming, Java, Kotlin, and building my apps.
I spent four years of college doing the same and now I have a job that pays comparatively well.
This is how long it took me to get to a position where I am confident enough that I can build software, fix any kind of vulnerability, and fix any kind of issue if I just spend enough time doing that.
So the intake is this.
If you are a fresher, do not be demotivated.
Head down and work hard.
You will be successful one day.
We just shipped Kosh's beta and we need YOUR feedback π
What's broken? What's missing? What do you love?
Join 50+ beta testers exploring custom domain email without the price tag.
https://t.co/8RIzXEL93c
Reply with your biggest email pain point β
If you're a solopreneur, freelancer, or indie hacker:
Your email IS your business.
[email protected] looks 10x more professional than Gmail.
But setup has always been expensive and ugly.
Kosh fixes that. Free. Modern. Built for you.
https://t.co/8RIzXEL93c