6 ms·
While Eve is an interesting problem, the main issues that makes programming hard are the same thing that makes law hard: 1) Specifying something in an unambigu
by RcouF1uZ4gsC 9y ago
While Eve is an interesting problem, the main issues that makes programming hard are the same thing that makes law hard:
1) Specifying something in an unambiguous way.
2) Knowing what assumptions you are making.
3) Anticipating contingencies.
Read a contract or the tax code. Even though they are using English (in the US), it requires an advanced degree to be able to craft such legal documents well.
It is the same thing in software. No matter how easy and intuitive you make the language and environment, you will still run into those 3 issues, and it will require dedication, training (whether formal or informal), and time to make a great programmer.
- nightski 9y agoAgreed, it's hard and it takes a certain type of person to be effective at it. I'd go a step further and say that tools designed to make programming "easier" or for the masses not only are a wasted effort but actually detrimental (I'm not taking about learning environments such as MIT Squeak here, that is altogether different). We need better tools that let someone who masters programming to take their vision and realize it in production ready code as quickly as possible. This is a very different goal from "allowing a newbie to pick up a programming language in 15 minutes". I desire master tools. Tools that I know if I invest the time to learn (whether that takes months or years) will allow me to achieve unparalleled productivity as a programmer.
- dman 9y agoI dont think we will get better tools until we as an industry get ready to pay for them.
- paulhodge 9y agoYeah, people talk about necessary complexity vs unnecessary complexity. "Unnecessary complexity" is all those arcane coding rituals that we do, that our users don't know or care about, but we have to do because our current tools demand it. We can't get rid of necessary complexity and so we probably can't design a programming interface for someone that is completely illiterate in math & logic. But what we can do is 1) Eliminate unnecessary complexity, and 2) Provide helpful, structured, interactive, learnable tools, which help guide the author as they do all the "necessary" steps. If we just did that then that would be a huge improvement from the state of the art.
- anewhnaccount2 9y agoHence the name of the Eve blog, http://incidentalcomplexity.com/ http://incidentalcomplexity.com/
- flukus 9y ago> "Unnecessary complexity" is all those arcane coding rituals that we do, that our users don't know or care about, but we have to do because our current tools demand it. What exactly do you mean by this? I can think of many things that fit this description but none that don't have good reasons to exist or remain.
- netheril96 9y agoWebpack config?
- flukus 9y agoCorrect me if I'm wrong because I'm not familiar with it. But isn't that a way to declare dependencies and share the information with other developers? That's something that has a good reason to exist. Replacing that functionality would involve a way more complicated solution to the same problem.
- TeMPOraL 9y agoEveryrhing depends on the scope. Webpack is a complicated tool solving a complex problem, which makes it useful in large projects. But it's also way overcomplicated and unnecessary for small projects. A lot of incidental complexity comes from misapplication of powerful tools to simple problems.
- acemarke 9y agoFWIW, Webpack 4 will have "zero-config" defaults set up out of the box: https://github.com/webpack/webpack/releases/tag/v4.0.0-beta.0 https://github.com/webpack/webpack/releases/tag/v4.0.0-beta....
- cardigan 9y agoAn upper bound to the amount of information you need to transmit to have something built the way you want it built is how much you need to tell a good developer about what you want made before it is made to a satisfactory degree. And an upper bound to how long it can theoretically take to build something is the same as the time to transmit that information for a human plus some small epsilon: computers can run very fast. So getting a computer to do what you want ideally should not be close to as slow and difficult as it is today. This is sort of the true goal, rather than formally specifying what you wish the computer would do. If you believe the goal is formally specifying what the computer does on top of bulletproof abstractions, we're already very far away from that - programmers today don't tell a CPU how to do branch prediction, or a compiler how to optimize their code, for instance. Probably a really good system could do even better than the upper bound above - what if you knew what someone wanted before they could even describe it to you, and you built that for them?
- indubitable 9y agoAnother good example of the issue here is any programming language that was meant to be able to be read/used by non programmers. SQL is a great example there in my opinion. The syntax and structure is clearly meant to try to mimic relatively natural language, yet in practice I think SQL is vastly more challenging and complex than most any programming language intended to be used by programmers. Of course this goes all the way back to all the programming language that used to be used around the time of SQL's development, such as things like COBOL. They're just really tough to work with, even for those of us who learned it as one of our first languages. Anecdotally at least C structure languages now feel 'natural' to me, whereas the natural language programming languages always felt (and feel) like trying to fit a square peg in a round hole.
- dragonwriter 9y ago> The syntax and structure is clearly meant to try to mimic relatively natural language, yet in practice I think SQL is vastly more challenging and complex than most any programming language intended to be used by programmers. I don't; and the fact that I've known plenty of people who are not programmers before and do not consider themselves such afterward who have picked up SQL fairly quickly seems consistent with it not being that much of a barrier. I think SQL had some design decisions that are particularly frustrating to programmers who are familiar largely with currently popular general purpose languages, though.
- lucozade 9y agoI find SQL to have a usage profile that's, not surprisingly, similar to other declarative languages. Then tend to have a sweetspot of functionality that, if you stay within, makes them very easy to use even for less experienced people. But outside the sweetspot, things tend to go south very rapidly and you end up needing detailed implementation knowledge that the language will fight against.
- QuantumAphid 9y agoSQL as a language is simple and easy. It's applying it properly for a relational algebra of a database which makes it far more complicated.