We've banned this account. Please stop registering accounts to break the guidelines with. It's such a pointless waste of everyone's time. Find something useful to do, really.
You could easily imagine structural issues driving this. It's pretty unsatisfying to get refused for something that 'should' be handled and also to be dinged for doing something dangerous. You see this stuff in human organizations all the time.
I would hope writing C code for the Linux kernel qualifies you as a real C programmer. And yet, here we are. Being good, careful, and extensively reviewed by others helps, but is clearly not enough.
Yeah this is the real issue. Ironically Nespresso pods are probably more environmentally friendly even if thrown in the trash and not recycled because the real environmental burden comes from the coffee itself and those pods are highly efficient in terms of how little coffee is consumed per shot.
I still drink coffee regularly so am not going to say people should stop doing what I continue to do but it's worth it for coffee drinkers to be thoughtful about the impact of their consumption.
Apparently producing coffee beans for one large coffee uses 140kg of water. Ok, that sounds like a lot.
But also apparently producing one meal worth of chicken takes 700kg of water. Over 3000kg of water for beef. So I think, in comparison, coffee water use if negligible.
I'm interested in knowing more about the company itself. How many people is/was it? Were they working all in an office together or local-remote, or fully globally distributed? Was the focus massive scale, or ultra-low latency (for agent iteration), or agent-first (but human in the loop) usecases that could be enabled by having core control of a git service and the wrappers around it?
You probably need admin/write concepts in order to change users, rotate keys, allow/disallow IP ranges, network setup, etc....
Still totally agree that there should be guardrails around the core functionality but it's easy to imagine that the thermostat would be something one would expect to be able to control once you implement all this remote functionality.
You need none of that if it's truly broadcast only. The network or receiving system can be configured to accommodate the device. A hardware button and screen on the device can be used to regenerate a key, although that is probably necessary.
I still wonder if AI will be designed to have flavor profiles like coffee. Right now I don't think alot of product thinking has gone into this line (maybe it has??) but I suspect that AIX (AI eXperience) design will become more and more of a thing as the space matures.
I'm sure to some degree people (and AI being used to build AI) are kind of doing this thing but I don't yet think that OpenAI has a distinct flavor profile for their models that they have standardized on and are intending to lock into over time.
When I go to Starbucks I know what I'm going to get and it's been reasonably consistent over a decade plus and similarly that's true of other coffee shops which have different profiles. I'm expecting something along those lines.
Links are almost an anti-pattern. The reader should not have to click links unless they're really interested in diving deep on that particular topic (and ideally it's more of an endnote thing, not inline)
That's always been my concern - there's just so much garbage code out there and very few signals about which of it is well written and which is not ... so LLMs will just regurgitate the good enough code that it's been trained on.
Now would be the ideal time for everybody to give it negative feedback when bad code is returned but I'm afraid not enough people care and we'll just settle with what works just like we always have.
reply