116
I Am Happier Writing Code by Hand (www.abhinavomprakash.com)
top 27 comments
sorted by: hot top controversial new old
[-] newthrowaway20@lemmy.world 1 points 1 hour ago

Journey before destination.

[-] erebion@news.erebion.eu 3 points 5 hours ago

If you automate all aspects of your life, what have you got?

[-] floquant@lemmy.dbzer0.com 11 points 8 hours ago

Whenever I'm learning a new resource/concept and pull up the example code, I have the habit of typing it out instead of copy-pasting. Is it slower? Definitely. But it does make a big difference in actually understanding what you're doing

[-] termaxima@slrpnk.net 3 points 6 hours ago

As always, the process matters more than the result.

[-] Kolanaki@pawb.social 1 points 4 hours ago

How do you compile it? Do you stick the paper in the CD tray?

[-] into_highest_invite@lemmygrad.ml 3 points 8 hours ago

i hear rumors that as many person-hours are spent cleaning up the messes left by LLMs as are saved having them write the code. has anyone found that to be true or am i just talking out of my ass?

[-] sip@programming.dev 2 points 7 hours ago

imo more. just a hunch

[-] GiorgioPerlasca@lemmy.ml 38 points 20 hours ago

Writing code is only the tip of the iceberg. You actually have to:

  • understand how the company works
  • understand the use case you are managing and how it relates to other business flows
  • understand strenghts and weaknesses of the technologies, libraries and frameworks involved
  • decide which one to use and how
  • thinking about all possible corner cases, evaluating their frequency and importance
  • only at the end, write, test, optimize the code

While large language models can help in the last step, they are very limited in previous ones, except working as a search engine on steroids.

[-] Solumbran@lemmy.world 8 points 18 hours ago

More like a search engine on LSD.

AI results are always shit when trying to find anything not completely obvious. You end up more often than not with an hallucinated reality that has absolutely no value.

[-] FishFace@piefed.social 0 points 9 hours ago

No, AI results can be quite good, especially if your internal documentation is poor and disorganised. Fundamentally you cannot trust it, but in software we have the luxury of being able to check solutions cheaply (usually).

Our internal search at work is dogshit, but the internal LLM can turn up things quicker. Do I wish they'd improve the internal search? Yes. Am I going to make that my problem by continuing to use a slower tool? No.

[-] Solumbran@lemmy.world 3 points 8 hours ago

"It's quite good" "you cannot trust it"

What is your definition of good?

What a recipe for disaster...

[-] FishFace@piefed.social 5 points 8 hours ago

Something that you can't trust can be good if it is possible to verify without significant penalties, as long as its accuracy is sufficiently high.

In my country, you would never just trust the weather forecast if your life depended on it not raining: if you book an open-air event more than a week in advance, the plan cannot rely on the weather being fair, because the long-range forecast is not that reliable. But this is OK if the cost of inaccuracy is that you take an umbrella with you, or change plans last-minute and stay in. It's not OK you don't have an umbrella, or staying in would cost you dearly.

In software development, if you ask a question like, "how do I fix this error message from the CI system", and it comes back with some answer, you can just try it out. If it doesn't work, oh well, you wasted a few minutes of your time and some minutes on the CI nodes. If it does, hurrah!

Given that, in practice the alternative is often spending hours digging through internal posts, messaging other people (disrupting their time) who don't know the answer, only to end up with a hack workaround, this is actually well worth a go - at my place of work. In fact, let's compare the AI process to the internal search one - I search for the error message and the top 5 results are all completely unrelated. This isn't much different to the AI returning a hallucinated solution - the difference is that to check the hallucinated solution, I have to run the command it gives (or whatever), whereas to check the search results, I have to read the posts. There is a higher time cost to checking the AI solution - it probably only takes 30 seconds to click a link, load the page, and read enough of it to see it's wrong. Whereas the hallucinated solution, as I said, will take a few minutes (of my time actually typing commands, watching it run, looking at results - not waiting for CI to complete which I can spend doing something else). So that is, roughly, the ratio for how much better the LLM needs to be than search (in terms of % good results).

Like I said, I wish that the state of our internal search and internal documentation were better, but it ain't.

[-] GiorgioPerlasca@lemmy.ml 4 points 17 hours ago

Good point. Reading the documentation of the library and the source code is often a better use of a software developer's time.

[-] kibiz0r@midwest.social 21 points 18 hours ago

In order to be effective at software engineering, you must be familiar with the problem space, and this requires thinking and wrestling with the problem. You can’t truly know the pain of using an API by just reading its documentation or implementation. You have to use it to experience it. The act of writing code, despite being slower, was a way for me to wrestle with the problem space, a way for me to find out that my initial ideas didn’t work, a way for thinking. Vibe coding interfered with that.

If you’re thinking without writing, you only think you’re thinking.

– Leslie Lamport

Yep. This what I don’t get about people who are using these spaghetti-bots. How do they figure out the right solution to a problem without actually walking around the whole perimeter of the problem?

My guess is they are not, and they’re just waiting until someone complains and they’ll get a job somewhere else and leave the mess for someone else(‘s chatbot) to clean up.

Between that and the death of open source, our industry is about to become a disaster area.

[-] BrianTheeBiscuiteer@lemmy.world 26 points 20 hours ago

Humans want to accomplish things, but business wants to get shit done. The two will always be at odds.

[-] blitzen@lemmy.ca 19 points 20 hours ago
[-] OpenStars@piefed.social 7 points 20 hours ago

Sometimes both:-P

But one is always shit.

[-] W3dd1e@lemmy.zip 3 points 13 hours ago

Reading only the headline: “why would you write code by hand? Would your fingers cramp up? How are you going to test it?”

Reading the article: “Oooohhhh.”

[-] crabsoft@gamerstavern.online 4 points 12 hours ago

@W3dd1e @codeinabox For what it's worth, a lot of pretty famous programmers did/do write code by hand. They often have an assistant of some kind do the actual typing after it's done. It can be an interesting experience.

this post was submitted on 08 Feb 2026
116 points (96.0% liked)

Programming

25415 readers
452 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS