291–300 of 331 posts
I think the thing that "coding without code" fundamentally misses is that learning to actually write Python or Java or whatever is not the hard part of being productive in a business context. The hard part of creating useful software is that you have to understand a business process and its requirements so precisely that you can write it down for the computer to do. I work with business stakeholders creating internal…
Earlier quoted context omitted.
That's interesting. Personally, learning Django to be comfortable with it takes quite some time for me. Translating the business process to code means you have to be comfortable with the framework, no matter what you're using. What do you often you feel you're stuck on?
It's not that I get stuck. It's just that, with Lotus Notes: - authentication was already taken care of - adding a field at a particular place was one step (rather than updating a model, updating a view and running a database migration) - I could make small changes in production (ok, maybe that's not so good!!) - adding events between different Lotus Notes apps on the same server was a snap - the learning curve to be…
I am working on a product in this space. I think pretty much all the 'no code' apps that are coming out have taken the wrong approach to it. No matter what, they are still 'designed' by programmers with a programming mentality. This will lead to a sort of failure as people will feel limited when using it, and a 'non programmer' mentality looks at this and goes wtf? For example: > =Filter(Tasks,"Tasks[Done] % ORDER BY…
Earlier quoted context omitted.
Indeed, I've observed that while programming seems easy, a large fraction of people find learning to program is utterly prohibitive. This includes many really smart people. And I don't think we understand why. But here's what I think you give up if you don't have code. Over the past 70 years, one of the problems that computer science has studied is how to manage the size and complexity of programs and development tea…
> one of the problems that computer science has studied is how to manage the size and complexity of programs and development teams Did we though? Can you point out some books, or PHDs or whatever slightly more scientific and substantial than blog-post anecdotes? I honestly believe as an industry we completely don't know how to scale development and I would love to read something that helps understanding this challeng…
But I'm just thinking of something like the transition from BASIC to Pascal (which I experienced in 1983). There were rules of thumb that we learned in BASIC (avoid global variables and GOTO's) that were formalized in Pascal, and Pascal also let you create much more elaborate named structures, and control the scope of names more precisely.
That's just one really simplistic example, but it rather profoundly improved my programming. On the other hand, I can believe that scaling is still a struggle -- there is still a point where we run out of juice, but it's a lot further than you'd get with BASIC, or with Excel-sans-macros.
I think the thing that "coding without code" fundamentally misses is that learning to actually write Python or Java or whatever is not the hard part of being productive in a business context. The hard part of creating useful software is that you have to understand a business process and its requirements so precisely that you can write it down for the computer to do. I work with business stakeholders creating internal…
I think you are radically underestimating the perceived barriers to entry with programming. You sound a lot like the Linux advocates who think everyone should just memorize a bunch of commands, and get used to using shell. This type of insider view is often referred to as 'the curse of knowledge'.
1. Understand the problem
2. Break the problem into subproblems. Goto 1 till subroblems
are small enought to be tackled.
3. Develop the algorithms for each of the subroblems you got
after step 2. No handwaving allowed.
4. Implement the algorithms.
I am working on a product in this space. I think pretty much all the 'no code' apps that are coming out have taken the wrong approach to it. No matter what, they are still 'designed' by programmers with a programming mentality. This will lead to a sort of failure as people will feel limited when using it, and a 'non programmer' mentality looks at this and goes wtf? For example: > =Filter(Tasks,"Tasks[Done] % ORDER BY…
The only saving grace it has is that most of the interface is "no code" so that you can focus your training on smaller pieces... But that's just "low code" at that point, which isn't nearly as marketable.
I think the thing that "coding without code" fundamentally misses is that learning to actually write Python or Java or whatever is not the hard part of being productive in a business context. The hard part of creating useful software is that you have to understand a business process and its requirements so precisely that you can write it down for the computer to do. I work with business stakeholders creating internal…
I think you are radically underestimating the perceived barriers to entry with programming. You sound a lot like the Linux advocates who think everyone should just memorize a bunch of commands, and get used to using shell. This type of insider view is often referred to as 'the curse of knowledge'.
Low code solutions work by presenting a simplified view of the world to the user. Once your vision doesn't mesh with their abstraction, you end up having to dive under the hood if you're lucky enough to have a solution that lets you. In the best case, you've now had to learn the underlying tech and the abstraction.
Earlier quoted context omitted.
Wow, that looks great. An COSS alternative is exactly what this space needs. I wish you great success.
Thanks! I agree, was surprised to learn that there aren't that many good open source no-code tools out there.