4 ms·
What you need is a speed bike that lets you switch to a mountain bike when you decide you need/want to go off the trail. That is, a "no code" or graphical or w
by AnimalMuppet 7y ago
What you need is a speed bike that lets you switch to a mountain bike when you decide you need/want to go off the trail. That is, a "no code" or graphical or whatever whizz-bang tool that lets you drop into C++ or Python or Lisp or whatever when you need to.
And to do this, it needs to be better than JNI in Java. It needs to be able to have something better than a gouge-your-eyeballs-out-ugly syntax for interfacing to the "real" programming language.
- weiluen 7y agoI’ve found that most no code environments that I’ve tried advocate that they have this capability but in practice it’s still nearly impossible to get what I need because their abstractions aren’t at the right level. Not saying this is impossible just that my personal experiences have made me skeptical of this approach.
- asdfman123 7y agoI mean, that's pretty much how I program things. I start new web apps with an MVC framework that auto-generates new pages. When I want to do something, I try to use someone else's code as much as possible. If I'm doing a simple, well contained task, someone else has already thought of it and made a library for it. If I need to send an email, I just do something like calling _emailSender.SendEmail(message). Easy peasy. But processing data is complicated and nothing can completely abstract it away.
- paulie_a 7y agoI am a lazy programmer in that way. I'd rather autogenerate and use robust libraries as much as possible.
- asdfman123 7y agoIt's not lazy, it's just smart. The less code you write, the better it is.
- spacechild1 7y agoThis is what I get from Pure Data (a graphical audio programming language). Once things get too unweildly, I write a C/C++ extension or Lua script.
- z3t4 7y agoI think the abstraction layers are important, they should not be leaky. You shouldn't have to go up/down the stack. If you can't build what you want with one tool, then choose another tool.
- cgrealy 7y agoCouldn't disagree more. Unless your job is unbelievably trivial, you should use a range of tools and use the best one available for the task at hand.
- z3t4 7y agoLets say you call for pizza, but you need to know how to bake in order to use their self help service, then that's a leaky abstraction. As high levels of abstractions it's OK to only know the name of the different pizzas. And the baker doesn't need a master in chemistry or engineering to operate the oven. We humans are very good at abstracting things and take most abstraction layers for granted, even though the world around us is very complicated.
- cgrealy 7y agoI fail to see at all how that relates to the question. If I order a pizza, I’m using a communication channel (phone, internet) to place an order; one tool. I deeply hope the pizza place is using chefs and an oven to make the pizza; completely different tools. If I demanded the pizza chef make the dough, slice the ingredients, and bake the pizza with just a stand mixer... that’s just dumb. Use the appropriate tool for the job and use the right level of abstraction at each step.
- dscpls 7y agoYeah while I think one of the hardest parts if a software developer's job (working at multiple levels of abstraction), that's literally the job. You're translating between the business and the sillicon. By all means restrict yourself to assembly but yhe rest of us will get more done by using things at convenient levels of abstraction for those specific units.