this post was submitted on 21 Nov 2023
19 points (85.2% liked)

Programming

17429 readers
75 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 [email protected]



founded 1 year ago
MODERATORS
top 5 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 11 months ago

Very weird example to me, with the LLM chatbot video. Like, yeah, interacting with an LLM can be interesting, but you're not going to learn anything meaningful about it.

And when I jumped into the middle of the video, that looked pretty much exactly as I expected, too. The guy was tweaking the pre-query and then chatting with the chatbot to see how it turned out. So, they didn't do/learn much coding either.

There is all that surrounding technology, which you are inevitably going to learn something about, but ultimately this is what I find so tiring about LLMs. I can learn something about the surrounding technology and tackle a topic which is meaningfully interesting at the same time. Unless I had a problem which a custom adaptation of an LLM could solve, why would I choose to play with it?

[–] [email protected] -5 points 1 year ago (2 children)

Focusing beyond the code - as a developer you will code 20% of your time.

Doesn't sound like a great software engineer to me

[–] [email protected] 10 points 1 year ago (1 children)

I'm not sure about the exact percentage but I don't think it's necessarily that far off. I spend a lot of time reviewing code, designing, documenting, reading documentation. Actually writing code is a cherry on top.

[–] [email protected] 4 points 11 months ago

Yeah. As a manager of developers, I don't want my team to spend their time producing code.. I want them to spend their time solving problems.

[–] [email protected] 7 points 11 months ago

If anything 20% is on the high side, for experts working in difficult (profitable) domains.

When we pointy-haired-bosses are doing our job right, producing new code is a much lower priority in the software engineer's day, behind understanding and maintaining the important code that is critical to the objectives of the organization.