News for hackers. Stuff that matters.
Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @01:24PM (#31226801)
90% of my software engineering is fighting with incomprehensible framework magic to automates simple tasks that don't need to be automated, to "save me" from just writing some simple code. It's literally rube goldberg all the way, the most over complex contraptions to achieve the simplest of tasks.

"You don't want to write "raw" html/js/sql/Java" Uhm I thought that was my job.

Re:90% of software engineering done today is integrating poo... by twblalock on Sunday May 01, 2022 @04:13PM (#31228248)
> "You don't want to write "raw" html/js/sql/Java" Uhm I thought that was my job.

It's not your job, any more than a firefighter's job is to be a hose operator, or a nurse's job is to be a syringe operator.

Your job is to produce software that meets the requirements of the business, as a member of a larger engineering organization which needs to be able to function well enough to deliver that software.

Why are frameworks popular? Because they provide a standardized way for multiple engineers, and multiple engineering teams, to collaborate effectively on the same product -- and they make it easy to hire people who already know the frameworks.

If everyone is writing "raw" JS/HTML/SQL/Java/whatever, they are actually building their own individual, unstandardized frameworks.

That's not good for supporting software when the author leaves, and it raises the barrier enormously for onboarding new people. Above a certain scale it's just not workable.

You can be cynical about this and say that it reduces engineers to interchangeable cogs in a machine. Or, you can understand why things are the way they are, understand how to succeed in this reality, and build a fulfilling career path for yourself by providing value that a mere cog cannot. I've worked with a lot of successful, happy engineers who are not cogs, and what separates them from the others is not coding skill -- it's that they all understand this reality.

Re:90% of software engineering done today is integrating poo... by wackget on Sunday May 01, 2022 @05:09PM (#31228692)
> If everyone is writing "raw" JS/HTML/SQL/Java/whatever, they are actually building their own individual, unstandardized frameworks.

That is only "technically" true, in the way that if you develop any kind of sufficiently complex program then you will have, by necessity, built something which could be called a framework.

Realistically, though, your point is invalid and misses the mark.

To say that programmers shouldn't write pure code without an existing framework is akin to saying that a house builder shouldn't use bricks and lumber to build a house; they should buy a pre-fab kit instead. Which is, of course, nonsense unless you want the shittiest quality most generic house possible.

Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @05:26PM (#31228833)
> then you will have, by necessity, built something which could be called a framework.

What they call "building your own framework" is simply what I think of as programming. You design a program, it will have a structure. Why is that "forbidden" and something that programmers are thought of as unable to do?

Re:90% of software engineering done today is integrating poo... by mattgreenrocks on Sunday May 01, 2022 @07:52PM (#31229874)
Because many (not all) devs use frameworks to cover for their own weaknesses in software design. There’s something deeply comforting in the faith that a few Very Smart Framework Authors have laid a gold-plated path of success for them to follow.

What they overlook is the time and energy wasted in the framework cottage industry: making dependencies talk to one another, aligning version numbers, major version upgrades being forced on them (or risk being insecure) and the time spent searching Google, SO, and GitHub issues for support.

Re:90% of software engineering done today is integrating poo... by ryanbrunner on Sunday May 01, 2022 @08:11PM (#31230009)
This really doesn't ring true to me. The biggest value of frameworks in my mind is that I don't have to waste time doing software design for things where my solution has no reason to be unique. Directory structure, how I interface with the database, how I write to logs, how I route HTTP requests to endpoints in my code are all certainly things I could solve, but I'd rather spend time on things that are unique to the problem I'm solving, and accepting a perfectly suitable standard for everything else.

As a bonus, I know that every dev I hire with experience with that framework is also going to know how these things are set up, and they can focus their onboarding time on what actually needs to be unique to the problem we're solving.

Regarding the downsides:

- a framework doesn't necessitate additional libraries any more than rolling your own does (arguably this is worse without a framework, because unless you don't use libraries altogether you have a hodgepodge of libraries to solve common problems that don't have a lot of incentive to be cross-compatible, and a framework really can't be incompatible with itself)

- Any half-way popular framework is going to ship security updates for past major versions (and again, if you're using libraries this is more of a headache than updating a single framework)

Re:90% of software engineering done today is integrating poo... by nh23423fefe on Sunday May 01, 2022 @09:38PM (#31230517)
Agree. I've never seen a poor dev reach for a framework to solve a problem. Poor devs do nothing for days and then ask a bad question at a stand up.
Re:90% of software engineering done today is integrating poo... by scarface74 on Sunday May 01, 2022 @11:56PM (#31231296)
I would much rather waste my time on a well documented industry framework that I can use when I leave than learning a framework written by the architect astronaut because he thought his problem was a special snowflake.
Re:90% of software engineering done today is integrating poo... by Tabular-Iceberg on Monday May 02, 2022 @04:02AM (#31232467)
> because he thought his problem was a special snowflake

I think this is the heart of the issue. Of course everyone thinks their problem is a special snowflake, otherwise they wouldn't invest resources into solving it. The job of us developers is to distill the essence of it and generalize the rest. But it's something I've always struggled to communicate with the business side. Either I "just don't get it", or they take generalization to mean I want to drown them in configuration.

Re:90% of software engineering done today is integrating poo... by hadlock on Sunday May 01, 2022 @08:36PM (#31230153)
Because someone else is going to come along behind you and need to maintain what you wrote. If you're using a standard, just about anybody can sit down and pick up where you left off within an hour or two
Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @03:52AM (#31232419)
> If you're using a standard, just about anybody can sit down and pick up where you left off within an hour or two

Yeah it just doesn't work that way, you need to understand the domain and understand the system, and it takes a while to learn in a new job. This is just a fact, for every job, also software engineering. Stop this weird fantasy of replaceable cogs on the assembly line, you are not henry ford.

Re:90% of software engineering done today is integrating poo... by Handytinge on Wednesday May 04, 2022 @12:50AM (#31256887)
This may have been true at one point, however new frameworks are the "standard" every few years, and the pool for anything > a junior dev depletes quickly.

Documentation or (preferably and) built in language convention are the winners here as frameworks come and go.

Re:90% of software engineering done today is integrating poo... by codedokode on Sunday May 01, 2022 @05:37PM (#31228930)
Because if you move from one project to another you want to see a familiar implementation of Request class or ORM from a framework rather than reverse engineer custom-built undocumented untested replacement for this.

It may make sense if custom framework is a magintude order better, but if it is the same as a standard framework or worse then it is not worth to spend time on it.

Re:90% of software engineering done today is integrating poo... by scarface74 on Sunday May 01, 2022 @11:54PM (#31231286)
Because your framework eventually becomes a badly written, not as widely tested version of a known framework. When you leave, it will be a lot easier to hire someone who knows React than someone who knows jseban.js.

I’ve had to come in before and deal with someone’s custom ORM or logging framework.

I’ve made the mistake myself of writing something that was a cross cutting concern and then later found out that there was a popular third party package. I replaced my implementation as soon as feasible.

Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @02:10AM (#31231917)
> Because your framework eventually becomes a badly written, not as widely tested version of a known framework. When you leave, it will be a lot easier to hire someone who knows React than someone who knows jseban.js.

Why are you assuming that everything a software engineer creates will always be bad? That's an unbelievably deprecating attitude. Do you ever see any other professions do this? UX? Product? Writers? "everything we always try to do will always be bad" and we have to try to safe us from ourselves? What?

And this "framework" would be custom made to solve exactly the use cases at hand, and nothing else by definition would be better at those specific use cases.

And why would you optimise so much for onboarding and hiring anyway, at the expense of so much continuous wasted time and less output?

When my product owner quit, the new guy was working in parallel for three months, because "of course, they have to learn the ropes". That's normal for every single job basically, except software engineering.

Why not just spend a couple of days, or a week, to give an introduction to your new hires, so that they understand and learn how you have structured your program?

The only "problem" with that, is that you have to stop acting out this farce of the computer genius with the superior intelligence, in your hiring and onboarding process.

Re:90% of software engineering done today is integrating poo... by Tabular-Iceberg on Monday May 02, 2022 @03:23AM (#31232260)
>Why are you assuming that everything a software engineer creates will always be bad?

Not necessarily, but it usually ends up badly. I have no doubts most of my peers could write a fine custom framework, but it's going to take a whole team of them at least a year to come up with something decently ergonomic, tested and documented. How often is the business side of the company going to be on board with spending that amount of resources on a solved problem?

Instead developers decide to fly under the radar and do it anyway, but then run out of steam while the framework is still an untested, undocumented prototype and the pressure to shift focus to features becomes too great to resist. And by that they have doomed the whole company to a bottomless swamp of technical debt, with seniors getting fed up and leaving, and being replaced with juniors with no clue of what's going on, making the onboarding problem magnitudes greater than it was in the first place. And if someone has the genius idea of a big rewrite, we all know where that's going, especially since the only people they have been able to retain the whole time are either inexperienced juniors and mediocre seniors, so the cycle repeats again.

Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @03:38AM (#31232344)
> I have no doubts most of my peers could write a fine custom framework, but it's going to take a whole team of them at least a year to come up with something decently ergonomic, tested and documented.

No, because they would not make a framework, it would not require all of this work, because it's not designed to be generic and reused by others.

Simply write a program. Not a framework. Has this idea been completely lost? Solve your own use cases only. Don't try to generalise it and optimise it for reuse by someone else.

Re:90% of software engineering done today is integrating poo... by Tabular-Iceberg on Monday May 02, 2022 @04:06AM (#31232492)
An abstraction doesn't care what you call it, or how many times it gets used. It still needs to be carefully designed, tested and documented, and this almost never happens in industry.
Re:90% of software engineering done today is integrating poo... by scarface74 on Monday May 02, 2022 @04:43AM (#31232671)
It’s not about the person being a “genius”. A popular framework has been well tested, written by a group of people, it’s well documented, a community has grown up around it, their are books, training videos, etc.

Would you write your own operating system or programming language because it might be better suited to solve your particular use case or use a general purpose language?

Re:90% of software engineering done today is integrating poo... by codedokode on Sunday May 01, 2022 @05:39PM (#31228942)
> What they call "building your own framework" is simply what I think of as programming.

If you want an analogy, this is like a builder claiming that he is going to make all bricks and nails himself. You don't usually write your own standard library, why would you write your own framework?

Re:90% of software engineering done today is integrating poo... by jacoblambda on Sunday May 01, 2022 @09:49PM (#31230571)
I think there's a very prevalent and very real difference between "building your own framework" and "building your own bricks and nails". Programming isn't exactly equivalent to a construction worker. Rather your team are the construction worker, the structural engineer, and the architect all at once.

The framework isn't bricks and nails. It's a prefab house plan. You follow the instructions and you get a house out on the other end. If you need to go outside what the prefab covers, you have to fight the framework because now you are drawing over top of an already printed out structural plan to try and do something different.

The equivalent of bricks and nails in SWE is using libraries. Use a library to do a thing. You still need to design the program (drawing the floor plan), formalize how the parts interact (drawing the structural plans), and actually put the pieces together (building the actual house) but you don't need to worry about the small details like how to perform X algorithm (make the bricks), write a messaging standard (make the nails), or handle the intricacies of concurrency, distributed data structures, or drawing to a user interface (making the concrete and mortar). Your libraries do that for you. All you need to do as a developer is focus on writing neat functional kernels that do "the hard stuff", wrapping all your "hard stuff" and libraries together in some OO class to implement a certain functionality, and then stringing the bits together with some imperative glue to tell all the pieces to work together. Past that is orchestration & administration and that's Ops' responsibility.

Unless all you need is cookie cutter, don't use a cookie cutter. Fighting the cookie cutter will be far harder than using the tools for the job(cleanly separated, well documented, and interoperable libraries) to solve specific problems.

Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @05:47PM (#31229015)
Except it's not like that, software is not standardised, it's custom made.

And software engineers already have their toolset. The real analogy would be telling all the builders that they now have to use those shitty multi tools that are 10 screwdrivers and a hammer all in one.

Re:90% of software engineering done today is integrating poo... by cornel_io on Sunday May 01, 2022 @07:35PM (#31229768)
For 90% of SWEs (and closer to 99% of anyone doing front-end web stuff) it really isn't that custom. You're not solving problems that are difficult except those which your team creates for themselves by making bad choices as they service the fairly routine and unexciting feature requests that come in from product. And that's not to say that is a bad thing, all teams make bad choices and have to improve them over time, even when they are using highly opinionated frameworks. It's an unavoidable part of software development, even incredible teams and devs need to refactor.

The point of using frameworks is that you can be sure that many of the bad choices the people who wrote it made early on have by now been tidied up. You don't have to worry that Dougie the intern's custom HTTP router is actually all sorts of ballsed when you go to set up your first DELETE endpoint, because Dougie didn't get to touch anything that fundamental to the stack.

I do get off the boat when it comes to leftpad and stuff like that, don't ever pull external dependencies for trivial things. But an ORM or a UI framework? Those problems have been solved hundreds of times, absolutely no need for anyone to solve them again unless you're that good that thousands will move to using your solution instead of the existing ones.

Re:90% of software engineering done today is integrating poo... by delusional on Sunday May 01, 2022 @06:21PM (#31229295)
The analogy is now officially making the argument less clear
Re:90% of software engineering done today is integrating poo... by jprd on Sunday May 01, 2022 @07:15PM (#31229671)
you are limiting yourself to typing out code, rather than what is amazing about a human brain, the ability to see coherence in random shit and improve it.

If you feel your job is to find neat ways of writing Java or C# or wtfever, you are limiting yourself. You should be looking to offload any repetitive/tedious task to automation, and from there figuring out how to leverage ML to make it efficient.

The "work" you speak of is going to be obsoleted in the next decade, if it isn't cutting edge CS theory it should be done by the machine.

Re:90% of software engineering done today is integrating poo... by xmprt on Sunday May 01, 2022 @07:07PM (#31229617)
The house building analogy is pretty good and I think that frameworks are pretty close to how house building works right now. Pre-fab is like using cookie cutter components and throwing them together into a website using something like Wordpress or Squarespace. On the other hand, frameworks are like using common tools, foundations, scaffolding, and (literally) frameworks to build a custom architectured house.

Of course, building your own home is possible but that could be a shack made up of sticks and mud or a stack of bricks and mortar with no base/foundation which can fall apart at any moment.

Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @03:01AM (#31232146)
> On the other hand, frameworks are like using common tools, foundations, scaffolding, and (literally) frameworks to build a custom architectured house.

This is exactly the problem, you are trying to use a standardised blurprint, to build a custom architectured house. Where you should probably make a choice here, either go standard or custom.

> Of course, building your own home is possible but that could be a shack made up of sticks and mud or a stack of bricks and mortar with no base/foundation which can fall apart at any moment.

Why would a highly skilled builder build a shack of sticks and mud, or a house without foundation? Why do we assume that every software developer is an incompetent clown?

Re:90% of software engineering done today is integrating poo... by rightbyte on Monday May 02, 2022 @02:26AM (#31231992)
I agree with your point but the analogy fails in that prefab house elements does not add complexity in the way software frameworks do which is the main problem in my opinion.
Re:90% of software engineering done today is integrating poo... by arinlen on Sunday May 01, 2022 @05:14PM (#31228727)
> To say that programmers shouldn't write pure code without an existing framework (...)

That's not what's been argued.

The overall thesis is that developers end up using higher-level abstractions, and between wasting time writing and debugging your custom high-level abstractions and simply adopting a feature-complete, stable, and standard high-level abstractions, you'd have a hard time trying to justify wasting time rolling your own when others already did all that work.

Re:90% of software engineering done today is integrating poo... by TuringTest on Sunday May 01, 2022 @05:28PM (#31228853)
> between wasting time writing and debugging your custom high-level abstractions and simply adopting a feature-complete, stable, and standard high-level abstractions, you'd have a hard time trying to justify wasting time rolling your own when others already did all that work.

That's only true when all the abstractions you need have already been implemented by others. Most of the time though, in addition to off-the-shelf abstractions, you need to build new abstractions which are specific to the business problem at hand; and shoehorning those abstractions on top of an existing framework which was not created with them in mind may be more work and may provide a less robust, way more complex solution.

Re:90% of software engineering done today is integrating poo... by arinlen on Sunday May 01, 2022 @07:35PM (#31229766)
> That's only true when all the abstractions you need have already been implemented by others.

Not really. More often than not, any framework already ships with far more features than the ones you'll be using, with the added benefit of already being production-ready and extensively tested not only by the maintainers but also by everyone else already using it.

When you roll your own... Well, good luck.

> Most of the time though, in addition to off-the-shelf abstractions, you need to build new abstractions which are specific to the business problem at hand (...)

You're confusing implementing higher-level abstractions which allow the low-level details to be ignored with actually implementing your own business logic.

Re:90% of software engineering done today is integrating poo... by ratww on Sunday May 01, 2022 @10:23PM (#31230771)
> You're confusing implementing higher-level abstractions which allow the low-level details to be ignored with actually implementing your own business logic.

The grandparent definitely isn't, and that's a bit of an uncharitable interpretation. I'm sure there must be a tiny minority of developers out there that doesn't ever have to write higher-level abstractions, but in the real world, writing both "business logic" and higher-level abstractions is the norm for most jobs. Only toy projects and the most menial development jobs escape that.

Even frontend, which someone erroneously claimed above that is "99% isn't custom" really is. The two major libraries, React and Vue, and the rising one, Svelte, really aren't frameworks at all, and require in practice not only a lot of custom stuff but also higher-level abstractions. Again, the exception is toy projects and menial dev jobs.

Re:90% of software engineering done today is integrating poo... by ryanbrunner on Sunday May 01, 2022 @08:05PM (#31229955)
Frameworks can be limiting, but I've never seen a framework that doesn't allow you to implement business logic on top of it. At the end of the day frameworks execute code that you write, and you can break out of the concepts your frameworks introduce and do whatever you want.

Just because 10% of your codebase is uniquely unsuitable to the 'standard' introduced by the framework doesn't mean that you can't use it for the remaining 90%. And even for that 10%, it's probably not so alien that some of the functionality provided by the framework is still relevant.

Re:90% of software engineering done today is integrating poo... by woojoo666 on Sunday May 01, 2022 @06:46PM (#31229474)
It's really just a cost-benefit analysis of whether it's worth it to build your own solution or build on top of somebody else's. I think a few years of experience gives everybody an idea of the general tradeoffs of each approach, some people will just tend to lean one way while others lean the other way
Re:90% of software engineering done today is integrating poo... by jjnoakes on Sunday May 01, 2022 @04:33PM (#31228399)
Not op but I have to disagree with this sweeping assessment. I think there is room for both approaches.

I for one believe that the best solutions I've produced over the years were things that side-stepped the popular or established frameworks and were more customized and focused solutions. They gave the business an undeniable edge over the cookie cutter competition, and by being well versed in the full stack, my team was able to implement new features at a fraction of the cost.

Anyone who knows the underlying technology can pick up our work in not much more time than learning any off-the-shelf framework simply because our solution has fewer moving parts and the relationships between the business logic and the bedrock are direct and intuitive.

Re:90% of software engineering done today is integrating poo... by twblalock on Sunday May 01, 2022 @04:39PM (#31228451)
> I for one believe that the best solutions I've produced over the years were things that side-stepped the popular or established frameworks and were more customized and focused solutions. They gave the business an undeniable edge over the cookie cutter competition, and by being well versed in the full stack, my team was able to implement new features at a fraction of the cost.

Yes but that's different from being a cowboy coder or a cynic who rejects the concept of frameworks in the first place. You built a new framework customized to your business needs. To do that, you needed to understand the context of the business and your tech stack, understand why existing frameworks didn't fit, and build a new one that works well. It's a good example of not being a cog, which is what I was encouraging in my comment.

Re:90% of software engineering done today is integrating poo... by jjnoakes on Sunday May 01, 2022 @04:51PM (#31228558)
That's just it though - I wouldn't call anything we've built a "framework" at all. All of the projects were much simpler at their core than most frameworks I've ever dealt with.

Of course, "framework" might have different definitions for different people. To me, by definition, a framework tries to be more generic than a custom solution, has more features that appeal to more than one use-case, and is designed to be flexible and fit multiple projects.

The solutions I've had major success with were none of those things because the benefits we got (deeper knowledge of our stack, faster iterations, and features no one else could touch) way outweighed any perceived benefits of using something mostly off-the-shelf.

Re:90% of software engineering done today is integrating poo... by onion2k on Sunday May 01, 2022 @04:53PM (#31228570)
I for one believe that the best solutions I've produced over the years were things that side-stepped the popular or established frameworks and were more customized and focused solutions.

No one can judge their own code. We all think we've written great stuff that other people hate working with. Even your team can be bad at judging it, because they can reach out to you if they get stuck. Those are awful ways to judge how good code is.

In my experience the best measure of good, robust, well-written code is the opinion of the team maintaining it a year after you've left. If those people are singing it's praises and happily working on it rather than complaining about tech debt and saying they want to do a rebuild, then you can say you did a good job.

Re:90% of software engineering done today is integrating poo... by breakfastduck on Sunday May 01, 2022 @06:26PM (#31229334)
You're confusing a developing thinking their code is well written with a tech team evaluating the value, reliablity and flexibility of a system.

The 'common framework' approach works great if you've solving a common problem. That's why we use libraries for certain modules or functions of a system. When your business is, even just operationally, different in some way, bespoke is often the best way. Make it good and it doesn't matter a sniff if it's an established public framework or not.

Re:90% of software engineering done today is integrating poo... by woojoo666 on Sunday May 01, 2022 @06:57PM (#31229554)
> When your business is, even just operationally, different in some way, bespoke is often the best way. Make it good and it doesn't matter a sniff if it's an established public framework or not.

There was a post recently on hackernews talking about how startups have an "innovation limit". That is, if you try to innovate too much, your scope grows beyond your reach. I think the idea applies here as well. Building everything yourself takes a lot of time. If you can position yourself to leverage the advancements of others, you can move much faster.

Re:90% of software engineering done today is integrating poo... by breakfastduck on Friday May 06, 2022 @06:07PM (#31290065)
Absolutely. I am a big force in my place of 'just buy' when others are all 'build everything in house'. If there's no genuine advantage of having something custom then don't do custom, buy something that works.
Re:90% of software engineering done today is integrating poo... by chii on Sunday May 01, 2022 @08:28PM (#31230107)
> When your business is, even just operationally, different in some way, bespoke is often the best way.

most business think themselves different, esp. in their IT infrastructure. It's closer to hubris imho.

If you have an internal/back office app, it doesn't require a custom UI framework to be created.

The only place where a custom framework should be created is if the domain of the software is custom.

Re:90% of software engineering done today is integrating poo... by breakfastduck on Friday May 06, 2022 @06:08PM (#31290071)
I'm not talking about back office admin systems. I'm talking about genuine business operations systems. And YES, most are more different than they appear on face value.
Re:90% of software engineering done today is integrating poo... by jjnoakes on Sunday May 01, 2022 @05:10PM (#31228698)
I'm not judging my own code. I'm basing my statements off of the results-oriented perspective of the businesses I've helped. And based on their positions in the market, both at the time my team implemented the projects I'm referring to, as well as long after most of us have moved on and the projects are in maintenance mode or retired, I would objectively say we were highly successful.
Re:90% of software engineering done today is integrating poo... by chii on Sunday May 01, 2022 @08:24PM (#31230083)
> I'm basing my statements off of the results-oriented perspective of the businesses

there's different criteria for judging. Business criteria and business success is one (good) criteria, but there's also the criteria of good craftsmanship (which may contribute to business success indirectly by making future maintenance easier). This criteria is hard for a non-technical business stakeholder to judge, but easy for the maintainers.

Re:90% of software engineering done today is integrating poo... by breakfastduck on Sunday May 01, 2022 @06:28PM (#31229349)
People often seem to overlook how different businesses operating in the same space can be purely because of a particular specialization or culture.

Custom is best sometimes. And that's ok. A well thought though and implemented 'bespoke' framework (literally just a system) has no value based disadvantage over a public, well known, framework / approach.

Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @04:59PM (#31228617)
That's some seriously self deprecating attitude, that can never be a healthy working environment.
Re:90% of software engineering done today is integrating poo... by scarface74 on Sunday May 01, 2022 @11:59PM (#31231309)
They gave the business an edge until someone else had to use your framework instead of a popular well documented one
Re:90% of software engineering done today is integrating poo... by com2kid on Sunday May 01, 2022 @07:28PM (#31229730)
> If everyone is writing "raw" JS/HTML/SQL/Java/whatever, they are actually building their own individual, unstandardized frameworks.

It depends.

If you have a nail, and you are using a jackhammer of a framework to pound it in, every developer that comes after you has to learn how to use that jackhammer unless they have previous experience with it. And honestly, most complex frameworks have so many different potential usage patterns that future developers will still have a heck of a learning curve. (I've never seen two uses of redux that remotely resembled each other! After using redux for 3 years I can easily find redux code that I have literally next to no idea what it is doing!)

If you use a hammer, even if it is a bespoke hammer, future developers just have to learn how to pick up that hammer.

Obviously at some point it pays to switch to using an Industry Standard(tm) solution, but for many problems plain old JS or HTML may very well be appropriate.

For example, I was making ad campaign landing pages for my now defunct startup. To ensure speed I wanted them to all be static HTML. I could have used a static site generator of some sort, configured templates and all that jazz, or, instead, I could just write HTML + CSS for 3 landing pages. (Actually I only had to write the CSS once).

Now if I needed to programmatically generate dozens of landing pages, then sure, adopting some static site generating framework may have been worthwhile. But in my case it wasn't. Raw HTML was the correct solution.

Re:90% of software engineering done today is integrating poo... by explaingarlic on Sunday May 01, 2022 @08:56PM (#31230275)
> To ensure speed I wanted them to all be static HTML

Feels like people shoehorn Gatsby too much into those kinds of situations. Bless you for keeping the dream alive - every time I see well written and small HTML/CSS/JS code on a landing page I want to scream.

Despite knowing React and being familiar enough with Vue, Angular etc. I still get imposter syndrome when I see a site's markup and see weird artefacting that comes from some framework that I have never heard of.

Re:90% of software engineering done today is integrating poo... by chii on Sunday May 01, 2022 @08:19PM (#31230057)
aka, right tool for the job.

there's no mantra that should be followed without thought in software engineering. Frameworks helps in a lot of cases, and should be used - but this decision require someone with experience to make, and this experience has to have been hard earned from previous failures or projects.

Re:90% of software engineering done today is integrating poo... by emsy on Sunday May 01, 2022 @04:38PM (#31228445)
I don’t think you have a lot of experience with long software projects. The pros of frameworks are outweighed by their cons pretty quickly. This effect is accelerated by shorter support times and an ever growing number of frameworks.
Re:90% of software engineering done today is integrating poo... by tluyben2 on Sunday May 01, 2022 @05:01PM (#31228635)
Maybe depends what tech you work in? In the Java and .NET sphere things are pretty much stable over many years. We hardly had to do any work to to move our systems (quite large ones) across the same well supported frameworks to new versions the past decades and the fact everyone in these ecosystems know the popular frameworks well and the design patterns, it scales well to many and new people.
Re:90% of software engineering done today is integrating poo... by woojoo666 on Sunday May 01, 2022 @07:13PM (#31229659)
Do you have any examples of web apps or websites with millions of users, and don't use any frameworks? The only one I can think of is HackerNews, funny enough.
Re:90% of software engineering done today is integrating poo... by robocat on Sunday May 01, 2022 @08:58PM (#31230294)
The more users, the less likely you are to use an off-the-shelf framework.

Netflix: https://netflixtechblog.com/building-the-new-netflix-experie...

Facebook: https://blog.risingstack.com/the-history-of-react-js-on-a-ti...

Edit: find out what framework (although it didn’t work on some urls I tried): https://www.wappalyzer.com/

Re:90% of software engineering done today is integrating poo... by woojoo666 on Monday May 02, 2022 @12:58AM (#31231612)
I may be wrong since this article is from 2018 but it seems like Netfix uses React for everything but their homepage [1]. Facebook uses it's own framework since, well, that framework is React. But their framework isn't some special-purposes framework built for Facebook's purposes either, it's a general purpose framework, used by tons of companies including Netfix. So I don't think many web tech companies are going to find success building their own special-purposes front-end frameworks, like some earlier comments seem to suggest.

[1]: https://medium.com/dev-channel/a-netflix-web-performance-cas...

Re:90% of software engineering done today is integrating poo... by twblalock on Sunday May 01, 2022 @09:14PM (#31230390)
It's really more about the size of the company -- those companies have enough engineers to have large teams dedicated to their various frameworks and build systems.

Some of the popular open source frameworks are derivatives of what these companies had already developed internally for themselves, e.g. React.

Re:90% of software engineering done today is integrating poo... by atotic on Sunday May 01, 2022 @10:42PM (#31230881)
I think that the decision on whether to use a framework is very hard.

When using a framework, you get most of the benefits right away, and most of the costs happen much later, when abandoning the framework is costly.

Besides pure technical quality, you have to consider more murky issues: who wrote the framework? how long will they be around for? Does their problem match your problem? Will your interests remain aligned in the future? Is there a succession plan? Will new hires be familiar with it? What's the learning curve? Does it integrate with the other N tools you are using?

Ideally, the decision to use the framework or not should be made by someone who has used it before. This is often not the case.

My personal preference is to always use simplest tools that get the job done.

I wish that hiring technical writers to write docs was more common. Most of the new libraries I have to use have documentation that is so poor, I have to use stack overflow + write test cases.

Currently, I am in the middle of taking over a go code hairball from someone who left, and who loved external dependencies. Out of 31 direct dependencies, 11 are not at release 1.0 yet. Many have poor documentation. I believe that when I am done with it, our code will have fewer dependencies, and be half the size.

Re:90% of software engineering done today is integrating poo... by belter on Sunday May 01, 2022 @06:44PM (#31229454)
And how to avoid ending up with a:

"General-Purpose Tool-Building Factory Factory Factory"?

"Why I Hate Frameworks": https://www.gwern.net/docs/cs/2005-09-30-smith-whyihateframe...

Re:90% of software engineering done today is integrating poo... by hkt on Sunday May 01, 2022 @10:56PM (#31230966)
I agree with most of this, but

> it raises the barrier enormously for onboarding new people.

is.. a little ironic. I've never met any of the gazillion frameworks out there that have made it easier to get people up to speed, despite promises to that effect.

Re:90% of software engineering done today is integrating poo... by marcosdumay on Sunday May 01, 2022 @05:11PM (#31228704)
> Why are frameworks popular?

Because they make it very quick to get a 70% working system that you can sell to people (internally too) before the people with the capacity to get a 100% working system gets their first version.

Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @05:51PM (#31229052)
In other words: they make sense for making prototypes.
Re:90% of software engineering done today is integrating poo... by marcosdumay on Sunday May 01, 2022 @07:18PM (#31229689)
And then your prototype gets into production, and you can never rewrite it.

So, no, they do not make sense for making prototypes. They do make work when you want a 70% solved problem and won't care about never reaching 100%. On the other cases, you still need to use them, because if somebody gets those 70% first, you will have problems, but they make no sense at all.

Re:90% of software engineering done today is integrating poo... by commandlinefan on Sunday May 01, 2022 @06:26PM (#31229330)
> Your job is to produce software that meets the requirements of the business

In “raw" html/js/sql/Java.

Re:90% of software engineering done today is integrating poo... by thewarrior on Sunday May 01, 2022 @06:37PM (#31229411)
Honest question - how does one provide value in this reality. It’s something I’m trying to understand
Re:90% of software engineering done today is integrating poo... by closeparen on Sunday May 01, 2022 @07:39PM (#31229797)
The business itself is like a computer process. There are flows of information and resources. There is state. There are subroutines. There are bottlenecks and bugs and wasted efforts and errors that may or may not be getting detected or mitigated. There are various intents that customers and stakeholders might have that are unreasonably difficult to fulfill under the current layout of things.

You add value when you optimize, debug, and refactor the business operation. Increasingly in old-economy companies, but especially in Silicon Valley companies, the business operation is largely defined in code. So this is something software engineers can do, through well-chosen code changes.

Outside of startups, engineers rarely do this alone. There are executives, business analysts, product managers, data scientists, etc. with very similar tasking. But you want to get into a position where these people see you as a full intellectual partner, not as an implementation resource to type in their already-baked ideas.

Re:90% of software engineering done today is integrating poo... by john567 on Sunday May 01, 2022 @06:48PM (#31229492)
Start simple. Educate co-workers on why a specific approach is good. Build culture. Slowly but surely you should all be working towards the same goal. It's a slow process but with many moving parts. Take on a single piece at a time. That's the only thing that works.
Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @06:14AM (#31233225)
This is the worst type of working environment, when everyone on the team is trying to "educate" and evangelise and "build culture" which is nothing but sucking up to the manager, instead of trying to be realistic about solving issues and delivering value.
Re:90% of software engineering done today is integrating poo... by woojoo666 on Sunday May 01, 2022 @06:41PM (#31229431)
At least if I'm understanding your question properly, frameworks only provide the frame, you have to fill in the rest
Re:90% of software engineering done today is integrating poo... by x-shadowban on Sunday May 01, 2022 @05:39PM (#31228946)
His argument was more that that there are hose-operating-tooling (and tooling for that tooling) that many fire departments are using but if you want to adjust the nozzle aperture well that's not implemented yet and you need the schematics
Re:90% of software engineering done today is integrating poo... by KronisLV on Monday May 02, 2022 @06:05AM (#31233161)
> Why are frameworks popular? Because they provide a standardized way for multiple engineers, and multiple engineering teams, to collaborate effectively on the same product -- and they make it easy to hire people who already know the frameworks.

Hmm, i'd say that there are frameworks that actually make things easier and better, and some that are much like the incomprehensible Rube Goldberg machines that the previous poster complained about.

For an example of this, you needn't look any further than the Spring framework in Java, perhaps the ultimate example of enterprise bloat of poorly understandable (unless you spend all your time digging into the internals) and overly abstracted non-solutions for problems, and that's even before you pull in 50-100 dependencies for making your dated monolith do whatever the business wants.

There is an absurd amount of XML configuration needed, except that sometimes you need to mess around with annotations in your source code as well, except for those cases when instead you'll want to just overwrite some class with your custom logic inside of the methods, which will be initialized by some Eldritch abomination of class loading and reflection, or maybe you'll need to change a bunch of properties in a config file, with all of this leading to long and arduous error messages that will make you waste hours digging through Stack Overflow.

I was in charge of migrating an older Spring app to Spring Boot, which attempts to alleviate some of these issues (and there was also the fact that the particular Spring version was EOL at that point) and after wasting more time than i'd like to admit of an error after an error after an error, it was decided to just update Spring itself as far as possible and let it chug along in a barely alive state.

The framework wasn't a way of managing risks or "getting things done", it ended up being a risk in of itself and was a massive pain once the system needed to be supported, maintained and also have new functionality developed for 5-10 years or so. That's not to say that there aren't better frameworks out there, but there definitely are some that will be more trouble than they're worth, unless you want to have a person or two full-time just to wrangle them in order and continuously maintain and update them, which for many of the smaller orgs out there is unacceptable.

> If everyone is writing "raw" JS/HTML/SQL/Java/whatever, they are actually building their own individual, unstandardized frameworks.

I've also seem bespoke frameworks be used and those were generally worse - while there was the occasional good idea in them and they could be decent to work with in a limited set of circumstances, getting help when something goes wrong with them was impossible and you were stuck reading the source and mucking about in it. Why is that bad? Because with the larger and more popular frameworks out there you can instead look up solutions for problems or integrations that someone else has written.

I'll admit that pulling in dependencies carries certain risks in of itself, but you'll very quickly realize how nice it is to let someone else step on rakes before and learn from their problems and mistakes, instead of attempt to translate code comments from Lithuanian to your own language when prod is running into issues, because the original devs are long gone and there is no documentation, nor examples of how to use anything in place.

Thus, it is better to use frameworks that have tens of thousands of collective man hours put into them, or even more, as long as they don't suck.

So, in the end, it's probably better to use frameworks that keep you closer to the code that is actually running, like Spring Boot (where at least parts of the config can be done in plain Java), or even look at ones like .NET (the newer ones are a bit like Spring Boot), rather than DSL hell.

You can put a breakpoint in your Java code and see why something isn't initializing properly. You cannot put a breakpoint into your .properties, .xml or .yaml file (or even feasibly find where to put into the over-abstracted configuration read mechanism, or find how it connects to the bit that is actually initializing your data).

Re:90% of software engineering done today is integrating poo... by explaingarlic on Sunday May 01, 2022 @08:42PM (#31230186)
> Why are frameworks popular? Because...

That's an extremely open question, and I wouldn't agree that frameworks, in any way, "provide a way for people to collaborate" any more than a whip does. They seem to me to limit the ability to write the code you want for no value other than providing confirmation bias.

The idea that the same thing being outputted on the screen will have two implementations by two uncommunicative engineers that vary in such a way that they become impractical, impossible or even at all harder to debug, is simply a myth. I highlighted the word "engineer" because that's the key point - if you are hired to solve a problem, you are probably going to solve it the easiest and most convenient way. You are trusted to write code, not use an API. I find it hard to buy the idea that 20 year old aspx code is any easier to debug than pure JavaScript written around that time.

As far as why frameworks have become the norm, I would personally put it down to, in no particular order, the following ideas:

- Some are genuinely useful - functionality is limited in the parent environment's API and must be implemented in some way. This is rare, in my (mild) experience.

- The company had learned the lesson that contractors (especially ones that win the bidding wars) write horrific and unmanageable code. Therefore, it decided that a cost-free way to alleviate this issue is to force all engineers, permanent or on-contract, to use a specific framework.

- The above point spread between companies as people (directors of engineering) shifted around, word spread that someone was able to make significant cost savings etc.

- They are in place to allow one to follow idioms better. I recently interviewed for a company that followed, quite closely, the clean architecture book by Martin Fowler, with their own internal framework. They had a good plan in mind - they wanted components to be interchangeable, usually at compile time, and needed to ensure that they followed procedure in order to write code that was manageable at scale in order to achieve this. They made their own framework and have used it for 10+ years. This proper, elegant use of a framework is very rare.

I do not mean to say that frameworks are useless - however, JQuery has always been absolutely worthless to me in my personal endeavours - which often included quite bespoke DOM manipulations - the exact place that JQuery is meant to shine. To me, it is a great example of something that was phased in as a Band-Aid solution to people writing terrible code as they had no ownership of the product.

I will admit that I use little helpers, such as

  function $(usuallyASwearWord){
      // Yes I really use element by id for this when writing my own fun code. Not query selector. 
      return document.getElementById(usuallyASwearWord);
  }

and I wouldn't be using these if JQuery never exploded in popularity - but it's just a skeuomorph. A cute little oddity that has some minor, pointless, boring history/flavour behind it. I don't think that JQuery has provided the world with any significant net effort savings, and that it is far from the only framework that will have this legacy.
Re:90% of software engineering done today is integrating poo... by wnolens on Sunday May 01, 2022 @03:38PM (#31227979)
I've started and quit web dev projects about 4 times in the past 5 years. I'm a distributed systems dev. The complexity of the recommended tool chain is mind boggling (and I consider my day job incredibly complex, of which I have a decade of experience doing). I would have said I hate React.

Finally started another project. No frameworks this time. Started with html and single js file until I needed more.. and solved the problems step by step. I'm at the point that I now see the benefits of react, but only by doing it this way could I possibly learn why.

Re:90% of software engineering done today is integrating poo... by moonchrome on Sunday May 01, 2022 @04:30PM (#31228374)
>I'm at the point that I now see the benefits of react, but only by doing it this way could I possibly learn why.

That's why I feel bad for the new generation of developers. When I started developing in 2000s it was enough to know low level abstractions, some design patterns, etc. Along the way I've seen the context in which for eg. MVC was revolutionary, and all the latest frameworks actually solved a lot of real problems (SQL query in PHP garbage all over the place on backend, jQuery/MooTools/ExtJS/Coffescript/AngularJS, supporting IE6, etc.)

A lot of modern tools make sense to me because I know the context they came out of. I feel we've done a shit job of preserving this context and lesions that lead to current frameworks - this will eventually lead people to rediscover all the mistakes that were hit in past, but also saddle us with legacy burden because it's hard to distinguish what's relevant and what's a result of historic constraints.

Re:90% of software engineering done today is integrating poo... by sprkwd on Sunday May 01, 2022 @03:55PM (#31228095)
I have completely given up on web dev these days.
Re:90% of software engineering done today is integrating poo... by commandlinefan on Sunday May 01, 2022 @06:28PM (#31229356)
Backend is worse, they’ll make you use the Spring “framework” that makes React look like a dream.
Re:90% of software engineering done today is integrating poo... by guywhocodes on Sunday May 01, 2022 @07:58PM (#31229907)
We have a basic template that when empty, takes about 20min to compile on a very new laptop, builds to a 200MB+ jar.
Re:90% of software engineering done today is integrating poo... by newtwilly on Sunday May 01, 2022 @10:50PM (#31230920)
Something sounds wrong, but I don't know exactly what you mean by "basic template"? Like a Spring boot example app?
Re:90% of software engineering done today is integrating poo... by AtlasBarfed on Sunday May 01, 2022 @09:26PM (#31230453)
A couple annotations and a base application class and you're up and running with a REST service. That's considered hard?
Re:90% of software engineering done today is integrating poo... by presentation on Sunday May 01, 2022 @10:22PM (#31230761)
Translated to React: a single render function and you're up and running with a webpage. That's considered hard?
Re:90% of software engineering done today is integrating poo... by mdoms on Sunday May 01, 2022 @06:47PM (#31229481)
Spring is a simple MVC framework, it follows the same patterns as similar Ruby, Python, C#, PHP etc frameworks. React very much blazes its own complicated trail.
Re:90% of software engineering done today is integrating poo... by ratww on Sunday May 01, 2022 @10:47PM (#31230902)
That statement is beyond the absurd. The API of React is several orders of magnitude smaller than Spring and similar MVC frameworks with the same feature. There is even a React replacement with feature parity, Preact, that clocks around 3kb.
Re:90% of software engineering done today is integrating poo... by erik_seaberg on Sunday May 01, 2022 @07:34PM (#31229759)
Spring is a powerful but pretty complicated DI framework. That MVC stuff is also there but for many use cases (microservices, batch, CLI) it’s not really helpful.
Re:90% of software engineering done today is integrating poo... by Blackthorn on Sunday May 01, 2022 @07:29PM (#31229739)
Well, nowadays anyway. It's come a long way from the point where an AbstractSingletonProxyFactoryBean seemed like a viable solution to a problem in the framework.
Re:90% of software engineering done today is integrating poo... by eastbound on Sunday May 01, 2022 @04:28PM (#31228353)
One major problem React solves is HTML injection. It used to be an interview question to work at our place, and since React, developers don’t often realize that old frameworks like Freemarker didn’t escape HTML. By default.
Re:90% of software engineering done today is integrating poo... by arcbyte on Sunday May 01, 2022 @06:15PM (#31229239)
I remember html escaping being a problem in the early 2000s, but promptly solved. Its been solved in every language for over a decade. React didnt do jack to solve it because it was already table stakes and had been for over a decade.
Re:90% of software engineering done today is integrating poo... by bennysomething on Sunday May 01, 2022 @05:13PM (#31228722)
Genuine question, what do you mean escape html by default?
Re:90% of software engineering done today is integrating poo... by likecarter on Sunday May 01, 2022 @05:37PM (#31228927)
If someone submits a text field with the contents `<bold>Injection</bold>` that will then be reflected on the site (i.e. a comment section), React will display the literal string, rather than bolded text.
Re:90% of software engineering done today is integrating poo... by bennysomething on Monday May 02, 2022 @10:30AM (#31235587)
Ah I see! Thanks
Re:90% of software engineering done today is integrating poo... by ecshafer on Sunday May 01, 2022 @02:25PM (#31227405)
This is what I have always really disliked about many web development frameworks. Their goal is to either a) do things magically in a specific way or b) do so with a bunch of configuration files. Spring comes to mind as a particularly egregious case that does both. Spring does things automatically, until you need to add a configuration file for every change. You need to add this wrapper and this library for this other case. I have always wanted a web development framework that works more like a game development framework. Where you still code everything you need but it doesn't hide the part where you make a window or add a listener. Which makes it a lot easier to find where things are going wrong and how to change the configuration as opposed to go to stack overflow and learn you need to add this dependency which then does things behind the scenes.
Re:90% of software engineering done today is integrating poo... by brightball on Sunday May 01, 2022 @03:46PM (#31228036)
This is actually why Rails was so successful. The world of Java was frameworks full of configuration files and Rails went with the "convention over configuration" approach.

You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately. It's fantastic for teams and long term maintenance between different devs because the learning curve of each project is virtually non-existent.

But Rails has gotten bigger and more complicated over the years, which makes it tougher to make the case.

Re:90% of software engineering done today is integrating poo... by ratww on Sunday May 01, 2022 @11:30PM (#31231145)
> You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately.

Except lots of projects today use very diverse structures and the meat of the code is often on complex libraries like ActiveInteractors, Trailblazer Operations, stuff from the Dry-RB ecosystem, etc, or sometimes (hopefully) simple Service Pattern classes, if you're lucky. Sometimes all of them at the same time. For lots of companies, Rails projects in the real world has ceased being easy to grasp for a while.

Re:90% of software engineering done today is integrating poo... by brightball on Monday May 02, 2022 @10:45AM (#31235760)
Yea, this has been my experience as well. That's what I meant by the "bigger and more complicated".

Certainly set the standard for a long time though.

Re:90% of software engineering done today is integrating poo... by emteycz on Sunday May 01, 2022 @03:15PM (#31227794)
Node.js + Express is what you want. I'm not a Go developer, but it seems to me that the Go ecosystem also has what you want.
Re:90% of software engineering done today is integrating poo... by gernb on Sunday May 01, 2022 @04:32PM (#31228392)
can you give more details? My understanding is the node + express is really low level providing almost nothing except a set of chainable functions based on routes. To get any actual functionality (storing to databases, authentication, users, sys admin, etc requires writing everything yourself.

The reason I like batteries included frameworks is I get all that for free and ideally it's already following best practices so I don't have to worry about security, about account recovery, about versioning new data/features, about scaling, etc

Re:90% of software engineering done today is integrating poo... by chii on Sunday May 01, 2022 @08:36PM (#31230159)
> don't have to worry about security, about account recovery, about versioning new data/features, about scaling, etc

with the exception of security (i take it you mean authentication), everything else is unlikely to be provided by a framework like spring directly - you'd have to choose something to provide it or write it yourself.

Re:90% of software engineering done today is integrating poo... by gernb on Monday May 02, 2022 @04:53AM (#31232720)
Rails provided many of those things. I believe Django does. Meteor used to provide many of tbem
Re:90% of software engineering done today is integrating poo... by omginternets on Sunday May 01, 2022 @02:01PM (#31227171)
I tell every junior colleague two things:

1. There is software engineering, and then there’s working at the digital factory.

2. A good way to set yourself on the path that leads to the former is to get intimately familiar with the HTTP protocol. A good way to start is to reject fancy frameworks, and to get comfortable reading RFCs.

Being the guy who really knows HTTP is a powerful career move. Becoming that person almost inevitably kicks off a virtuous cycle that steers bright/motivated devs well clear of writing REST endpoints for the rest of their working lives.

Re:90% of software engineering done today is integrating poo... by pc86 on Sunday May 01, 2022 @02:11PM (#31227298)
I don't think I can really articulate why but this smells a lot like the "real programmers use [neo]vim" or "real developers write C++" kind of gatekeeping that was pretty widespread and even expected/accepted a few decades ago, but really has no place now.

Being intimately familiar with HTTP is fine, reading a lot of RFCs is fine, but there are plenty of well respected, well compensated, influential engineers who do neither, and have no need for either one.

Re:90% of software engineering done today is integrating poo... by omginternets on Sunday May 01, 2022 @02:14PM (#31227316)
I see what you mean, but you’ll note that I’m neither saying that it’s the only way, nor am I saying that it’s required. What I’m instead doing is trying to cultivate a deep understanding of one’s tools and protocols, which is absolutely the hallmark of a competent engineer.

I concede that this may superficially resemble the aberration you describe, but insist that it’s actually very different.

Re:90% of software engineering done today is integrating poo... by blagie on Sunday May 01, 2022 @03:43PM (#31228010)
My experience is that to do any kind of engineering and most kinds of science really well, you need to have a deep understanding one layer down and one layer up.

The HTTP comment seems off-base. HTTP is neither particularly important or interesting as a protocol. You can spend a half-hour with netcat and have a few conversations with your web server, and you're set.

The concept more broadly is spot-on. The "I don't need to know [x] to do my job" crowd is universally mediocre at their job.

For a programmer, the set of things one layer down is important, be that cache/memory hierarchies, low-level programming, operating systems, databases, compilers/interpreters, or otherwise. So is one layer up, which is usually business and product understanding.

I'll also mention: Mediocrity at one's job is okay. There are plenty of wonderful people who have work-life balance and do interesting things outside of their job, and just want a pay check. There are people happy to be working on systems I'd be miserable working on -- payroll, banking, inventory, etc. -- and I'm glad they're around. A few of them are among my favorite people too.

Re:90% of software engineering done today is integrating poo... by omginternets on Sunday May 01, 2022 @05:22PM (#31228792)
Respectfully, if you think http is unimportant or uninteresting, then you don’t know it very well. It’s exceedingly interesting from a linguistic point of view, to name but one; the notion of verb + complement of the object is fundamental to http, and sheds light on where it tends to be the _wrong_ choice. This inevitably leads to non-trivial design discussions.

And comment about netcat happens to be exactly what I’m condoning.

As for mediocrity, sure. But it should be voluntary, not imposed by a lack of options.

Re:90% of software engineering done today is integrating poo... by blagie on Sunday May 01, 2022 @10:33PM (#31230840)
I think this: "Respectfully, if you think http is unimportant or uninteresting, then you don’t know it very well" is fairly presumptuous.

HTTP has no interesting theoretical basis, and doesn't really generalize to much. Like most early internet protocols, it's kind of random and ad-hoc, with incremental hacks and improvements like keep-alive added later. You can pick up any RFC -- POP, IMAP, or whatever, and get just as much out. That's not nothing; they're worth knowing, but here's a short list of protocols and data standards which which have a theoretical basis which will teach you something deeper:

- git. Brilliant data standard.

- SQL. And relational database theory.

- SGML. Yes, the original. Much juicier than XML in design.

- Cryptographic protocols. Pick up a copy of Applied Cryptography, and read the chapter.

- A survey of the early RPC and object embedding protocols (OpenDoc, OLE, etc.)

- TCP/IP

- Any of the various compression and/or error correction protocols.

- Printer standards, especially PostScript

- Video, audio, or image compression standards.

.. and so on.

Some of those require months of study.

Re:90% of software engineering done today is integrating poo... by ratww on Sunday May 01, 2022 @11:03PM (#31230999)
I would say that mediocrity is okay as long as you don't force others to follow it. Sometimes I feel as if there is some sort of "militant mediocrity" happening in some corners of our profession, where anyone even remotely interested in digging one layer down is not only looked down as not being enlightened enough, but also committing a capital sins of acting against the business interests and walking outside the predetermined boundaries of their programming-caste. Cue horror stories of cowboy coders and NIH.
Re:90% of software engineering done today is integrating poo... by bennysomething on Sunday May 01, 2022 @05:20PM (#31228772)
That's a good way of looking at domain knowledge "one layer up". I'm have been terrible at this in the past and I have been making an effort to improve. Business knowledge seems to provide the most leverage, especially in fields like finance.

My problem is I find the knowing the lower level stuf way way more interesting. Heck I'm doing a udemy course on network programming which arguably won't help my career, I just have a secret shame about not really knowing networking. (Plus it's really interesting)

Re:90% of software engineering done today is integrating poo... by folkhack on Sunday May 01, 2022 @03:16PM (#31227810)
If I'm hiring a SWE that will touch anything web I expect them to know the basics of HTTP and to be capable of referencing/digesting an RFC. It's a common interview question for these roles to outright ask, "how does the internet work?" gesturing to a whiteboard. It's a reasonable stance to take.

Overall I agree with your gate-keeping comment - that's how people interview/hire. I disagree that it "has no place" - if I'm hiring a mid-to-senior engineer that's web-capable I am 100% gate-keeping to make sure they have an intimate understanding of HTTP + are capable/comfortable reading RFCs.

Re:90% of software engineering done today is integrating poo... by zozbot234 on Sunday May 01, 2022 @03:49PM (#31228064)
> how does the internet work?

It's like a series of tubes. That's why SWE work involves so much plumbing and getting deep into all sorts of $#!+.

Re:90% of software engineering done today is integrating poo... by eastbound on Sunday May 01, 2022 @04:39PM (#31228450)
While Internet is a series of tubes, SQL is a sewer: You need a lot of layers to interact with it because it’s very dirty. Real engineers have Liquibase over Hibernate and completely hide SQL from developers. Also it’s extremely slow, I don’t know why old people like it. That’s why NoSQL works better when you have large databases, like a thousand documents or more.

Also, React is not slow at displaying tables. If it’s slow, you can use plugins to hide cells which are not in the viewport.

(Old farts like me manage a billion records and display tables of 7k rows x 100 columns in a webpage in mere milliseconds, a joy that React developers will never understand. Why do you need more than 10 lines if you have pagination, they say).

Re:90% of software engineering done today is integrating poo... by xeromal on Sunday May 01, 2022 @04:30PM (#31228369)
I would say that if a web dev can articulate http verbs, their uses, and how to design a cohesive naming strategy and documentation scheme, that's all they need to be competent. There is no need to read the HTTP RFS for most design tasks. I can understand those requirements for Google, AWS, Facebook devs, but 90% of the work out there doesn't need that level of understanding to make something decently performant.
Re:90% of software engineering done today is integrating poo... by ratww on Sunday May 01, 2022 @10:54PM (#31230944)
90% is an exaggeration. Even someone doing CRUD has to be familiar not only with HTTP verbs, but also some headers, response codes, query strings, request bodies, understand how caching works, etc, at some point. The only way to avoid it is only working for years on the simplest of projects.

They don't have to read RFCs in bed before sleep, but they should at least know the gist of what they contain.

Re:90% of software engineering done today is integrating poo... by xeromal on Sunday May 01, 2022 @11:14PM (#31231065)
All those things that you listed can be learned without reading the RFCs though, no? But yeah, I agree with the list you wrote. That's what I had in mind.
Re:90% of software engineering done today is integrating poo... by ratww on Monday May 02, 2022 @09:58AM (#31235187)
That's why I wrote "They don't have to read RFCs in bed before sleep, but they should at least know the gist of what they contain."
Re:90% of software engineering done today is integrating poo... by ransom1538 on Sunday May 01, 2022 @04:33PM (#31228400)
I bet this is a poor juniors interview out there:

Interview 0:

"I expect them to know the basics of HTTP and to be capable of referencing/digesting an RFC"

Interview 1:

"All devs should be up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff"

Interview 2:

"Any real programmer can reverse a string in C without a buffer"

Interview 3:

"I expect anyone working with k8s to understand the cgroup fundamentals."

Interview 4:

"No really. What is html5?"

Re:90% of software engineering done today is integrating poo... by tester756 on Sunday May 01, 2022 @04:21PM (#31228301)
Why would you need to be capable of referencing a HTTP RFC?

Are you doing something fancy with HTTP?

Re:90% of software engineering done today is integrating poo... by thombles on Sunday May 01, 2022 @04:39PM (#31228454)
Would it count as “fancy” to find out whether header names are case sensitive? Plenty of useful things in there.
Re:90% of software engineering done today is integrating poo... by joshuamorton on Sunday May 01, 2022 @05:26PM (#31228836)
I certainly don't think that's a thing someone needs to know to be a useful web developer. I've certainly never needed to care, although I wouldn't classify myself as web in particular.
Re:90% of software engineering done today is integrating poo... by antifa on Monday May 02, 2022 @08:06AM (#31234027)
I've never needed to look up if headers were case sensitive, it's just never caused an issue in my 10 years experience.
Re:90% of software engineering done today is integrating poo... by omginternets on Sunday May 01, 2022 @05:23PM (#31228805)
Referencing, no. But being able to look up the answer to an tricky edge case in the RFC is a valuable skill
Re:90% of software engineering done today is integrating poo... by pydry on Sunday May 01, 2022 @04:23PM (#31228319)
Thats a really odd set of things to gatekeep on.
Re:90% of software engineering done today is integrating poo... by commandlinefan on Sunday May 01, 2022 @06:34PM (#31229397)
What, fundamental knowledge and capability?
Re:90% of software engineering done today is integrating poo... by pydry on Sunday May 01, 2022 @06:55PM (#31229542)
Fundamental for those whose job is building web servers, sure. Id expect nothing less from the authors of apache, nginx, etc.
Re:90% of software engineering done today is integrating poo... by mattgreenrocks on Sunday May 01, 2022 @03:14PM (#31227783)
Well respected and compensated engineers usually have a depth of experience that extends beyond their REST framework. That’s what the parent was advocating.
Re:90% of software engineering done today is integrating poo... by commandlinefan on Sunday May 01, 2022 @06:32PM (#31229385)
> real programmers use [neo]vim" or "real developers write C++"

Real programmers know how to do both even if the don’t do them exclusively.

Re:90% of software engineering done today is integrating poo... by pc86 on Sunday May 01, 2022 @08:48PM (#31230220)
The idea that you're not a real programmer if you can't use a specific editor is idiotic.
Re:90% of software engineering done today is integrating poo... by commandlinefan on Sunday May 01, 2022 @10:22PM (#31230763)
The idea that not knowing something makes you smarter is idiotic.
Re:90% of software engineering done today is integrating poo... by pc86 on Monday May 02, 2022 @07:57AM (#31233952)
Feel free to quote where anyone here is saying not knowing something makes you smarter.
Re:90% of software engineering done today is integrating poo... by andrewprock on Sunday May 01, 2022 @04:31PM (#31228386)
If reading RFCs is a gate, then it is a pretty bad one. They are public, free, well known, and generally well written.
Re:90% of software engineering done today is integrating poo... by antifa on Monday May 02, 2022 @08:14AM (#31234111)
Also unnecessary to read for 99% of webdev work.
Re:90% of software engineering done today is integrating poo... by superdisk on Sunday May 01, 2022 @06:05PM (#31229170)
Why is gatekeeping always considered to be a bad thing?
Re:90% of software engineering done today is integrating poo... by antifa on Monday May 02, 2022 @08:24AM (#31234206)
Gatekeeping is not always a bad thing, but OP implemented a clear sample of the No True Scottsman fallacy to draw a rather arbitrary and mostly useless line to put themselve in the imaginary "real programmers" group.
Re:90% of software engineering done today is integrating poo... by urthor on Sunday May 08, 2022 @07:52AM (#31303220)
It does feel like the barrier to entry for that kind of deep knowledge career is increasing these days.

Maybe it's because I live outside the United States, but it seems like it's much harder to build a "pathway" into work that demands that intensive, deep understanding of engineering on computers. At least one that'll pan out in my 9-5.

The supply of problems that require deep knowledge vs framework Kung Fu... my impression from ground level is they're tilting more towards GitHub martial arts every year.

The supply of companies outside the United States with a deep interest in these topics is sparse, to say the least.

Re:90% of software engineering done today is integrating poo... by Consultant32452 on Sunday May 01, 2022 @07:58PM (#31229909)
I find the best path, for me, is to be the guy who knows HTTP pretty well but I don't let anyone else know. Once they find out I know things I get tapped to fix all the old problems instead of build new problems, then I have to leave because the work becomes miserable.
Re:90% of software engineering done today is integrating poo... by scarface74 on Monday May 02, 2022 @12:02AM (#31231324)
Yes and I tell junior developers the only way to be good is to know assembly language like I had to know. /s
Re:90% of software engineering done today is integrating poo... by ozmodiar on Sunday May 01, 2022 @01:57PM (#31227117)
This strikes a nerve with me. Lately my work has started taking apart our website and shifting functionality to 3rd party vendors in an effort to limit liability. We're going to end up with something far less versatile, uglier and ironically less secure than what we started with. My focus is shifting to a bunch of API stuff that I just don't find very rewarding.
Re:90% of software engineering done today is integrating poo... by dottedmag on Monday May 02, 2022 @01:55AM (#31231841)
I feel you.

In my role as a software architect in a small company I've been booting out various "frameworks" and overly invasive libraries, because it turned out they are not delivering much, while requiring attention and forcing us to bend our code to satisfy their demands.

First ones to go were various cloud libraries: AWS, Google Cloud, CloudStack. It's a plain REST. I estimate that the code that talks to Google Cloud directly is shorter than it was when the library was involved.

Docker went (it's a REST with a few quirks). Kubernetes client went (same). GitHub client went.

gPRC went (fortunately we're not required to talk gRPC anywhere except a few endpoints, and it turned out that Protobuf is not hard to implement if you don't have tons of schemas, and gRPC is HTTP/2+Protobuf).

Finally I booted Mongo client library, because all we needed is a few requests, and implementation of Mongo wire protocol + BSON ended up costing us ~300 lines of code.

Remaining libraries earn their keep: there is cryptography, XPath, JSONPath, compressors, userland IP stack, complex serialization formats. I thank the authors of these libraries, and due to some reason these libraries are also the least complicated and most compatible version-over-version.

Re:90% of software engineering done today is integrating poo... by jd_mongodb on Monday May 02, 2022 @12:38PM (#31237429)
When you booted the Mongo client library what did you use in it's place? Were you connecting to a cluster or a single node? Lightweight clients are always interesting because of the trade offs they make.
Re:90% of software engineering done today is integrating poo... by tootie on Sunday May 01, 2022 @07:08PM (#31229623)
Every time I see a framework how quickly they can bootstrap I now consider that a red flag. The more automagic, the more you can't ever figure out why something goes wrong. It's been said that most products spend 99% of their lifetime in maintenance. If a framework wants to impress me, show me how clear the stack traces and IDE integration are. Show me how crystal clear it is to trace the execution path.
Re:90% of software engineering done today is integrating poo... by sjaak on Sunday May 01, 2022 @02:31PM (#31227459)
What are you talking about?

What's not to like about the SimpleBeanFactoryAwareAspectInstanceFactory [1]?

[1] yes, this exists

Re:90% of software engineering done today is integrating poo... by Forge36 on Sunday May 01, 2022 @02:35PM (#31227489)
That I couldn't find the advanced one or the generic legume factory and ended up having to write my own as the owner wasn't currently accepting pull requests?
Re:90% of software engineering done today is integrating poo... by _Algernon_ on Sunday May 01, 2022 @04:38PM (#31228438)
Re:90% of software engineering done today is integrating poo... by jchw on Sunday May 01, 2022 @05:00PM (#31228630)
Writing raw anything is not necessarily your job.

However, a lot of people have an interesting view of things like frameworks, ORMs, and other abstractions. To some, it feels like pure all-or-nothing; but what if it didn’t have to be?

Even the biggest hater of SQL database abstractions will admit there are reasons why someone would want them. But I wonder if there is an answer somewhere in the middle that could go both ways. For example, sqlc[1] provides basically all of the type safety that overbearing database frameworks might, but it lets you write plain old SQL just as you normally would, and integrates cleanly with your existing migrations solution. It doesn’t solve everything, but I have a feeling more people would like tradeoffs like these: an enormous amount of complexity does exist, to say, parse SQL and emulate DDL transactions for the sake of typing, but it stays entirely in the tool itself, and the resulting code and interfaces are completely simple and obvious code.

I believe that there are multiple better middle grounds waiting to be discovered in any given niche where the options currently feel like barely-worth-it trade-offs.

[1]: https://sqlc.dev

Re:90% of software engineering done today is integrating poo... by jseban on Sunday May 01, 2022 @05:14PM (#31228728)
> Even the biggest hater of SQL database abstractions will admit there are reasons why someone would want them.

There is only one reason, and it's that people don't understand how to use SQL, and that's because it's not taught in computer science degrees, and this also has strong ties to the battle between sun and oracle.

And this makes database developers expensive and hard to hire.

There is no reason to use an ORM if you know SQL and database modelling. The relational model is by far the most powerful tool to solve CRUD use cases, which "web development" is, and that's just simply a fact.

What the ORM will do for you is automate some boilerplate mapper code, which might be a bit boring to write, but is very simple. And the downside is that it will make all of your database modelling, querying, access etc orders of magnitude more obscure and complex compared to just using SQL. And now you will waste enormous amounts of time fighting with the framework to debug the ORM and find out which kind of weird SQL statements it generates, where you would have complete control over this if you just wrote your own.

The obvious solution that would benefit everyone, is to simply train your developers to use SQL, if they don't already know it, and let them take a course if they need to. Not to slap on some stupid framework and make a huge unmanageable mess of the whole system.

Re:90% of software engineering done today is integrating poo... by jchw on Sunday May 01, 2022 @06:22PM (#31229302)
> There is only one reason, and it's that people don't understand how to use SQL

Unfortunately, I immediately think you have misunderstood. While ORMs and other database abstractions may be a boon to folks who don’t know SQL, or at least some may think that, it is not the only reason that people use them. It may not even be one of the bigger reasons.

Type safety is first and foremost a great example. Wouldn’t it be great if you could literally not ship SQL code that has typos, syntax errors, or other query errors? Unit tests catch those, but you have to actually write them, and they still can’t help if you hold things wrong. (Like using sprintf for SQL queries, god help us. Yes, that is a mistake no professional should make. But if you add enough layers of complexity, you might just fool someone who knows better into doing basically that with extra steps. There are some ways to combat this of course, like PEP 675[1].) In some environments you might accomplish this with compile-time linting or advanced metaprogramming. However, ORMs also do this right out of the box generally, at least in languages where it can be done.

But even then, that doesn’t scratch the surface of what’s possible. Mind you, with sqlc, we’re still talking about making raw SQL queries. But those SQL queries contain tons of information that gets duplicated by the programmer. For example, it is possible to statically know what types of inputs and output columns any given query will have based on just the schema and the query itself. sqlc gives you this information. It generates correct wrappers for SQL code using only raw SQL queries as input.

This is not the only benefit of abstractions of course. And sqlc doesn’t give you all of the benefits of an ORM. However, that’s exactly what I’m trying to say: a lot of people have an idea in their head about what an abstraction must entail, but there’s probably better tradeoffs that are genuinely not susceptible to the same issues that you’re imagining. Case in point, I have a feeling you interpreted my post to only be regarding ORMs, but even the text you quoted is more general—I said “database abstractions” for a reason :)

[1]: https://peps.python.org/pep-0675/

Re:90% of software engineering done today is integrating poo... by shroompasta on Sunday May 01, 2022 @08:58PM (#31230292)
I disagree.

How would you be able to validate data that you can map to your tables without hitting the db?

If you wanted to add a new row of data to one of your tables, you would have to hit the db, get row columns and make sure that data fits.

Or you could write out your table structure separately outside of the db, and validate against that, but that would just leave you with two sources of truth which is an antipattern.

Or you could just use an ORM.

I'm fluent in SQL, and understand the solutions that ORMs solve - it's not just a pure abstraction over sql queries, but the tooling and utility provided wrapping around that is what makes it so powerful.

Re:90% of software engineering done today is integrating poo... by scarface74 on Monday May 02, 2022 @12:09AM (#31231356)
I’ve known SQL for close to 25 years. Composing queries programmatically is much easier and less error prone than raw sql when using an ORM.

In the case of C# Entity Framework, the ORM abstraction- LINQ - is a first class language feature with full compile time type checking and auto complete.

The same LINQ query can work across databases and in memory collections including RDMS’s and Mongo. Eventually in any object oriented language, you’re going to end up doing “something” to convert relational data to objects.

Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @03:59AM (#31232449)
> Composing queries programmatically is much easier and less error prone than raw sql when using an ORM.

This is only true for the most trivial of use cases that will not really bring any value to your users. As soon as you get more advanced feature requests, you need the power of the relational model, which is now abstracted away behind a much less powerful interface.

Edit: more advanced, or even just a higher number of orthogonal use cases against the same data.

Re:90% of software engineering done today is integrating poo... by scarface74 on Monday May 02, 2022 @04:36AM (#31232638)
Have you used LINQ? LINQ is basically just a slight variant of SQL. All data is related, the only difference between a document type model like Mongo or ElasticSearch is how it stored and retrieved.
Re:90% of software engineering done today is integrating poo... by jseban on Monday May 02, 2022 @07:18AM (#31233686)
I've only been introduced to it, but I did get the impression that LINQ is probably the best SQL abstraction, and that it's much better than Hibernate, which is what I have the most experience with.

I think the whole framework situation in general is much better in microsoft land because it's one company that designs the whole ecosystem, and overall experience, and also the people with probably the most experience in software development. I even think VB6 is superior to the standard open source web development stack used today. The only part where MS seems to be behind is version control.

Re:90% of software engineering done today is integrating poo... by scarface74 on Monday May 02, 2022 @09:16AM (#31234737)
Oh Hibernate sucks. LINQ is built into the language not a bolted on library.

How can MS be behind in version control? TFS has had git support for ages and MS owns GitHub.

Re:90% of software engineering done today is integrating poo... by shroompasta on Sunday May 01, 2022 @08:51PM (#31230239)
I found it significantly easier to set up table structures and migrations through ORMs and abstractions as opposed to raw sql scripts.

Moreover, many ORMs give you the tooling to validate data before hitting the db, which is also another huge plus.

I mainly work with Python on the backend, and I've recently switched from SQLAlchemy + marshmallow + alembic to SQLModel and both have been amazing to work with.

I would never dream of setting up tables through plain raw sql ever again.

If it is the case that I'm moving onto a different language, as Go may be it, I'm willing to learn the ORM, granted that it deals with migrations and validations out of the box.

Re:90% of software engineering done today is integrating poo... by beej71 on Sunday May 01, 2022 @06:48PM (#31229486)
I get this sentiment. But I think it's not so much that there's a framework but rather that the framework is an I'll fit for the problem to be solved. So you "fight" with it.

In general, it seems like the easier it is to do something in the scope of the framework, the harder it is to bend the framework to do something outside it's scope.

We've all seen this with frameworks that make 95% of the work really easy, and the remaining 5% is like pulling teeth. You're bending the thing where it's not meant to be bent.

(And that's when new frameworks are made. :) )

But if you go lower, under the framework, it's way more flexible. As a dev, you can explore and create instead of fighting. Which is great.

But really we're just on a different turtle. Raw JS has a really hard time with some problems when you try to bend it wrong.

Our job is to take the right technologies for the job and make them work, no matter how abstracted they are. The pain is merely from the wrong tool. And, truly, it sucks when you have to do that.

Re:90% of software engineering done today is integrating poo... by scrozart on Sunday May 01, 2022 @04:29PM (#31228368)
We use a pretty jank framework at my professional gig, and are thankfully finally beginning to plan a migration to the much better documented framework it rips off. A full rewrite is almost never worth it, but between the already poor and now mostly out of date documentation, and the apparently diminishing community, there's not really a better route.

All that said, every other framework I've ever used in my personal projects has fine documentation and community support, including their peripheral deployment tooling. My experience at work seems like an outlier to other tools I see. Comments like the original post and OP make me think everyone is working in legacy systems based on aged tech from the cowboy era.

Re:90% of software engineering done today is integrating poo... by grishka on Sunday May 01, 2022 @05:26PM (#31228831)
Yes, this. There's a reason I avoid complex abstraction layers that helpfully "hide" the underlying platform from me. So, yes, in my hobby project that's a server application in Java, I use a simple, easy to understand micro-framework (sparkjava.com), a simple template engine (pebble), and a homebrew SQL query builder on the backend, and vanilla JS (compiled from TypeScript) on the frontend.

Every dependency is a liability, especially the kind you can't remove without rewriting your entire project. Adding a library to my project is a very serious thing for me.

Re:90% of software engineering done today is integrating poo... by pojzon on Sunday May 01, 2022 @04:06PM (#31228199)
Company: “We dont want you to write code, because finding ppl who understand the code is hard, while finding ppl who eat generic pulp is easy”
Re:90% of software engineering done today is integrating poo... by wackget on Sunday May 01, 2022 @05:05PM (#31228659)
As a recently-retired Magento developer of ten years... this speaks to my very soul. I've sworn to never use Magento again.
Re:90% of software engineering done today is integrating poo... by krainboltgreene on Sunday May 01, 2022 @02:47PM (#31227570)
> "You don't want to write "raw" html/js/sql/Java" Uhm I thought that was my job.

I mean it isn't your job and it shouldn't be. Your job is to make software handle with consistency some business process or become an extended memory of some business people.