GitHub repo Updated 2025-07-16
List of AWS AMIs Updated 2025-07-16
Mathematics masters course of the University of Oxford Updated 2025-07-16
Open source oscilloscope Updated 2025-07-16
n-sphere Updated 2025-07-16
Phonetics Updated 2025-07-16
Red Hat Updated 2025-07-16
PhysX Updated 2025-07-16
Had hardware acceleration in mind from the very start, and for a long time that has meant GPU acceleration.
Software design pattern Updated 2025-07-16
Extraterrestrial life Updated 2025-07-16
Jim Baggott Updated 2025-07-16
NASA Updated 2025-07-16
Natural sort order Updated 2025-07-16
Navier-Stokes equations Updated 2025-07-16
Porting Updated 2025-07-16
Software testing Updated 2025-07-16
Rail transport in Great Britain Updated 2025-07-16
Raising and lowering indices Updated 2025-07-16
Ciro's Edict #4 Further improvements to the website's base technology Updated 2025-07-16
github.com/cirosantilli/node-express-sequelize-nextjs-realworld-example-app contains the same baseline tech as OurBigBook, and I have been use to quickly test/benchmark new concepts for the website base.
I'm almost proud about that project, as a reasonable template for a Next.js project. It is not perfect, notably see issues on the issue tracker, but it it quite reasonable.
The side effects of ambitious goals are often the most valuable thing achieved once again? I to actually make the project be more important thatn the side effects this time, but we'll see.
Since the last update, I've made some major improvements to the baseline tech of the website, which I'll move little by little into OurBigBook. Some of the improvements actually started in OurBigBook.com. The improvements were:
- got a satisfactorily comprehensive linting working at: this commit. Nothing is easy, not even that! Part of the wisdom extracted to: stackoverflow.com/questions/58233482/next-js-setting-up-eslint-for-nextjs/70519682#70519682.
- fully rationalized directory structure to avoid nasty errors that show up in Next.js when accidentally requiring backend stuff on the client. Commit. A detailed explanation of this was extracted to: stackoverflow.com/questions/64926174/module-not-found-cant-resolve-fs-in-next-js-application/70363153#70363153.
- create an extremely clean and rationalized way to do API tests from a simple
npm test. These now actually start a clean server, and make full HTTP requests to that server. Commit. Wisdom extracted to: stackoverflow.com/questions/63762896/whats-the-best-way-to-test-express-js-api/70479940#70479940. - greatly reduce the number of SQL queries, fully understood every problem
- more intelligently using JOINs where I have managed to get Sequelize to do what I fucking want. This also led to several sequelize Stack Overflow answers as usual: stackoverflow.com/search?tab=newest&q=user%3a895245%20%5bsequelize%5dEverything that I didn't manage to do because of crappy sequelize is documented at: github.com/cirosantilli/node-express-sequelize-nextjs-realworld-example-app/issues/5
- better understanding Next.js/React/useSWR do avoid doing double API queries
Playstation Updated 2025-07-16
Unlisted articles are being shown, click here to show only listed articles.