clncy

You can do it, but if you stuff that process up (e.g. touch the wrong tables/schemas) you’re now dealing with a more complex recovery.

Also are you applying migrations with CREATE OR REPLACE etc? I find that much harder to collaborate on than just standard code.

While I love postgres, I take issue with coupling too much application logic to the DB. It’s much easier to update/rollback stateless containers/cloud functions/VMs than to recover a DB.

I agree that it seems very improbable. The only possible malicious scenario I can imagine is that the Github repo is clean, but npm creds have been compromised.

It's so hard to triage this when no justification has been provided for the advisory. Was the GHSA released in response to npm pulling the package, or vice versa?

Many suggestions for workarounds, but if the GHSA is indeed accurate (all versions affected) then that seems unwise.

The beacon to be guarded at all times by Ralphie??

Exactly. More like changing the state of the system to reduce the observed behaviour while introducing other (unknown) behaviours

MS PowerApps, PowerAutomate and related offerings are truly awful products. I’ve given them the benefit of the doubt and been burned repeatedly.

Don’t tar all no/low code tools with the same brush though. I’ve had good success with Retool, for example.

No-code platforms are really DSLs wrapped in a nice UI. No-code platforms that are more open and developer focused typically let you actually dump out the app as a big bundle of config/DSL (e.g. a custom JSON format).

Maybe using LLMs to generate DSL code will produce better (and more maintainable) results than fully-fledged languages?

“In the land of the blind, the one-eyed man is King”

Agreed. Try inheriting a project that hasn’t been updated for a few years. Between the absolute dependency hell, and major breaking changes, there is huge temptation to just rewrite the whole thing.

Even a basic application requires layers upon layers of dependencies. Many of them are not as mature as people like to think either.

> And often it is so alluring that actual requirements and costs fly out the window. Need to scale... infintely? Just use Lambda Functions.

I don’t know why the author singles out Lambda. For many use cases their ongoing maintenance is close to zero.

I second the suggestion of Kevin Powell. As a backend dev who has always struggled with CSS, his videos really made CSS concepts click for me.

I also like the term Resume Driven Development (RDD) to describe this. Choose whichever technologies improve the developers resume the most.

Spot in with the automation! Too often people rush to build a new system without thinking first about the systems and processes that already exist.

The life span of the inverter also needs to be considered

Counter to that though, re-inventing the wheel is a great learning exercise.

People seem to equate wealth with materialism, but think of some of things having money allows you to do:

- Donate to causes you care about + get access to influential people to further those causes

- Receive top medical care for physical and mental health problems

- Drop everything to care for or spend time with sick friends and family

- Engage services like lawyers and accountants to make stressful problems go away

I could go on...

And sure, having money is not to going to guarantee things like good personal relationships. But it's a hell of a lot easier when you can throw money at many sources of stress.

It sounds like a plausible mechanism by which students in poverty experience poorer academic results though, even if it's not the only mechanism.

Even the time people don't want this year to last any longer than it has to