In some ways Stack Overflow feels dated, but in some ways I hope it will go on; I still often prefer responses found there from the AI's. It also brings the recurring theme of what the LLMs will be trained on when people create less and less content. But I guess some people will always, and it might be enough
"The tool is designed to learn about users through questions and, if permitted, by scanning images stored in their phone’s Camera Roll to interpret interests and personality traits. Match says this data-driven approach will improve compatibility between users."
I wonder how it would be even possible. Especially, what lack of photos or their modest number tell about me :P
Interesting - I guess the main problem would be that most people do not have their own domains and use something like gmail, outlook or apple for their email; you would need to convince those big players to implement this standard as well; not impossible, but hard!
Interesting, but I'm not totally convinced that searching for LLMs is different than for us (humans). In the end, we both want to get information that's relevant to our query (intent). Besides, I wonder whether there will be able to convince big players like OpenAI to use them, instead of Google Search with its proven record :)
Got you :) I advise you to work on it and get over it - it's far more satisfying to mostly (not always) write about things others are interested in; people find value in your work and you have more impact at the same time; it's an overall win-win.
Great write-up :) I find hosting VPS on DigitialOcean/Hetzner to be the best middle-ground: you save a lot, but it still convenient; you just SSH into the thing, no need to think about physical cables, cooling, electricity and all the being physical baggage
But if the talent is globally available, thanks to the remote work, what difference does it (location) make? I know that it's still not 100% true, but I think we're moving in this direction
Well, interesting idea, but can you trust that it generates it properly? Because if it doesn't, then your understanding of the code will be incorrect, even worse than lack of knowledge; and if you do need to check all the things it has generated for you, as a description - doesn't it defeat the purpose of the tool?
That + OpenAI planning to lose money until at least 2030 might put into question the perspective of whether these LLMs business can sustain themselves in the long-run; increasing prices is one thing, but you will lose lots of customers together with this change.
As a European, I don't think we need one; I would argue that location is becoming less and less relevant, especially for building digital project. Finding your market niche and fit is another thing, but building the thing can be done from anywhere, by the teams of people located everywhere
Interesting, a few questions:
1. How hard/easy is it to make responses dynamic, i.e. to use something from the request data like query/path param or a body to execute function instead of hardcoding the response
2. What's the main motivation for creating this tool? I feel like every programming language have similar tool already - WireMock for Java etc. Why should people switch?
Interesting, although something about the language makes me think it was written by a LLM; I like the ending though:
"The key insight is to treat container images not as opaque black boxes, but as structured, manipulable archives. Deeply understanding the underlying technology, like the OCI image specification, allows for advanced optimization and troubleshooting that goes far beyond standard tooling. This knowledge is essential for preventing issues like Kubernetes disk space exhaustion before they start."
SQLite has its quirks, but in this particular case all you need is set PRAGMA busy_timeout=<a few seconds> and the problem is solved; and if you google it, it's widely known issue with described (this) solution.
It's just weird that it's set to 0 by default rather than something resonable like 3000 or 5000 ms.
Exactly - it's also strange that they didn't find a simple solution of setting PRAGMA busy_timeout=N; if you google/search SQLITE_BUSY: database is locked there are plenty of solid results describing the problem and solution
Also worth mentioning - it happens more often when you set journal_mode=WAL, which is not a default.
The default is DELETE mode, where the rollback journal is deleted at the conclusion of each transaction. What's more - in this mode (not-WAL), readers can coexist, but they do block the writer (which is always one) and the writer block readers - concurrency is highly limited.
In WAL mode - which pretty much always you should set - there's also at most one writer, but writer can coexist with readers.
You should definitely be able to entertain all kinds of weird ideas - having open mind and always be willing to accept that you might be wrong - but also reject most of them, if they do not pass a smell test; after all, most weird ideas are just weird and wrong; nothing less, nothing more
Interesting perspective, agreed 100%; having UDP available in the browser would open up a plethora of interesting new use cases - games, video/audio calls without WebRTC overhead - and techniques to use. Ohh wait - we will soon have it! https://developer.mozilla.org/en-US/docs/Web/API/WebTranspor...
True; that's why we have companies with paid product who devote a lot of their time - arguably majority - to make the exact interfaces people want and understand:) it's a ton, a ton of difficult work, for which there is little to no incentive in the free software ecosystem
True, but you have to have a really intensive workload to hit its limits; something in the order of tens of thousands writes per second; and even then, you can shard to a few instances. So yes, there is a limit - but in practice, not for most systems
100%; often batch integration - pulling data from REST endpoint/endpoints in the background, with reasonable frequency like every 5 -15 minutes - is good enough ;)
This camp is far more pragmatic. They strip away unnecessary complexity and steer clear of overengineered solutions. They reason from first principles before making technology choices. They resist marketing hype and approach vendor claims with healthy skepticism."
We should definitely apply Occam's razor as the industry far more often; simple tech stacks are better to manage and especially master (which you must do, once it's no longer a toy app). Introduce a new component into your system only if it provides functionality you cannot get with reasonable effort, using what you already have.
I would partially agree. Speaking from experience, I can say that if you're naturally good at something, you can learn it pretty well even if resources are of poor quality. Obviously it makes all the difference if they're good, but you get it easily in any case