People are scared AI proving P = NP and other hard problems.
I am just fascinated, tbh.
As a species we still haven't conquered deep space travel and we haven't figured out whether there are aliens in the observable universe, so its exciting, whatever is happening.
The problem with hype is, its easy for people to make moutains out of molehills, and our industry is plagued with course sellers, pretending they know a lot, but a lot their net worth is coming out of the gullibility of ambitious people who want to make something of themselves.
I love how confidently people talk about world wars. “You only realise you're living through one years after it begins.”
We've had two. TWO.
That's like having two production outages and writing a LinkedIn article titled “The 7 Stages of Every Production Incident.”
The problem with tech evolution is that everyone tries to predict things for humanity, and yet no one has a single complete clue about the collective mess we are.
It's hard to tell if the engineering influencer or guru you follow is an expert or not. Most of the time these folks just learnt to teach or present themselves well, and that doesn't always mean they have something useful to say.
Working as a software engineer has become extensively difficult. Everybody's sharing random half baked claude artifacts, expecting me to make unicorns from banana dough.
We have too much noise in the industry, with AI hype. Some engineering orgs close thousands of PRs daily, reverse engineering is child's play now, and our daily work is just machines discussing with each other. The problem is comprehension and attention. What to know and why?
The issue with all the AI hype around software engineering is some people have disillusioned themselves that they were competent before, and the others have accepted that they're incompetent now. Its funny.
There are people who say so absurdly nonesense things out loud confidently that they seem insane. Yet, for some reason, they have appeal, and are considered cool.
Hrishikesh retweeted
As a software engineer, it's very important to learn about Gall’s Law, which states that complex systems cannot be created successfully from scratch.
In reality, even large systems, such as Netflix, Google, or Facebook, have started small and built incrementally over the course of decades.
Herd mentality can trap you.
Herd immunity can save you.
If 90% get vaccinated, even the 10% who don’t are safer.
Sometimes, being part of the right crowd protects you.
Choose your crowd wisely.
#HerdImmunity #MentalModel #Psychology
The anchoring effect tricks us into focusing on the first info we get. Salespeople use high starting prices to make later offers look cheap. Stay sharp! #AnchoringEffect #CognitiveBias #BehavioralEconomics #Sales #Marketing #Psychology
I just published Push, Pull, Commit, Repeat: My Life with Git medium.com/p/how-i-use-git-1…
Read “Too Obvious to Check — So We Didn’t, and It Broke Everything“ by Hrishikesh Patil on Medium: hrishikeshblogs.medium.com/o…
Sometimes you'll find that people have developed their own terminologies while working on a project for far too long (let's say 5 to 10 years) that they feel is the industry term but nobody uses it except for them. It can get weirdly frustrating.
#developerproblems
People see work as a Job, Career, or Calling. Those who view it as a calling tend to perform better and feel happier. The good news? It’s easier than you think to find meaning in what you do.
sciencedirect.com/science/ar…
Day 100 of #100DaysOfCode. I learned about container runtime in detail and found a few amazing resources and it was fascinating.
TBH, I didn't complete the challenge with consistency, but I learned a lot about programming, go, and my own style of learning
github.com/itishrishikesh/co…
Day 99 of #100DaysOfCode. Learning about how containers work with this talk youtube.com/watch?v=8fi7uSYl…
Day 98 of #100DayOfCode. Wrote a simple grpc server and client. It doesn't do anything right now, but things work and communication between client and server happens.
github.com/itishrishikesh/go…
Day 97 of #100DayOfCode.
I hit an unexpected break with this challenge but I'm still continuing from where I left off.
Today -
- I learned/read more about HTTP/2.
- I learned/read about protobuf a bit, and generated some go code using a .proto file.