fullstackchris

Don't you want the engineers who are language agnostic, and have seen many a many framework and can quickly learn any quirks from your existing team?

Every time I see anti framework posts I am forced to frusteratedly chime in. This mentality makes me fume... not all of us work on massive teams where building stuff without a framework is even an option.

And even then, whats really a "framework"? You could argue it's even the language itself. Android apps used to be written in Java, and now they are pushing Kotlin way harder (and it may even be the default soon). Everyone who wrote those JavaScript apps back in the 1990s without TypeScript, are they still just as maintainable as their TypeScript counterparts? Such a shortsided and ignorant view IMO.

I think what bugs me the most is any sort of purist mentality (about anything) in software engineering. WE ARE ENGINEEERS. ENGINEERS USE THE RIGHT TOOL FOR THE RIGHT JOB! It should NEVER be "always use X", "never use Y". Both X and Y exist for a reason, so they are both useful for some reason.

And again, because I'm an engineer, I've also built my fair share of apps in just "purist" languages, the classic HTML / CSS / JavaScript, so I'm not against the purist approach either. Again, right tool for the right job.

I agree that for bugs a simple list may be the most valuable or at least offer a good overview, but bugs are a world different from what is needed for feature planning / epics / sprints and so on.

The real problem is that any native developer is essentially slave to Apple or Google's requirements (or both!). Where or how did we go wrong with native development and applications? Its all owned (and thus gated) by these industrial behemoths. The web, for example, is a much more 'open' platform. There needs to be an open platform like the web that can be used on mobile devices.

How are you going to manage interantionalization, testing, sessions, etc. with just these tools?

