Jai
@jaibhavaya.bsky.social
Software Engineer of about about a decade. Polyglot that loves learning new languages. Current obsessions: Rust, Elixir, OCaml
And it will read from SQS and emit events when the number is found.
June 26, 2025 at 3:37 AM
And it will read from SQS and emit events when the number is found.
I skimmed the first 2 sentences of the very first message, and replied to the thread: “my team worked on this, this is already handled, I will merge it tomorrow”.
For some reason this is making my stomach turn.
For some reason this is making my stomach turn.
June 26, 2025 at 3:33 AM
I skimmed the first 2 sentences of the very first message, and replied to the thread: “my team worked on this, this is already handled, I will merge it tomorrow”.
For some reason this is making my stomach turn.
For some reason this is making my stomach turn.
Watched a whole conversation like this happen while away from my computer today, practically LLMs talking to each other.
It was regarding something my team had worked on, and 2 uninvolved leaders were spitting out buckets of outlines and approaches like they were getting paid by the word.
It was regarding something my team had worked on, and 2 uninvolved leaders were spitting out buckets of outlines and approaches like they were getting paid by the word.
June 26, 2025 at 3:32 AM
Watched a whole conversation like this happen while away from my computer today, practically LLMs talking to each other.
It was regarding something my team had worked on, and 2 uninvolved leaders were spitting out buckets of outlines and approaches like they were getting paid by the word.
It was regarding something my team had worked on, and 2 uninvolved leaders were spitting out buckets of outlines and approaches like they were getting paid by the word.
Why should I take the time to carefully digest the words you’ve mindlessly generated, only to realize after reading it, that it could have been conveyed in 2 sentences or a quick call, rather than 8 paragraphs of LLM markdown.
June 26, 2025 at 3:30 AM
Why should I take the time to carefully digest the words you’ve mindlessly generated, only to realize after reading it, that it could have been conveyed in 2 sentences or a quick call, rather than 8 paragraphs of LLM markdown.
It devalues words in general, it’s changing how I read content and I hate that. Being intentional and concise about how you communicate, especially in technical conversations, respects the person on the receiving end as well as their time.
June 26, 2025 at 3:29 AM
It devalues words in general, it’s changing how I read content and I hate that. Being intentional and concise about how you communicate, especially in technical conversations, respects the person on the receiving end as well as their time.
Having a clear paradigm to explicitly handle and thus implicitly document the different data types allowed makes my heart happy.
June 22, 2025 at 1:29 AM
Having a clear paradigm to explicitly handle and thus implicitly document the different data types allowed makes my heart happy.
I work on a rails monolith and we just finally upgraded to ruby 3.3.8. The amount of places in code where we pass arguments of 3+ different varieties, just letting them bounce of walls of .try() makes my skin crawl.
June 22, 2025 at 1:27 AM
I work on a rails monolith and we just finally upgraded to ruby 3.3.8. The amount of places in code where we pass arguments of 3+ different varieties, just letting them bounce of walls of .try() makes my skin crawl.
Yeah! I honestly think Class based OO isn’t terrible by itself, but over the past decades it’s given rise to this “abstraction first” design mentality that has been deeply coupled to it. That needs to die off…
June 16, 2025 at 3:15 AM
Yeah! I honestly think Class based OO isn’t terrible by itself, but over the past decades it’s given rise to this “abstraction first” design mentality that has been deeply coupled to it. That needs to die off…
Hahah that’s very very fair…
June 16, 2025 at 3:12 AM
Hahah that’s very very fair…