Everything else is the same. Will let y'all be the judge which is better.
Both where made in one-shot with this prompt:
Create a habit tracking app where users can create habits, mark daily completions, and visualize streaks. Include features for setting habit frequency (daily/weekly), viewing completion calendars, and tracking overall progress percentages.
Agreed. It is curious how the agent got nudged to add auth in that one.
I did another ad-hoc but this time I added "Use guest auth" to the prompt. This way you don't need to enter an email. Full prompt below
Create a habit tracking app where users can create habits, mark daily completions, and visualize streaks. Include features for setting habit frequency (daily/weekly), viewing completion calendars, and tracking overall progress percentages. Use guest auth
I read parts of it a while ago when I had an idea on using webRTC data channels to pass data from databases to browser clients via a CLI. Your book made me understand that it's probably not a great fit for my use case. I just used a centralized control plane and websockets instead.
I still feel like there is something fun that we can do with webRTC data channels + zero copy Apache Arrow arraybuffers + duckdb WASM, but haven't figured it out yet
You can't beat Websockets :) Especially since you have so much tooling/existing stuff that works with HTTP.
I have been trying to get a website off the ground that does Datachannels + SQlite in the browser and then users sync between each other. I have gotten distracted so many times though.
What is preventing the fun is that even though we now have IPv6 widely enough available we still can't have p2p connections in the browser without a cumbersome control plane of servers. If you could join a federation in the browser from some bootstrap IPs then I think we could have some real distributed fun.
It started with a founder's preference and also some desire to make a point (the point being that PHP makes an extremely solid foundation for web application development) and continued with it revealing itself as a useful attitude, skill and maturity filter when hiring.
I have felt this a lot when designing the landing page for my SQL canvas side project. _I_ really want to write about DuckDB WASM, pre-signed URLs and how cool Cloudflare's durable objects are.
But my target audience are data analysts, and they just want to analyze some data!
I have gone through a lot of design revisions because I have a hard time containing my technical excitement. I was surprised how hard communicating a product clearly is.
As a backend/data person I was on the high horse thinking that designers jobs are so much easier than distributed systems. Now I feel the opposite!
Maybe that's why I am not in your target audience, but love how the design looks. I have bookmarked it also.
You show so many features and it is nice in the way it is being presented and is also mobile friendly. Also I too am a fan of neobrutalism. :)
I remember p2hari commenting on one of my "What are you working on" comments, so maybe they got it from there. Anyway, here's the link: https://kavla.dev/
I totally agree on investing in a sane data model upfront. So many production systems have schemas that only made sense to the engineer that created them. I would be delighted if I can read a schema and understand what a column means without having to dig through a bunch of migration PRs.
I recently encountered `is_as BOOL` in an important table. After way too much invested time we found out it meant "is active service". </DDL rant>
I integrate with many ERPs and this is the bane of my existence.
One of the worst has field names like `ft_0001...N` and table names like `UNCC_00001...N`, all in `text` fields (even numbers!), zero FK, almost no indexes and what are views?
The other has this funny field that is a blob that need decoding using a specific FreePascal version. The field? Where is the price of the product.
Other has, in the same column, mix of how handling "," or "." for numbers and
I need to check the digital places to deduce which.
FUN.
P.D: I normalize all this Erps into my own schema and has get praise for things like, my product table is called products.
I may have worked with that one. Did it have a parallel schema that mapped tables and fields with legible/customisable names, so every SQL call had to join the mapping tables to hit the required table and fetch the fields you were after?
Wrote a Windows .Net program once upon a time to convert the data from other financial CRM systems into the system I worked on. Built a data mapping tool as no customer we onboarded placed "custom" data in the same tables or fields even when using the same financial system.
I actually miss doing that kind of work, my brain seems to be wired to find it fun. Writing SQL is one thing I don't delegate to an AI or even an ORM like Doctrine.
I think the best db schema I had the displeasure of working with was one where it was a requirement that every table and column name NOT have vowels, except for the few that could, and "the few that could" were governed entirely by a spreadsheet owned by the DB admin.
And so you got tables like LANDMRK and columns like RCR_RCRDR.
I work with an Oracle database like this. In the old days, there was a 30 character limit on column names, so you end up with conventions like no vowels. The limit no longer exists today, but the DBA continues to enforce the limit on new columns.
I never got an answer when I asked. This same government agency also got extremely mad when our dev manager upgraded the ASP.NET version for one project because it had some really useful features we were developing with. They deleted his permissions to deploy to production from there until the end of time, requiring us to email someone each time we wanted to update the application. It was great.
I recently switched from Shotcut to Kdenlive. Kdenlive's UX is much more intuitive. Lots of features, I still feel like a beginner, which is such a fun feeling!
I'm using it together with OBS to post short demo videos of my side project. I could use Loom I guess, but I prefer to keep my tech stack FOSS when I can.
Creating "non standard" video resolutions is a bit of a pain though. But I've solved that with an ffmpeg oneliner.
reply