How big of a problem is it that we have this crucial craft, on which we are knowingly staking the future, and almost none of its practitioners understand the fundamental tool they are using?
-
-
Show this thread
-
(For the record, I don’t place myself in the top tier re understanding of speed or anything else. I am somewhere in the middle of that gradient between the 99.9% and the People Who Really Know.)
Show this thread -
We see all this bad rhetoric claiming “system X is only 2x slower than native code therefore it’s fast”... but one must ignore rationalizations and look at the actual output, which is several orders of magnitude inefficient. Few people are willing to put 2 and 2 together here.
Show this thread -
The most common objection to these points is "we write slow software because it lets us make things faster and more easily". I agree this is the common belief, but it's wrong. If development is so much easier, why is productivity approaching 0 over time?
Show this thread -
Replies seem to be rat-holing on the old well-understood concept that software is slow. Yeah, we know, I have said that many times (and said to ignore that this time). What I am highlighting here is a deeper issue: programmers don't really know what computers are any more.
Show this thread -
Speed is one dimension of understanding that's lacking; the picture of speed in programmers' heads is 2-4 orders of magnitude too slow. It's easy to see and understand this, which is why I brought it up. But it's not the only dimension of missing understanding.
Show this thread -
To make the speed point again, for an attempt at clarity: Programmers have a picture of their computer, in their minds, that they use to figure out what to do. For 99.9%+, that picture is inaccurate: the imagined computer is 100x-1000x slower than the real computer.
Show this thread -
This will result in software that's too slow, obviously. But it also affects what one thinks is possible, what one dares to imagine to do. That is the more important part. Humans are very example-based, and if our examples are wrong, where they lead us will be wrong too.
Show this thread
End of conversation
New conversation -
-
-
I think you’re an incredible programmer and game designer. I’ve thoroughly enjoyed your imaginative and inventive games, especially the
@witnessgame. I follow you for technical ideas and inspiration. But why, oh why, do you feel the need occasionally to belittle people? -
I am not belittling people, I am pointing out an objective issue in an ostensibly scientific discipline. If what I said is untrue, show me how.
-
A basic requirement for being a serious engineer is the ability to tell the difference between emotional communication and technical communication, and to compartmentalize them.
-
There we go with the dig. I feel many people, including me, could learn a lot more from incredibly clever and accomplished programmers like yourself if the tone were just a little friendlier. I believe tech discourse too often becomes aggressive.
-
It's not a dig. If you insist on interpreting things that way, that's on you. Sorry.
End of conversation
New conversation -
-
-
it's bc of time and money, right? the faster our computers become, the less time and skill devs need to finish and release a product. the performance gain of a faster cpu gen is used to make _software development_ faster (and easier), not to make the software itself faster.
-
we abstract the hard parts away so development gets easier at the cost of efficiency and reliability. that kinda sucks. but it's also cool that people without a strong computer science background can sit down and write apps.
-
This is the common viewpoint, but I disagree with it. For example, development is not easier -- web development, for example, is ridiculously overcomplex and difficult for what it is. And that is the place where the most "tools" exist. Coincidence?
-
web development got harder and more complex because we drastically changed our requirements for what the web should be able to do (interactivity, instant server-feedback, etc) with the tools used (html/css/js) slow to catch up.
-
for every language, there are now thousands of "black boxes" (call them packages, gems, ..) you can knit together and call it software. that surely must be easier and faster than how we wrote software 10 years ago.
-
Why is interactivity supposed to be hard? Computers have been interactive since home computers in the 1980s. About black boxes, if it is surely "easier and faster" then why are we so bad at making software today?
End of conversation
New conversation -
-
-
Question: Do most programmers believe computers are faster than they really are or slower than they really are?
-
Most programmers believe computers are way, way slower than they really are, by like 100x or 1000x.
-
Most users believe this too, because they've only ever used horrible software.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.