Engineer
India
Joined June 2021
- Tweets202
- Following70
- Followers68
- Likes11.3K
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 Patil 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.
Day 96 of #100DaysOfCode. I've decided to learn about gRPC which I left earlier in the challenge. I will be building a small server application that takes in a service schedule and stores it somewhere. Started it.
Day 95 of #100DaysOfCode. The earlier bug fix didn't quite solve the problem. Made some changes and resubmitted it for review 😬
Day 94 of #100DaysOfCode. Completed the fix, I was working on. But it's just embarrassing it's just a one-word change and still, I'm sure if the fix would get accepted xD
github.com/techrail/ground/p…
Day 93 of #100DayOfCode. Still working on the same bug, it's frustrating and entertaining at the same time that I'm spending this much amount of time on a fix that would just account for a couple of lines of changes.
Day 92 of #100DayOfCode. I'm working on an open-source programming task and thought I had fixed a bug, but it turned out I misinterpreted it. Instead of deleting a duplicate value, the system needed to distinguish between them. Ouch!