Max retweeted
Most people still think Go is only for infrastructure.
• Go + Fiber → Blazing fast APIs
• Go + Gin → Lightweight backends
• Go + gRPC → High-performance services
• Go + PostgreSQL → Reliable data layer
• Go + Redis → Caching & rate limiting
• Go + Docker → Easy deploys
• Go + Kubernetes → Scale with confidence
Built for concurrency. Not for comfort.
Max retweeted
i realized people think switching to rust automatically makes their app fast.
true in most cases but,
a database query that executes in 400ms is still 400ms even if you like write it in assembly.
you probably won't reach the point where you will need that level of optimisation
Max retweeted
Si on m’avait expliqué la physique comme ça quand j’étais au lycée, j’aurais peut-être eu une carrière différente
Max retweeted
Here is a good place to start; it summarises things.
cloudstreet-dev.github.io/Da…
Max retweeted
be careful out there
It looks like the AI layoff boom has started to backfire.
I was just going through a Reuters investigation on Meta, and holy shit...
They drew up plans to cut some teams by as much as 60% and let AI agents do the work. THEN Zuckerberg called off the next round of layoffs hours before the first one even started.
And when you look at the numbers... they tell you why.
Engineers were pushing out 220% more code, BUT major technical and security incidents jumped 40%.
So people spent 70% more time putting out fires.
AI cranked out way more work, and humans spent way more time cleaning it up.
A different report I saw this week showed something similar.
32% of hiring managers said they brought back the exact jobs they cut for AI.
Think about how dumb that is. You fire people, pay a fortune for AI, then pay again to hire the same people back.
Look, I’m no AI bear. I use AI every single day.
It saves me a shit ton of time and I’m not going back. It’s an incredible tool.
But market forces are still market forces.
Every boom in history has been overhyped, and every CEO wanted to stand up and tell Wall Street he could do more with half the people.
Now from what I’m seeing, reality is kicking in.
It costs way more than they thought, it breaks shit, and you still need people who know what the hell they’re doing.
Even the AI companies are feeling it. Elon just cut Grok’s usage limits and admitted it costs more to run than it brings in.
I still think AI is a great bet, and I’m still buying the companies building the data centers. But you need balance, and the guys who went all in on firing everyone are learning that the hard way.
Be careful out there.
Max retweeted
The engineer who says no all the time is a real archetype among senior and staff engineers. Their role is to slow things down, to block the development of features that add complexity, and to ensure that as little code gets written as possible (since code is a liability).
ALT The engineer who says no all the time is a real archetype among senior and staff engineers. Their role is to slow things down, to block the development of features that add complexity, and to ensure that as little code gets written as possible (since code is a liability). We can think of this as the just-say-no engineer, as opposed to the just-say-yes engineer. The just-say-yes engineer is obsessed with moving fast, approves code changes by default, values MTTR over MTBF, and tends to ship a lot of code. The just-say-no engineer is obsessed with quality, is happy to move slowly, and blocks code changes by default. Most engineers are somewhere in the middle of the spectrum. By “just-say-no engineer”, I’m talking about the group of engineers who most strongly identify with that archetype.
ALT The just-say-no engineer is having a hard time in the era of AI. It used to be that they only had to say no to more junior engineers’ handwritten PRs, but now they have to say no to a barrage of AI-generated code, some of it generated by managers and VPs who are politically difficult to say no to. For the first time in their careers, they’re under a lot of pressure to lower their standards and start saying yes. However, this isn’t because of AI. It’s because of the end of ZIRP. ZIRP and the just-say-no engineer
Max retweeted
A lot of people are in my DM about knowing how to differentiate original from fake solar products.
So I will be discussing how to differentiate real from fake solar panels because that's another thing solar suppliers and installers do.
They can charge you for 550 or 600w meanwhile the panels they get you is 400w or less.
These panels are not sold the same and they don't do the same thing.
10 panels of 400watts is not same as 10 panels of 650watts
If you make that mistake, your system will start struggling and then you'd come and be complaining on twitter.
To be honest, knowing real panels and their real ratings is the easiest thing. You don't need any fancy gadget but your phone and the internet.
The first thing you have to do is buy only from the trusted the international brands. They are: Jinko, Longi, Trina, Canadian and JA
Neither is better than each other in my book. I use JA. My dad uses Jinko. I have friends that use Canadian. They are all good.
So when you're getting them or ordering them, ask your supplier to snap the serial number for you.
And you have to be careful, don't take the serial number on the sticker.
Every panel has a serial number embedded in the front, inside the glass. This is the original serial number!
Once you get this, simply type "Verification Jinko panels (or the brand you got) on Google and you'd be directed to the companies website.
If you put the serial numbers in, you'd be able to know if it's an authentic product and the real specs such as manufacturing date, power rating, grade and the likes.
However, don't make the mistake of testing the serial numbers in stickers because that can be easily changed.
That's it about knowing original panels.
You can go away now.
Max retweeted
buffered vs unbuffered channels in go.
when creating a channel, we have two options. we can either give it a size or leave it unbuffered.
a buffered channel allows the sender to send values until the buffer is full. the sender doesn't have to wait for the receiver to receive each value immediately. it only blocks when there's no space left in the buffer.
an unbuffered channel, on the other hand, creates a synchronous interaction between the sender and receiver. the sender has to wait until the receiver is ready to receive the value.
Max retweeted
A lot of developers are spending thousands of dollars learning skills that are already available for FREE.
Full-stack development, Python, machine learning, cybersecurity, cloud computing, and more.
There is an entire university-level computer science curriculum available on GitHub.
And you can follow it at your own pace.
github.com/ossu/computer-sci…
Max retweeted
This is what software engineering or development mean, not connecting framework
Totally agree with
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.
Max retweeted
how to reset your life in 2 weeks (practically tried and tested)
1. if your sleep cycle is messed up, wake up at the same time every day. no matter what, let your body adjust.
2. don't touch your phone as soon as you wake up. get some sunlight, stretch, go for a walk ( optional ) and make your bed.
3. before sleeping, make a to-do list for the next day. stop wasting your mornings figuring out what to do.
4. clean your room, organize your desk and get rid of unnecessary stuff. a clean environment means fewer excuses.
5. start exercising. go to the gym, run, walk or do pushups. stop treating your body like a decorative object.
6. reduce your social media consumption. you don't have to quit it completely, just stop spending your entire day scrolling. everything is fine in moderation.
7. start reading every day. your attention span needs rehabilitation. and no, reading doesn't necessarily mean picking up some random self-improvement book. blogs, tech articles or literally anything that interests you works.
8. eat properly, drink enough water and stop surviving on caffeine and whatever you find in your kitchen. try to maintain a balanced diet with enough protein, carbs, fibre, vitamins and minerals.
9. dedicate at least 2 hours every day to learning something useful. consistency matters more than anything. if you're building something, sure, vibe code it, but also spend some time understanding how things actually work. explore new things that excite you, whether it's tech, a hobby or anything else.
10. stop comparing your progress with people on the internet. everyone's timeline is different, and half of them are just posting highlights. MOST IMPORTANTLY, people here on X are doing some crazy stuff, so take inspiration from them and work harder, but don't turn their progress into a reason to doubt yours.
give yourself 2 weeks. don't expect a completely new life, just build some discipline and get a little more control over your days.
and if nothing's working, just give up...
Max retweeted
Got stuck today on a problem and the moment I took a break from my laptop and sketched the problem out with pen and paper I made way more progress.
Max retweeted
7 free resources to learn computer science fundamentals:
1. cs50.harvard.edu — Introductory computer science
2. teachyourselfcs.com — Self-study curriculum
3. nand2tetris.org — Build a computer from fundamentals
4. openbookproject.net — Open programming books
5. ocw.mit.edu — University course materials
6. cp-algorithms.com — Algorithms reference
7. missing.csail.mit.edu — Developer tooling and shell skills
Max retweeted
try this
github.com/cloudflare/securi…
Max retweeted
Built the payment gateway in Java
Got multiple interviews cos of it
Landed two roles
Now I have to choose which is better for me
Thank you sir
github.com/benx421/backend-e…
Maybe this will help
Max retweeted
you all are just sleeping on these resources btw
roadmap.sh/backend
roadmap.sh/devops
edureka.co/blog/category/dev…
fanout.sh/ai-engineering/ove…
reddit.com/r/databasedevelop…
reddit.com/r/devops
Max retweeted
If you want to become a better communicator, here are two free resources worth checking out.
Communication is one of those skills that will open doors for you, regardless of your profession.
Start with these:
1. How to Speak – MIT OpenCourseWare by Patrick Winston.
2. Think Fast, Talk Smart – Stanford Graduate School of Business by Matt Abrahams.
