Earlier quoted context omitted.
but does team have 1 IT/ data person? Edit: sorry I see that you are the same person I was replying to. Then to understand it better, who is consumer of so vast amount of data?
The company has 1 IT person and uses a third-party vendor for IT support. We have several data engineers and scientists, but we are not specialists as DBA or cloud infrastructure; it's just one very small part of our work.
Ask HN: Have we screwed ourselves as software engineers?
281–290 of 430 posts
Re: Ask HN: Have we screwed ourselves as software engineers?
#282Re: Ask HN: Have we screwed ourselves as software engineers?
#283The way I look at it is: there are more tools in the toolbox than ever before. Which makes our judgement (the thing they really pay us for) even more important. Kubernetes, for example, is a specific solution to a specific problem. The solution is complex but so is the problem. If k8s give you the right trade-offs for your situation, then it’s not busy work. Of course, there are plenty of project where judgement Is t…
That's a great way to describe the phenomenon.
Re: Ask HN: Have we screwed ourselves as software engineers?
#284https://news.ycombinator.com/item?id=31217253#31240227
It's roughly 3x the complexity and labor compared to the 1990's desktop-oriented IDE's like VB, Delphi, PowerBuilder, Clarion, FileMakerPro, etc.
I realize deployment (installing, updating) was harder compared to web apps, but I'm not sure it has to be either-or in terms of simplifying deployment at the expense of development. Oracle Forms seemed to do the CRUD job sufficiently without installing a new EXE for each app update. It seemed almost a "GUI browser". A state-ful GUI markup standard may help us get closer to that again.
OF was not perfect, but we should've learned from what worked well and improved upon. We threw out the productive baby with the bathwater.
We have over-focused on social media and "web scale", but ordinary CRUD still does most the real office work. Making our apps "mobile friendly" has crippled them, despite the fact most real work is done with mice. It's time to return to YAGNI, KISS, and real GUI standards. It's not about nostalgia, it's about NOT excepting the waste and bloat our current dev tools now have. "Hello World" has a zillion lines of code behind it now.
Re: Ask HN: Have we screwed ourselves as software engineers?
#285You are experiencing what I call "The Bisquick Problem". Bisquick is basically flour with some other stuff, like salt, premixed into it, and sold in a box in the USA. So instead of just buying flour and salt, you buy them together, which makes some things easier (like making pancakes), but it complicates literally everything else. You can't use it as flour, or as salt. With software, the problem is even greater. You…
Re: Ask HN: Have we screwed ourselves as software engineers?
#286Earlier quoted context omitted.
With extensive experience in this vertical, (marketing agency and analytics), 200GB is a _partial_ day for one datasource, let alone table or total DB size.
but does team have 1 IT/ data person? Edit: sorry I see that you are the same person I was replying to. Then to understand it better, who is consumer of so vast amount of data?
Re: Ask HN: Have we screwed ourselves as software engineers?
#287I generally agree, but two things I'd like to point out. If you're using python for the web you're already part of the complexity problem, atleast from the perspective of someone deploying php 15 years ago. I use python for web development, and I love it, but deploying webpages used to be copy an apache config and ftp/scp your files to some location. Now we need app servers and reverse proxies, and static files are s…
> If you're using python for the web you're already part of the complexity problem, atleast from the perspective of someone deploying php 15 years ago. The problem with deploying PHP is that it immediately gives you something for very little effort, but the effort scales incredibly disproportionately once you outgrow your need for the bare functioning minimum. I personally prefer the "modern" approach of dropping a s…
Re: Ask HN: Have we screwed ourselves as software engineers?
#288I generally agree, but two things I'd like to point out. If you're using python for the web you're already part of the complexity problem, atleast from the perspective of someone deploying php 15 years ago. I use python for web development, and I love it, but deploying webpages used to be copy an apache config and ftp/scp your files to some location. Now we need app servers and reverse proxies, and static files are s…
> If you're using python for the web you're already part of the complexity problem, atleast from the perspective of someone deploying php 15 years ago. [...] deploying webpages used to be copy an apache config and ftp/scp your files to some location. There is a MASSIVE difference in the value proposition of a proper deployment from version control and using something like docker w/ docker-compose to facilitate runnin…
Re: Ask HN: Have we screwed ourselves as software engineers?
#289There are a few problems.
First, the gray beards that expect everyone to know "the basics" had built stuff so complex and convoluted that nobody can use it 100% correctly without their domain knowledge. It's fine, computers are complicated, but expecting everyone to keep it all in their heads is unreasonable. So people buried that stuff below a layer of abstraction, but that didn't solve the fundamental problem and so even these higher level tools are convoluted and cumbersome.
Then, you've got the people doing this on purpose to ensure that they are unfirable. This is pretty self explanatory, but there's a perverse incentive to overcomplicate your job so you come off as indispensible, it's like CIA and wall street lingo but for devs.
Of course I'd doesn't help that many people just go along with it for a paycheck.
You've got people that want to sell their cool shiny thing as a solution to anything and everything, who cares about the consequences. Everyone knows that these decisions ripple through time, but they don't care about that.
And finally, there's the guys that just don't know what they're doing, bit off more than they can chew, are in over their heads.
All of this leads to miles of technical debt, an industry made of it, increasingly unusable systems that require teams to understand and maintain.
I don't know that there is a solution. I don't know that it could happen any other way. But I do know that regardless of that, these systems cannot stand the test of time when built this way. If you want a future where computers serve humans and are ubiquitous, this path won't get you there.
Re: Ask HN: Have we screwed ourselves as software engineers?
#290Wait until it breaks one day and no one can understand it enough to fix it !!!