Computer Says No
koenvangilst.nl
Computer Says No
1–10 of 48 posts
Re: Computer Says No
#2To be honest, the same applies when a developer gets promoted to team lead. I made this experience on my own that I no longer got in touch with the code written. Reasons are slightly different (for me it was a lack of time and documentation)
Re: Computer Says No
#3To be honest, the same applies when a developer gets promoted to team lead. I made this experience on my own that I no longer got in touch with the code written. Reasons are slightly different (for me it was a lack of time and documentation)
I am a scientist who rarely collaborates (unlike programmers and unlike most scientists).
When I wrote a paper in collaboration some time ago, it felt very weird to have large parts of the paper that I had superficial knowledge of (incidentally, I had retyped everything my co-author did, but in my own notation) but no profound knowledge of how it was obtained, of the difficulties encountered. I guess this is how people who started vibe coding must feel.
Re: Computer Says No
#4If your computer says No just ditch it and buy a non-Apple computer.
Re: Computer Says No
#5To an extend, AI can help with explaining what the code does. So, computer says why it says "no".
Re: Computer Says No
#6this isn’t the right way to use ai to write code at work, it shouldn’t become a black box, you should make it iterative and be precise about architecture, guide the ai carefully to maintain the code in a state that a human can instantly drop in on if needed, use ai as a keyboard extension not a blindfold
Re: Computer Says No
#7> This is a great insight. For software engineers coding is the way to fully grasp the business context.
> By programming, they learn how the system fits together, where the limits are, and what is possible. From there they can discover new possibilities, but also assess whether new ideas are feasible.
Maybe I have a different understanding of "business context", but I would argue the opposite. AI tools allow me to spend much more time on the business impact of features, think of edge cases, talk with stakeholders, talk with the project/product owners. Often there are features that stakeholders dismiss that seemed complex and difficult in the past, but are much easier now with faster coding.
Code was almost never the limiting factor before. It's the business that is the limit.
Re: Computer Says No
#8If your computer says No just ditch it and buy a non-Apple computer.
One with Windows 11?
Re: Computer Says No
#9If your computer says No just ditch it and buy a non-Apple computer.
One with Windows 11?
Do you really think Windows 11 doesn't try to control the user, or say no to them?
Are you sure you can't think of a commonly used operating system which doesn't?
Name ends with "ux", or maybe "BSD"?
Re: Computer Says No
#10> This is a great insight. For software engineers coding is the way to fully grasp the business context. > By programming, they learn how the system fits together, where the limits are, and what is possible. From there they can discover new possibilities, but also assess whether new ideas are feasible. Maybe I have a different understanding of "business context", but I would argue the opposite. AI tools allow me to s…
I think that for the average developer this might be true. I think that for excellent developers, they spend a lot of time thinking about the edge cases and ensuring that the system/code is supportable. i.e. it explains what the problems are so that issue can be resolved quickly; the code is written in a style that provides protection from other parts of the system failing; and so on. This isn't done on average code and I don't see AI doing this at all.