I'm begging you to try systems programming.
I built tiny AWS - a cloud using no Docker, no VMs, just 10,000 lines of Golang and Rust code with this same mindset. Tiny AWS is legit just cli, and not even React or NextJS codes.
Stop spending all your time learning another framework, another library, another abstraction. Go figure out what actually happens underneath.
- Write your own memory allocator.
- Build an operating system kernel.
- Implement a TCP stack.
- Write a compiler.
- Build a database engine.
- Understand how Linux schedules processes, manages memory, handles interrupts, and talks to hardware.
Learn C. Get your hands dirty with Rust. Read source code. Read the Linux kernel. Break things. Spend time debugging a segmentation fault because you forgot how pointers work.
And then experience the satisfaction of finally understanding WHY something works, instead of just knowing WHICH API to call.
We're entering an era where AI can generate thousands of lines of code in seconds. Frameworks are getting easier. Abstractions are getting higher. The barrier to shipping software is collapsing.
But here's the interesting part:
The easier it becomes to generate code, the more valuable it becomes to understand what's happening underneath it.
Anyone can ask an AI to build an application.
But can you explain WHt happens when a process gets created? How memory is allocated? What happens when a packet travels through a network? Why a database quEry becomes slow?
Can you debug something when the abstraction leaks and the documentation stops helping?
That's the difference between knowing how to use technology and understanding how to engineer it.
You don't need to become a kernel developer. You don't need to abandon web development. And you certainly don't need to reinvent everything.
Just spend some time building things that force you to think.
Because there's something incredibly beautiful about programming when you stop treating computers as magical boxes that execute your JavaScript.
Don't just learn to build software. Learn how the machine works.
I'm telling you, try systems programming at least once.
@navyabijoy Yeah I believe even if we used to write basic applications back then without AI, but atleast felt the joy of understanding eveybit of code, it made us smarter.
π since past 3-4 days paypal's signup has been failing β
I've been trying to create an account to access their resources for the Paypal AI hackathon, the otp issue still persists.
And boommm their discord server is full of compliants. Do fix it ASAP!
@PayPal@devpost
Continued learning system design today:
- learnt about caching ( write policies and access patterns )
- understood how to approach a design question
- will wrap some basics within 2-3 days. before moving onto popular designs like ( uber , insta, netflix ..)
#learninpublic
I've been trying to learn system design for a while ,by going thru random articles and sources ( but lack the discipline, to follow a structure path ).
Today marks the beginning of my system design journey...!!!
I will be sharing my learnings on X and Linkedin
#buildinpublic
College Seminars , suck anyways!!!
Even more when you are deprived of presenting on your topic of interest, and rather forced to choose some crap your proff forced you to πππ
@itshaquiba I agree it's more about architecture and system design, but still back in the days I feel writing the code definitely made us smarter , thinking out the logic and structuring , but pity on us for what's happening nowwww
I've been working on my Backend project, for quite a while now ( over a month)
Still setting up NGINX , along with k8s on EC2
Will figure out the improvements of frontend .
Learning by building and breaking things β‘
#buildinpublic#backenddevelopment