procaryote

8 ms·

91.
by procaryote 9mo ago
AI doing a bullshit job isn't a productivity increase though; it's at best a cost cut. It would be an even bigger cost cut to remove the bullshit job
92.
by procaryote 9mo ago
This makes a lot of sense and is consistent with the lens that LLMs are essentially better autocomplete
93.
by procaryote 9mo ago
As I understand it, NLP is pseudoscience. Rhetoric and persuation has long been studied by humanity, but that doesn't make NLP real
94.
by procaryote 10mo ago
It's a way to dig yourself out of the hole without a full rewrite, and with a smaller retraining effort for your developers.
95.
by procaryote 10mo ago
The best advice is probably "don't", as it usually is to most people setting out to design a programming language, and even more so for people setting out to do a mostly backwards compatible extension to a language that isn
96.
by procaryote 10mo ago
C++ is a katamari ball of programming trends and half baked ideas. I get why google built golang, as they were already pretty strict about what parts of the c++ sediments you were allowed to use.
97.
by procaryote 10mo ago
C11 adds a couple of nice things like static asserts which I use sometimes to document assumptions I make. They did add some optional sections like bounds checking that seem to have flopped, partly for being optional, partly for being half-
98.
by procaryote 10mo ago
Is modern C really much more complicated than old C? C++ is a mess of course.
99.
by procaryote 10mo ago
Lowering the barrier to create your own syntax seems like a bad thing though. C.f. perl.
100.
by procaryote 10mo ago
From your faq: "We maintain zero logs of your activities. We don't track IP addresses, …" Front page says "zero logs" Some logs, including specifically datapoints you have promised not to log, but you mean well (?)
101.
by procaryote 10mo ago
They're good enough for fingerprinting and matching against other logs. Also: > // What we DON'T collect: > - IP addresses (not logged, not stored, not tracked) > - Usage patterns (no analytics, no telemetry, no
102.
by procaryote 10mo ago
is that faster to say than do, or is it an accessibility or while-driving need?
103.
by procaryote 10mo ago
As in "always run a network firewall" or "keep the IP secret"? Because I've had people suggest both and one is silly.
104.
by procaryote 10mo ago
I don't understand your answer I'm afraid
105.
by procaryote 10mo ago
You can of course bet on not being very successful as a company. If you can keep the number of users down you simplify a lot of things
106.
by procaryote 10mo ago
I get the impression that pico with micropython does this pretty well. You can ignore the second core and PIO if you don't want them. They won't hurt you.
107.
by procaryote 10mo ago
CMake doesn't spark joy, but it's not something you need to touch constantly. I figured out how to set up a basic cmake file and now I mostly need to touch it to set a project name, add or remove modules etc. It was a while since
108.
by procaryote 10mo ago
The raspberry pico is much nicer to work with, if you're looking for an alternative. It has dual core if you need it, and the fun little IO coprocessors if you want to get really low level. The pico2 even has a risc-v mode The process
109.
by procaryote 10mo ago
It's a nice ambition, but it's a different thing than memory safety
110.
by procaryote 10mo ago
Of course things are easier if you can run all your code in one binary on one machine, without remote users or any need to scale. As soon as you add users you need to start coping with backwards compatibility though, even if your backend is
111.
by procaryote 10mo ago
If you've run a microservice stack or N at scale with good results, someone saying it's impossible doesn't look pragmatic
112.
by procaryote 10mo ago
> or they had other requirements that necessitated microservices Scale Both in people, and in "how do we make this service handle the load". A monolith is easy if you have few developers and not a lot of load. With more develop
113.
by procaryote 10mo ago
You usually can't simultaneously deploy two services. You can try, but in a non trivial environment there are multiple machines and you'll want a rolling upgrade, which causes an old client to talk to a new service or vice versa.
114.
by procaryote 10mo ago
You solve a bunch of them by not using javacript in the backend though
115.
by procaryote 10mo ago
Why do all services need to understand all these objects though? A service should as far as possible care about its own things and treat other services' objects as opaque. ... otherwise you'd have to do something silly like update
116.
by procaryote 10mo ago
If you can rely on memory errors panicing before the memory error can have an effect, you're memory safe. Memory safety doesn't require "can't crash".
117.
by procaryote 10mo ago
Stop having backend and frontend teams. Start having crossfunctional teams. Problem solved.
118.
by procaryote 10mo ago
I've been at an embarassing number of places where turning off server side rendering improved performance as the number of browsers rendering content scales with the number of users, but the server-side rendering provisioning doesn&#x2
119.
by procaryote 10mo ago
I don't need my boss to care about me. I need them to care about the team succeeding, and the mission I signed up to. I need them to show some very baseline decency and honesty so that I can somewhat trust what they say. I need them to
120.
by procaryote 10mo ago
Caring and showing you care can be independent. Some people care and don't show it. Some people don't care but pretend to. If you don't care, showing you care is harder, and your acts might betray your true feelings

More ›