(In before people say, "but that's all I need for my blog!" Fine. go ahead and do that then. I'm talking about international huge scale applications)

What you'll do if you stay the purist and need to implement aformentioned services is that you'll eventually end up with some sort of quasi-framework, but bad in the sense that only you (or perhaps your team) know how it 'works'. With most frameworks there are at least opinionated ways to go about implementing all these things, and you can find other teams and consultants who speak this 'language' so to speak.

Being a purist is fine, but it really grinds my gears when people assume vanilla is ALWAYS the solution, and it can 'easily' be applied to things like e commerce shops, huge shared tools, or big social apps. Hint: it can't, unless you like a lot of pain.

I'm speaking from an application level perspective (REST or GraphQL APIs and the like). Of course at deeper levels of networking there needs to be a concept of state. But the only reason I can think of somebody having to hand roll anything todo with TLS nowadays is that they are doing something very very specialized, or have gone down a very wrong path.

Though that did remind me, if you're doing websocket stuff I suppose there could be a considerable amount of 'state' to handle on the backend.

Of course it does. The entire concept of 'state' doesn't even exist on the backend (okay, outside the concept of a user session, but then that barely adds any complexity; perhaps you use the user's ID and that's it). Frontend you've got to think about async calls, which automatically brings three states: loading, success, and error. You may have multiple of these calls and each combination of all of them leads to some crazy complex rendering. It's turtles all the way down if you're a junior (or to be honest, just a lazy dev), it's very easy to make a mess and abuse a library as flexible as React.

From my experience the better you can compose your components, the happier you'll be. And there's nearly always a dead simple way to design something even if from the outside the functionality seems very complex, like this for example: https://codesandbox.io/s/react-text-highlight-2h0kvu?file=/s...

Here's one for you: whenever I have my second monitor plugged in, I'm muted on any video platform (Google Meet, Zoom, etc)

Free postgres you say? Check out Supabase: https://supabase.com/

And, if you can save 'snapshots' of a given fuzzmap to detect potential regressions and / or changes in general to the flow.

Do you have an example? I've seen TypeScript handle crazy nested types (and generics) with ease.

I really _wish_ this were true, but go look at a vareity of "modern" React projects. React is so flexible that I've seen nightmare implementations of what could be reduced to just a few short lines. Then people turn around and blame React as a 'garbage framework'. Then if you talk about a much more verbose and strict framework like Angular, people turn around and complain "I can't do what I want with this overly opinionated framework!"

Damned if you do, damned if you don't.

However, if you look behind the curtains of these infamous gripes (some of them so often repeated they are cliché), 99% of the time its people who just haven't spent enough time around a certain framework or language and go create a rant post (similar to OPs post)

You're free to love the tools and languages you use all the time. But it's bad practice to go around bad mouthing tools and frameworks you don't full understand or haven't used productively.

> relatively straightforward to scale out

Is this true for any technology, let alone database technology? I've yet to find one.

...and you managing your own secrets is way better than a third party?

wake up people, its all the same types of servers managing the same type of passwords with the same types of security layers, not one is better than the other! nobody has a 'secret sauce' to storing your passwords.

It's bullshit like this why I hate boomers and / or stuck up / and / or snobby / and / or ignorant software engineers, who, in the end, maybe aren't actually snobby, but just ignorant.

YoU cAn Go YoUr EnTiRe CaReEr AnD nOt UsE iT!!!

sure, this is true if:

- you don't work for / build / care about apps that have a persistence layer and serve more than about... let's say 20K daily users

- you don't care about perfomance

- you are confused

Postgres over:

- mongo: Postgres has ACID principles, where with Mongo you aren't sure you've saved ANYTHING at scale, there are multiple blog posts and humorous videos about them, i leave hunting them down to your discretion

- mySQL: don't even get me started, doesn't have any sort of plugin possibilities, is slower performance wise in literally ANY benchmark

- LiteDB: I know its the hacknews hipster rage, but seriously, you're going to rely on your entire backend via IO with a single file? ok, enjoy that one

sorry for the rant, i know it's not conducive to the hackernews mentality, but i've heard this rage and poking fun at postgres so many times, and nearly all have absolute NOTHING to with postgres' technical performance and much more to do with ego or some bullshit affiliation to some company and i'm sick of all of it and finally laying down the law:

Postgres is one of the BEST (if not THE BEST, bar none) databases currently available.

This is just scratching the surface of anthropology, if you want to go on a wild ride, read The Dawn of Everything by Graeber and Wengrow: https://www.goodreads.com/book/show/56269264-the-dawn-of-eve... Oxford also has a similar shop to Resilience / Consilience, the Future of Humanity Institute: https://www.fhi.ox.ac.uk/ Toby Ord is a member, his book The Pricipe: Existential Risk and the Future of Humanity is quite interesting: https://www.goodreads.com/book/show/50485582-the-precipice

Excellent. Asimov's "decay of empire" scenario approaches! (every living human eventually forgets how to repeat, or even interperet how the complex systems undergirding our entire society works, eventually rendering maintenance impossible)

Yep. And your "reuse-in-the-large" I'd argue is also a side effect of reality itself. Take any market sector or industry, not just software - I suspect the "easyness" of directly reusing and copying any complex system is vanishingly small. If that were not the case, we would have infinite choices and brands of any complex product ever made!

> The move from testing to static analysis

Are you claiming that static analysis of code can replace the concept of writing tests completely? If so, I'm very skeptical.

What language code is written in has little to do with how "flexible" it is. Or what did you mean? Refactorable? Readable? I don't immediately see what the choice of Python specifically has over other languages.

The northeast is pretty damn 'safe', as long as you can handle the occassional downed tree and subsequent power outage.

Armchairing here, but what exactly about Einstein's theory doesn't correspond with this so called "current cosmological model"? This article doesn't really state what, exactly, needs to be "revised". Because, as someone said farther up in the comments, as far as I know, Einstein's theory has been confirmed against every experiement ever done.

meh, the FBI, CIA, and all big tech already know you are at home... does it really matter if they know you are on the couch or at your dining room table?

commented further up with a similar sentiment but i'll comment here too. "rethinking mobility" will not fix how idiotically layed out most of our existing infrastructure exists today - especially large sprawling haphazardly built cities like LA and Austin

but this is just a bandaid on a much larger problem: our cities and highway system were designed and built in eras where the amount of cars on the road was a fraction of what it is now. I-95 has become a complete abomonation, and some e-scooters and bikes wont fix that

Yes, but this is certainly a key to their success. They bring people back even after 2, 3, days, or even a month! Duolingo doesn't care _when_ you come back, as long as you _do_ come back. I was an earlier adopter of duolingo, and it's amazing to see how huge they've become. Overall I think it's an awesome platform; they've done very well with the entire design and clean UI of the site / app.

Regardless, you can't ignore the far reaching affects of Trump as president and January 6th. Was it just a "phase"? Perhaps. But any scenario I can think of leads to more of this boneheaded nonsense. You can't simply say 'bah people disagreeing is not the end of democracy' and be done with it. The statistics are there; the US is far more polarized and contentious than it ever was before.

Super late to the party but suprised how dreaded Gatsby is. I've been using it since its infancy and I've only seen improvements. I can consistently build sites with it that get a 100/100 score with Google's Lighthouse tool. Wonder if anyone could chime in if they ever see this.

I'm of the exact same opinion, but I've mostly given up on repeating similar notions. I think it's unlikely to change: I read something once that there are about 20 devs on all of twitter that generate 90% of all the tech chatter and hype.

Some days it feels the everybody software industry puts their trust in a handful of famous ex-<insert FANGG> here or famous youtubers / bloggers and takes what they say as undeniable truth (Though this is true for nearly everything nowadays, everything trite, washed down, and summarized with no heart or nuance)

There's a great saying in German: "Die kochen auch nur mit Wasser" - They also cook only with water. Sure, some of these youtubers and bloggers are super smart and helpful, and there are brilliant people who have worked at Silicon Valley companies. But there are smart, helpful, and brilliant people at nearly every company around the world. It just so happens that not all of them blog, have a twitter, or have youtube channels.

Sorry for the oldmanish grumbling but the more I learn about this industry is that everything is about picking the right tool for the job, documenting the arcane decisions made, and managing all of those decisions. When you really start getting into the weeds, the (IMHO) junior level ideals of 'perfectly clean code' and '100% code coverage' rapidly go out the window. We're _maintainers_ of complex systems, not wizards with panaceas. 100% of the time it is picking the tool for the job, and know what you are doing with that tool.

Experimenting? Great. Learning something new? Great. Just don't lumber into your organization one day saying "we should do X or Y because its the hype, or Z said so". Many painful stories can be shared on this type of mentality.

All the content on this site are symptoms of not using Jira properly.

That is all.