ProgrammerMonk's profile picture. Programming || Richard Feynman || Marcus Aurelius || Books || Minimalist || Tweets on Tech/Books/Work/Philosophy

Akshay

@ProgrammerMonk

Programming || Richard Feynman || Marcus Aurelius || Books || Minimalist || Tweets on Tech/Books/Work/Philosophy

固定されたツイート

Reading is when you take your brain for a walk.


Probably the best CS advice in a single picture. Source- teachyourselfcs.com

ProgrammerMonk's tweet image. Probably the best CS advice in a single picture. 
Source- teachyourselfcs.com

When working with / building a storage systems, I so much prefer "append only" form of writes. Makes dealing with concurrency, crash recovery and sequential writes - so much easier.


".... technical skill, product thinking, project execution, and people skills. And the more senior you get, the more you’re expected to contribute to each." joshs.bearblog.dev/being-good-isn…


SLO's! 100% green is great, but if your SLA is 98%, use that 2% to test in prod. Break things intentionally (maybe) and test that things will really on that rainy day.


Be it music, code, technical writings or whatever.. are you "producing" ? Some of the best advices to come back to every few months. guzey.com/personal/what-…


Akshay さんがリポスト

I loved this advice to young programmers: "If you like programming, you should learn programming. Just be content with all outcomes." This is how I live too. Great life lesson 🫶.


Akshay さんがリポスト

you need the founder. you need the founder there - he actually needs to be present. if the founder is gone it's over. this is why you can't invest in founders that are normal. normal people would stop pushing as soon as they have a modicum of success. you need insane founders


I am very skeptic when it comes to using any for of AI for doing the first draft of Writing. Writing is how I "Think". And it's true for many, imo. I read the post below recently, and concur the feeling on writing (thinking) with AI. dcurt.is/thinking?utm_s…

From a dev (at Amazon): "I use Claude all the time to write PR/FAQs and perf peer feedback: the things that were always time-consuming and I hated doing. Now I dread them less and can get back to coding faster." Interesting, given Amazon was big on writing to *force* thinking!



The best Software Architect role description that I have read : "instead of the superhero we need “super glue” architects—the guys who hold architecture, technical details, business needs, and people together across a large organization or complex projects"


"Q: How to destroy your social capital? A: Request a lot of changes on a PR."


The author of the book CODE, Charles Petzold, is making Logarithms understandable. I love this his latest work. lostartoflogarithms.com/chapter01/


Akshay さんがリポスト

Faking PTO to write code is a globally useful tip.


I was making some notes from everything I have done around metrics in the last year, but then ended up turning that into an elaborate blog. Metrics in #Observability space are overused. If you don't pay close attention, you will over pay the vendor. performanceengineeringin.wordpress.com/2025/01/07/obs…


Loading...

Something went wrong.


Something went wrong.