4 ms·
In theory yes, but at the same time, are we as software developers really more time-efficient as we used to be? I mean I'm still writing CRUD software ten year
by Cthulhu_ 6y ago
In theory yes, but at the same time, are we as software developers really more time-efficient as we used to be?
I mean I'm still writing CRUD software ten years later; the tools have changed from idk, jquery mobile and php to React and go, but I don't feel any faster doing it. I want to say that things like form validation are faster and easier now, but no, they've just been reinvented a few times with changing underlying technology. I want to say that they solved the ORM problem, but nope, still crap, and again because of having to re-invent the wheel for a new language, environment, and generation of developers. Did the existing tools and languages improve much? Also no, at least not that I know of, still wouldn't use Hibernate if I can help it.
So in many ways things feel like they have advanced, but at least speaking for myself, at the same time things feel like they are still the same.
At least for the moment my Go application recompiles / restarts much faster than the old Java / Spring applications I used to work with. Which puts it on par with the PHP experience from before that.
- keyle 6y agoThis is a very good point. In many ways I feel we're optimizing complexity without solving any old problems. We invent new problems to solve, and we do solve them, but still are left with the same old problems.
- ksec 6y agoWhich basically sums up what Alan Kay describe as Reinventing the Flat Tires. And it felt especially true in the field of Web Technologies. >at the same time things feel like they are still the same. In the past few years I have always felt things are far too complex. We just didn't make anything simpler.
- deergomoo 6y ago> I want to say that things like form validation are faster and easier now, but no I’d actually say forms are more of a pain in an SPA than they are with server rendering. You have to track the state of every field so input doesn’t get clobbered on a re-render, which isn’t difficult but can be pretty tedious, especially if it’s a very dynamic form. And if you want native input attributes like `required` to work you need to still do a native form submission, but then intercept it and do your AJAX request or whatever instead. The only part that’s really easier is handling server-side validation errors, because instead of trying to re-construct the populated form using the submitted input, you can just leave it all on screen.
- Agentlien 6y agoThis is what I see and hear from web developers all the time. It sounds terrible. As a graphics programmer I feel things have moved very far in the right direction within the last ten years. I used to write generic computations disguised as pixel rendering without any decent tools for diagnostics or profiling. Now I can just use a compute shader and if I want to debug or profile it there are so many great alternatives. I recently re-implemented a particle simulation I first wrote in 2011. Without access to the pervious code. The first time around it took me months. Now it took me days. Sure, I've learned a lot since, but a lot of the speedup was just from better language and tool support for what I wanted to do.