Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Nextgrid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
331.
▲
by
Nextgrid
9mo ago
Cyberattacks are a good scapegoat for any large incompetent non-tech company that is unable to admit a mistake. (tech companies are more open to admitting actual mistakes - and reluctant to disclose cyberattacks even if there actually was o
332.
▲
by
Nextgrid
9mo ago
Self-hosted runners with Github is a whole world of pain because it literally just runs commands on the host and does not handle provisioning/cleanup, meaning you need to make sure your `docker run` commands don't leave any leftov
333.
▲
by
Nextgrid
9mo ago
The way I deal with all these terrible CI platforms (there is no good one, merely lesser evils) is to do my entire CI process in a container and the CI tool just pulls and runs that. You can trivially run this locally when needed. Of course
334.
▲
by
Nextgrid
9mo ago
If you're relying on AWS you either way have a "PC" to relay communication between AWS and the keycard readers & door latches.
335.
▲
by
Nextgrid
9mo ago
Software engineering is a great skill to have and can help you in your own business. But it is a terrible career in its own. Look into a trade. Technically-inclined like electricity, industrial automation, and so on.
336.
▲
by
Nextgrid
9mo ago
The puff number was extremely exaggerated on the disposable ones I've tried.
337.
▲
by
Nextgrid
9mo ago
I think that's handled by the barcode scanner itself, at least on the ones I've used. The scanner will not recognize the same code immediately, but will immediately pick up a different code. What's slow is that after each sca
338.
▲
by
Nextgrid
9mo ago
Some of these are just dumb terminals with the entire state handled on a server. I've seen a bunch of them freeze at once where no UI would respond (but the interactions were buffered) and then when the network hiccup was over they all
339.
▲
by
Nextgrid
9mo ago
And nobody with options would settle for the low pay and terrible working conditions, so the quality of the output also reflects that.
340.
▲
by
Nextgrid
9mo ago
The reason for moving away from physical keys is that key management becomes a nightmare; you can't "revoke" a key without changing all the locks which is an expensive operation and requires distributing new keys to everyone
341.
▲
by
Nextgrid
9mo ago
> Some PC somewhere with storage is a bigger problem Both an embedded microcontroller and a PC have storage. The reason you can power-cycle a microcontroller at will is because that storage is read-only and only a specific portion dedica
342.
▲
by
Nextgrid
9mo ago
> with redundant power, cooling, etc The doors the system controls don't have any of this. Hell, the whole building doesn't have any of this. And it definitely doesn't have redundant internet connections to the cloud-based
343.
▲
by
Nextgrid
9mo ago
If you’re using the circuit-switched mobile phone calls it’s unlikely you will be able to negotiate that; GSM compression is optimised for voice and not data. If you have a phone or cellular dongle with a serial interface you might be able
344.
▲
by
Nextgrid
9mo ago
I think the occasional burst of activity can and does work, but it’s a budget you need to spend strategically and let it recover. Constant 996 indeed won’t work.
345.
▲
by
Nextgrid
9mo ago
Depends what one considers “work”; if you’re only counting focused, active coding work then there are places where 4 hours is the max you’re going to achieve of that anyway.
346.
▲
by
Nextgrid
9mo ago
> there are corners of the world where it is less true than one would hope. And it's readily visible in terms of software quality and technological capability of the company.
347.
▲
by
Nextgrid
9mo ago
Maybe 15 years ago I would've agreed because there was genuine innovation in tech where you could actually be passionate and proud of building it. "I want to work here because I want this product to exist" could've been
348.
▲
by
Nextgrid
9mo ago
The jamming is expensive to maintain and not 100% effective. It's still your best shot.
349.
▲
by
Nextgrid
9mo ago
And pay them well. If you want people to build you a thing that prints money, you better give them a sizeable cut. Otherwise enjoy "market rate" performance.
350.
▲
by
Nextgrid
9mo ago
As usual, the problem is not 996 itself but comp. You can get 996, you just have to pay for it. The reason Europeans don't want to do 996 is because the extra effort isn't fairly compensated.
351.
▲
by
Nextgrid
9mo ago
Starlink and/or BGAN/satellite phones.
352.
▲
by
Nextgrid
9mo ago
I concur. I've seen a lot of companies outside the techbro world where the entire thing runs on a single VPS/dedicated server with a setup that would make any sysadmin squirm. And yet, it just works and makes them money? Which i
353.
▲
by
Nextgrid
9mo ago
> vendors are just as fallible as the rest of us One of the issues I have with this is the insane markups they're charging for services that ultimately aren't any better than what you can do yourself. If they aren't any be
354.
▲
by
Nextgrid
9mo ago
I don't understand the advantages of this over a laptop (this is essentially laptop-grade hardware and thermal profile but without the screen & battery).
355.
▲
by
Nextgrid
9mo ago
Simply moving the time at which the mistakes occur can be extremely valuable. Doing it yourself means you can say "no touching the server during business hours". You can't guarantee that with a provider. Even if you work out
356.
▲
by
Nextgrid
9mo ago
> I can run several distinct apps running different frameworks and versions > don't have to muck about with pm2 or supervisord or cronjobs, that's built in. I don't have to muck about with SSL certs/certbot But doe
357.
▲
by
Nextgrid
9mo ago
I've had an RDS instance fail in an equally-weird way that required manual AWS operator intervention 24 hours later, until which we were effectively locked out of our data and had to restore from a recent backup & rebuild the missi
358.
▲
by
Nextgrid
9mo ago
Bonus point is that with such a simple stack you don't need to phone them often because the thing just works. Most cloud outages are self-inflicted with the endless churn trying to reinvent things, not actual hardware failure. Just not
359.
▲
by
Nextgrid
9mo ago
Nobody that uses Kubernetes and random shit from Github would sign such an agreement if they actually had to pay out and could not weasel their way out of it. That would be signing up for a near-unlimited liability and business suicide. Let
360.
▲
by
Nextgrid
9mo ago
> could you do better yourself For this particular failure mode absolutely - this is amateur-level stuff that shouldn't have happened. You know how to make something that works keep working? Not messing with it. Of course, this does
More ›