To be fair it is stupid that NaN !== NaN but that is how IEEE and CPUs made floats to be
3,756 karma · joined January 23, 2019
http://unsongbook.com/
My guess is it will be the weirdest book you will have ever read.
If it is not, please, I am curious about what is your weirdest book :)
To be fair it is stupid that NaN !== NaN but that is how IEEE and CPUs made floats to be
the anti-cloud-use license would include it, with no need of a separate release
Very likely there will be a lot of parts of the app you are not going to understand, those will be the main problems so help claude help itself.
Make it add diagnostic/event-logs to every part of the stack and potentially even design implementations around traceability (eg avoid batch background processes that touch many flows if possible). so that claude can check whether runtime behaviour matches expectations. also store historical data to help debug regressions.
Treat implementations as cattle not pets, once a feature is done consider scapping it and turning it into a design doc, then ask claude to reimplement interactively with you step by step explaining to you what is going to do, why it matters, etc. this is a very good way to minimize the black boxes you don't understand in the app.
if the app is web make it work very well with playwright for e2e ux tests.
finally i like the architecture given in https://www.youtube.com/watch?v=4KvbVq3Eg5w (use ui composition to define feature) but this has little to do with claude
If a bunch of good people acting in good faith produce a result an evil mastermind would want does it matter if they are good? On many levels obviously yes, on some practical levels the system and the incentives still need to change.
ht tp://[\x00::gg]\t/foo\nbar/%/%QZ/%F?q=<\"|{}>##also this one is valid too for the regex
%_%://%_%.%_%/%_%?%_%#%_%A parser that assumes the input to be already valid is usually not enough for most applications
according to that regex this is a valid url
__..__..%%%zz..
The difference between the 2 requirements is the level of technical knowledge needed and the necessary investment in tools
except that without a "prime minister" now there is no separation between the "king" and the fulcrum of political power.
The "lock on write" problem is that in MySQL i could run a OLAP pipeline for a few hours and have a fully functioning database with degraded perfomance, on SQLite the same pipeline would lock the database for the full hour. (there are surely ways to solve this (eg using the main db as read-only and a secondary db for writes or splitting the writes in incremental transaction), but it is not a "myth".
For better or worse they are much more well understood in C as they are front and center of the language semantics