I believe this is worthwhile long range target that we can build up to on solid foundation, such as component oriented software. As the pieces come together, the harder fought wins that use and prove its foundation early on will pay off greater, later.
Fair.
She did a year of com sci. She learned SQL at work. She can Excel with the best at her bank, with some VBA here and there. Still I had to coax her into learning Python for some bigger-than-Excel datasets. She wanted to for ages but just couldn't make the leap to "real" programming (her thinking, obviously not true).
Even when she tried we had issues installing things. She made good progress and almost got it. I sat an evening with her and we solved the issue. She had a lot of support to get over the various hurdles, support many don't have.
Obviously it's one data point but it highlights the issue. I think we've forgotten how hard it can be. Anything that helps should get a shot.
Programming math is high school stuff, but imperative programming is bullshit. Memory leaks. Exceptions. Callback chaining. Asynchrony. Model-change listeners. Spooky action at a distance. Legacy interfaces.
Functional programming fixes all that.
Programming excel is college stuff. RDBMS is bullshit. JOIN pain, batching vs caching, ORM, pressure to denormalize for performance at scale, eventual consistency at scale. Non-RDBMS solutions generally make sacrifices regarding ACID vs consistency vs performance. Bullshit.
Immutability in the database fixes that too.
https://www.native-instruments.com/en/products/komplete/synt...
There may be other specific problem domains where subject matter experts may be able to be productive, if given relatively basic programming tools along with specific, modular, abstractions useful to their problem domain.
I could see drone programming becoming something like this - a farmer may need to update his drone behaviour every day, but he may not be excited about learning to 'program' it.
They do some other full time job and can't invest 2000 hours per year for 5 years to become efficient at all the detailed things the programmers have to deal with.
The use case is people who can excel at Excel, but don't want to learn about dependency injection, semantic versioning, exception handling etc.
There is a large gap between what professional programmers are expected to know and the minimum skillset needed to write programs that are useful for one specific task. Many people in your typical office would benefit from the ability to (partially) automate some of the tasks they do every day. Implying that they have to invest countless hours to learn how to do that is part of the problem.
When I switched back to a shell after 20 years I realized how much a GUI hurts, how much I unlearned to work with computers. After decades of Windows and OSX, I got Arch with i3 (so no desktop environment). I am mainly using text-based software like the shell, bash, tmux and vim every single day. Then, it's a very small step to program or to get a programmer because you are already programming in little steps here and there and every day (bash scripts, vim macros, etc.) and you deal all the time with text.
Visual tools don't teach you to code, they introduce an unnecessary layer and create an even bigger insecurity when dealing with real code. Real coding with text is quite easy—and this should be the actual message. A very good example for an educative text-based coding environment which is even functional is Logo. But again, the best way to get into coding is to get an OS on your personal computer which focuses on the shell.
A story I've told before is my mum and the software that comes with her digital camera. This software is everything to her, if she want to back up the pictures she uses this software, if she want to print them she uses this software, she has no idea that the individual photos are just files on a disk. So what happens when she get's a new camera from a different manufacturer? Her knowledge is back to square one and she has to relearn all over again, this is what infantalising users has lead to.
Also, whether photographs or anything else use files stored in hierarchical directories is a historical accident. There are alternatives to file systems. For example, Squeak doesn't have files, hierarchically organized or otherwise, just persistent objects. EROS also took that approach.
I disagree. The main benefit of a visual tool (if implemented correctly) is that it exposes the constraints and the tool grammar to the user when implementing and not only when compiling.
The difference is more or less of that with clay, and lego blocks. Yes, you can design a house with both (Lego house). Clay offers an infinite shape grammar, but if all you want is a lego house, then Lego blocks are much faster.
Now, is the visual tool a cognitive crutch, or a bicycle for the mind, is another matter entirely.
https://blog.codinghorror.com/separating-programming-sheep-f...
I think this has rather psychological reasons. There is a good book from Seth Godin called 'The Dip' which deals with the problem why most are fast in prototyping but not able to transform a prototype to an actual implementation ('to stick to the end'). However, I think there is nothing wrong with a prototype to fully-implement rate of 100 to 1. Prototyping is how people learn as well.
Moreover, I am not saying that GUIs are per se bad. If I create vector-based graphics I need a GUI, when I browse the web I prefer HTML/CSS and a GUI's smooth scrolling over a text-based Lynx. Some programming languages like Java are better with GUI-IDEs but my main point was another one: That too much GUI in your daily life creates an unnecessary intimidation towards programming (if you are not a programmer yet).
That's a problem with this particular set of tooling then. In the past we've had drag'n'drop tools like visual basic which made rapid prototyping easy and you'd use the same tools for the final version. On the text side you've got similar tools like Qt and Gtk which allow you to slap together a prototype quickly and then use them for the final application. I always assumed react was quite similar.
The solution for this is simple, really: simply declare the prototype the working implementation, and put devs on the hook for maintaining it.
Lots of people can't code, and most programmers can't code well, yet very few people have been exposed to visual programming tools.
I'd look elsewhere for explanations:
(1) If those with more aptitude for programming are more likely to become programmers, and the demand for programmers increases, programmers with less aptitude have to be hired. (And the problem is made worse by excluding experienced older people when hiring.)
(2) Whatever the reason, very few women become programmers now compared to the past, so almost half the population is being excluded.
(3) There's less diversity in software now. There's only two operating systems (with the same user interface), and only imperative languages augmented with object orientation, mostly with C syntax, so programmers only learn to think in one way.
(4) Personal computers nowadays are basically appliances which you can just use without programming, and that's what most people do. When they first became available, there was very little software on them and a far greater incentive to learn to program so that you could make them usable. For many people back then, programming became an end in itself.
> Visual tools don't teach you to code, they introduce an unnecessary layer and create an even bigger insecurity when dealing with real code.
There are different kinds of visual tools. Some visual tools (like, if I'm not mistaken, Bubble) are code generators so aren't designed to teach you how to code. Others are programming languages in their own right with no textual substrate, so there's no extra layer.
It isn't as if you need visual tools to introduce unnecessary layers anyway. There are now frameworks and other unnecessary layers, which of course mean you need more programmers to handle the additional complexity, and then you have problem (1). If the software industry designed aircraft or bicycles, you'd never be able to rotate your plane or ride your bike uphill.
> Real coding with text is quite easy
No it is not. Programming is hard however it's done, even visually. Concurrent, type-safe programming is even harder, and it's here that visual dataflow programming would help. MIMD programming is problematic in textual languages because there's an explicit ordering of operations, and there are synchronization issues which have to be addressed. Switching to the dataflow paradigm avoids this, but dataflow is difficult to express in text. Also, textual languages make type inference and code optimization harder.
> A very good example for an educative text-based coding environment which is even functional is Logo. But again, the best way to get into coding is to get an OS on your personal computer which focuses on the shell.
I agree with you about Logo. But Logo originated and was closely associated with the Lisp community centred around MIT, which had a very different way of doing things from Unix approach you seem to favour: a listener instead of a shell, multiple windows, and a programming language very closely integrated with the operating system.
There were lots of people who can build small to medium complexity apps in Visual basic in those days when VB5/VB6 was active (Pre C#/.net). Even as a developer I was happy to hack in VB any day than VC++. But any developer I knew back then wouldn't touch VB, claiming multiple reasons ranging from "not powerful", "no performance", "messy" (don't know what that means) etc. It was like developers wanted to be associated with complex languages in order to have a respect among the community. True, VB performed slower than VC and even lacked few capabilities (like you can't write a device driver or difficult to write a custom COM component etc), but it was perfect for writing business applications.
Not sure what destroyed VB, but I believe it was the web that changed everything. Java and .Net though are well designed and powerful, but they bring a lot of complexity, requiring new developers to spent considerable time to gain even a basic knowledge. With the advent of SPAs things went even worser, current SPA frameworks like React and Angular are adding layers upon layers of complexity to build some basic stuff.
IMO if you can hack a UI in a prototype tool like Balsamic, then you should be able to make it a working prototype within at least 2-3x the time you took to prototype it, including binding dynamic data from a web service. If in 2017 we are still taking 3-4 months to build a basic website (dynamic) or mobile app, we have failed somewhere.
Projects like Bubble are providing stepping stones towards a possible future where we can build UIs almost as fast as we can imagine/sketch them in a prototyping tool.
Try "thinking and communicating clearly and precisely" the process of multiplying two numbers larger than one thousand, in Roman numerals.
For me, it was very difficult if I didn't cheat and implicitly convert everything in my head to normal (Hindu) numerals first.
Now, try to do the same thing with Babylonian numerals (base-60).
(I tried and gave up)
What I'm trying to illustrate is that the tool you use to express an idea, imposes a hard limit on how "clearly and precisely" you can think about that idea in the first place.
Hindu numerals are one tool (one notation) that make processes such as multiplication and division easy to express. If such tool wasn't invented, we'd be spending too much time 'thinking' and 'expressing' and 'teaching' multiplication, and be left with too little time to actually benefit from it.
I’d like to point out that 100k is not a lot in this market. Dev tools are an 11 figure market with tens of millions of programmers. I think the biggest change is the surface area has grown so much that the failed visual tools of yesteryear might have been able to carve out sustainable markets today. Bubble, Webflow, and Square Space can all be succeess stories but that doesn’t mean they’re a bellweather for all of coding. There are clearly a lot of small problems (simple web apps) business needs solved that are simple enough for these tools. I say hallelujah! Now I don’t have to update the pricing page every 3 days and can work on the real problems! The only caveat is to keep everyone in their swim lanes and don’t let the wise Bubble intern shard my database.
The biggest issue are always the skills required to bring their ideas into actual code. Most of those tools still require an extremely advanced knowledge of calculus, DSP theory and linear algebra. Imagine if a fashion designer wanted to display a set of generative images displayed in the background following the catwalk ground vibrations (this was a real request). Even if he/she could accurately describe their idea, that would be still several magnitudes outside their STEM Skills. Most of the times we end up hiring an external dev who will be forced to use such visual tools, making his job even worse.
You might be right, but they're still making over $1mm/year in revenue.
The fact is that if you can think and communicate precisely enough to describe your ideas then you can enter them into a computer fairly easily in a language like python or basic. If you can't then no matter how fancy your tools are you still need something intelligent (currently a human programmer) to pull the idea out of you and encode it.
Stuff like this isn't useful to people who are incapable of programming and is just a highly coupled mess that can't be easily automated and version controlled.