Huh, this just gave me an idea (provided a few modifications and enhancements to the noids) to create a god game with true emergent behaviour (yes, that's not very gamey like, I know, it can collapse for no reason). Let's see if I'm smart enough to pull it off (note: I'm waaaay over my head in this)
I must say, I find the experience curious to say the least. It prompted me to write something, and I immediately got frustrated that my text was gone, followed by a feeling of "well, it was ephemeral anyway" and then finding the reader mode and say "hmmm, does that take away from the experience?". In any case, I might come back to this every now and then, nice work.
Thank you for trying it, and for staying long enough to find the reader mode.
The frustration at the start is real. It doesn't fully go away. But for me, it slowly became something else — a feeling of gently letting go of what I'd written.
I thought hard about the reader mode. For long-form writing, an app where you can never look back is just too limiting. In the end, I decided to keep both.
We would have saved so many wasted hours in the last company I worked for if we had this... you have no idea, to give you a sense, the decision to move from a Neo4J db to MySQL (the service was failing, the DB was failing, it was a bad architecture decision) took 6 months, when it should have been at most a couple days discussion.
Nurture this, it will become a great tool in the belt for a lot of people
Do you mind me asking, what kind of problems did you run into with Neo4j? Did you encounter performance issues after the DB grew to a certain size, or did you realize that the data wasn't suited to a graph DB and weird query patterns started causing trouble, or was it something else entirely?
I'm considering using a Neo4j self hosted instance for a project, but having only played around with it in low-stakes + small-data toy projects, I'm not really familiar with the footguns and failure modes...
All that aside, plugging holes in a sinking database for six months because you can't come to a descision does not sound like a fun time :D
The first mistake was management not wanting to pay for Neo4J, so we were working in production with the free edition (no backups, only one database, lots of limitations).
The second error was that none of us had production level experience with Neo4J apart from what you just said, tinkering in toy projects at home or very low stakes services, so in the end, the schema that was created was a bit of a mess, you would look at it and say "well, it makes sense..." but in reality we were treating Neo4J as a twisted NoSQL/SQL interpretation.
The third mistake was treating Neo4J as a database meant to handle realtime requests from thousands of users doing filtering and depending on huge responses from external systems (VERY OLD systems, we're talking IBM AS400 old) while in an environment where each response depended on at least 2 or 3 microservices. We had one cypher query to handle almost all use cases, you can imagine what a behemoth that was.
In the end as I said, compound error between lack of experience, not analyzing correctly our needs and a "just go with it attitude" that to this day I'm pretty sure it cost quite a bit to the company. Eventually the backend team managed to move to MySQL (by that time I had moved to Ops) and the difference was abysmal.
Coincidentally, I've been toying with using concludia to make the argument behind a tech design for an upcoming project... when one of our teams is enamored with graph database for it - probably neptune in our case. So far I'm having trouble really nailing down the argument that would justify it.
I'd warn on the side of caution, moving from SQL to Graph is easier than undoing graph nodes, relationships and properties into a coherent SQL schema. Tread carefully :)
I built a time tracking app and control panel for ourselves at our company out of frustration (it was very basic, for compliance with spanish law) and eventually we just fixed so much stuff and added so many features that we just released it as a product https://workstamp.eu
We need to reduce the entry barrier (it's meant for companies so it needs explicit registration) so anyone can use it as a proper SaaS but so far we already have a couple clients :D
I'm writing this without reading the comments first but oh boy, I wanted to punch a stone wall while I was reading this. I don't tolerate any company that has more than 3 interviews for a position, it's an automatic "no, sorry, I have better things to do with my life", and I tried, believe me, Red Hat had 6, Creative Assembly burnt me with 2 personal and 3 technical, all on-site on different dates (edit for peace of mind: these interviews were 13 years ago, it's fine...)
Maybe it's my own personal working culture, but when I get into a company I'm not thinking about levels, growth, stock options... I go there with a salary, a position and a willingness to help in whatever I can, once I'm not needed anymore (it's usually a combination of managerial direction changes, new hires, new objectives) that's my cue to help somewhere else where I may be needed or wanted. Am I that weird? I honestly don't understand this culture of quarter finance agent, half developer, quarter manager aspirant :/
I'm working on a simple IoT visualizer. I built my own domotic system at home (which i hope to turn into a product at some point) and I had the need to visualize the sensor data per room and per floor.
While I was working on the tablet interface (in Godot Engine) I put Claude to work on what after two minutes became a full product on its own with a new file format as well. Tell me what you think! (so far the response is meh...)
Oh boy. I just set up my company a few months back, unfortunately I never had to go into email too much, so I didn't set up DKIM/SPF/DMARC. Then I started receiving emails from my own domain, I panicked because spoooofingg (read with spooky voice) and set up all three. I was bashed for an entire week with reports from all major email services with DMARC reports.
Fortunately I still only have a couple clients so no one was the wiser.
UPDATE: It ended up in a simple scare, nothing was affected and I'm not in any list that I know of, in case you're wondering
I have issues as well, each implementation (SDL/Jack/Pulse) is completely different, in some the shaders break completely, some don't respond to shortcuts or don't show the menus... it's a mess and the funny thing is that these are the same issues I had 10 years ago. The first thing that they have to fix is that each client works the same way.
