tommy_axle

Most likely "In my experience" and "business analyst"

To a non-developer, or no code review, couldn't the AI model also generate buggy code that then made it's way to production and deleted data just the same?

npm package registry definitely down. Happened to be doing a package install and it kept 504'ing

Wasn't there something when this went into effect about the mid-year being the start so it is 10% in years 1 and 6?

Neat. Did you have any thoughts on json5 or hjson?

Working on some starter templates for going from plain English requirements to a ready-to-use applications in a few minutes. Are you a small team looking to go from Excel to something a bit more streamlined but would like to avoid a time-consuming and costly process? Schedule a live demo today. https://genatron.ai

That raises an interesting question. Are all of these agencies using the build from the Play/iOS stores or is there a build based on the audited public repo?

For using requirements, much sooner. See Genatron.

Yes it was only those two missing but it might have been specific to Linux (desktop). When on my phone it renders properly.

Is there supposed to be an icon next to the "Featured Products" and Leaderboard headings? Just pointing out that it seems to be a missing font/icon box for me.

Yes to gathering requirements but for everything else it might be possible. See Genatron AI

As a PM if you're gathering requirements and building too have a look at genatron.ai

This is one that can sneak up on you even when you're not intentionally exposing a port to the internet. Docker manages iptables directly by default (you can disable it but the networking between compose services will be messed up). Another common case this can bite you is if using an iptables front-end like ufw and thinking you're exposing just the application. Then unless you bind to localhost then Posgres in this case will be exposed. My recommendation is to review iptables -L directly and where possible use firewalls closer to the perimeter (e.g. the one from your vps provider) instead of solely relying on iptables on the same node

It's not only a few mins when deploying. Often you want to test the production build locally and it feels like waiting forever. Especially since clicking around in an app for the dev build is slow during cold use. I think it has gotten worse as I don't remember build times taking so long in next versions 5 thru 9 or so.

With sqlite3 -backup There's an online backup api

Good to hear. Even with edge you can have a request that blocks or does something silly so IMO it should have had node from the beginning. A common use case is verifying a session or authorization for an entire area.

The thing is that even on a simple site with html and css while creating it there might be issues that you can quickly catch something that assists you... tools. The page looks broken? Oh, being able to lint that html or css will quickly find any issues stemming from that but hey those are tools to introduce. Not a build tool as in generating an artifact in this case but often checking is part of that pipeline to avoid errors.

I agree that it's gotten pretty crazy for certain things over the years but there's a good balance in there somewhere and it's only natural to advance technologically speaking with the addition of tools.

Not a standard per se but nanoid seems to fit the bill. Widely implemented.

Yes, but you would also need to guarantee that content that does 3rd party stuff can't get injected.

"Paramount" has been that word for me. Last year it seemed like every response from ChatGPT included it.

There's also typescript-to-zod that makes it possible to generate the zod schemas from your types.

It's in the <7B club, but Phi has always had a good dose of synthetic data https://huggingface.co/microsoft/Phi-3-mini-4k-instruct

What he said at the start of the cnbc interview sounded like an apology to me. The first thing that came to mind was that's great but at the same time might be a problem for a lawsuit IANAL.

It is simpler but like everything else it depends on the application. For a private app you can generally get away with it. Something that's more public facing? The ID will most likely leak information. As systems mature and you introduce things like replication, having IDs that are more universal starts looking good. In general, starting off with a uuid like uuid v4 or nanoid is a good bet.

Next.js jumped the shark with the app router. The page router, though it wasn't perfect, was a nice fit and was an extension of the React way (at the time) by handling the client-side well. You got routing and some ability to execute certain things on the server-side plus basic api support. For everything else you could use a full express backend or even other backend languages/stacks. But like with many things, simplicity could not be appreciated and now you have this mess. It's time for a better alternative.

IP banning might be limited if they're already using a proxy network, which is par nowadays for avoiding detection.

What I gathered from the post was that one of the investigations was to ask what was on [some page url] and then check the logs moments later and saw it using a normal user agent.

Looks like HuggingFace is experiencing issues again (https://status.huggingface.co/) same 503 errors like yesterday morning.

"The 8 billion is nearly as powerful as the biggest version of LLama-2" - Mark

Can't wait to try it.

VPNs were being blocked over the weekend (I checked after seeing https://news.ycombinator.com/item?id=39883747) but as of today within the last hour or so it seems like it works again for both old.redddit.com and regular reddit.com so something changed.