Abhinav Sarkar
@abhin4v.bsky.social
Programming languages aficionado, occasional runner, quantified-self enthusiast, and fervent napper. Works as senior software engineer at Google. Also at @abnv.me.
#programminglanguages #software #running #Haskell #NixOS #photography #quantifiedself
#programminglanguages #software #running #Haskell #NixOS #photography #quantifiedself
Reposted by Abhinav Sarkar
functional programmers never beating the “mostly write compilers” allegations
September 10, 2025 at 10:48 AM
functional programmers never beating the “mostly write compilers” allegations
Reposted by Abhinav Sarkar
Once again, the problem is that people ignore all of the invisible costs of vibe coding:
- prompting (specifying what to do *takes time*)
- learned helplessness
- constantly interrupting their own flow state
- babysitting rules files
- reviewing the LLM's output
- fixing bugs introduced by the LLM
- prompting (specifying what to do *takes time*)
- learned helplessness
- constantly interrupting their own flow state
- babysitting rules files
- reviewing the LLM's output
- fixing bugs introduced by the LLM
July 21, 2025 at 3:32 PM
Once again, the problem is that people ignore all of the invisible costs of vibe coding:
- prompting (specifying what to do *takes time*)
- learned helplessness
- constantly interrupting their own flow state
- babysitting rules files
- reviewing the LLM's output
- fixing bugs introduced by the LLM
- prompting (specifying what to do *takes time*)
- learned helplessness
- constantly interrupting their own flow state
- babysitting rules files
- reviewing the LLM's output
- fixing bugs introduced by the LLM