Dunstabzugshaubitze

not a course but a book Eloquent Javascript, especially chapters 13 to 19.

The Book is about plain JavaScript and a big chunk of it is about javascript in Websites.

• spent time to generate/optomize your indexes.
• faster storage/cpu/ram for your rdbms
• get the data needed by specific services into the service, only get the data from a central place if you have to (spinning up a new instance, another service changes state of data you need, which is a warning sign in itself that your architecture is brittle...)
• faster storage/cpu/ram
• generate indexes
• 2nd level cache shared between services
• establish a faster datastore for often requested data thats used by multiple services (that might be something like redis, or another rdbms on beefier hardware)
• optimize queries
• generate indexes
• faster storage/cpu/ram

gittea ltd was founded without adhering to the governance model gittea had and also claimed copyright on atleast the name and logo of gittea. many felt a non-profit would be a better way to organize development and thats how codeberg e.v. came to be.

the problem is not, and never was offering support and service against money, you can right now start selling forgejo if you'd desire to, it was allways about how the project itself should be organized.

https://kalpadesktop.org/ is basend on opensuse MicroOS, a distro with atomic updates. this comes with KDE, there is also a version with gnome of which i forgot the name.

that is the selling point of the head first books, they all feature bad jokes and other oddities to help you remember what you've read. it works.

oh, i was not aware that there is a head first just about desgin patterns, thanks for the heads up.

And Archicture is something that gets more and more important for devs, because it's likely that the code we write is just a part of a complex system of which we don't control every part and understanding communication channels and the reasoning behind the setup of the system allows us to write our part in a way that it works well in the bigger thing and not something others (or worse, we) have to work around later.

• Refactoring by Martin Fowler, having patterns to help identify parts of code that could be changed for the better helps a lot.
• Test-Driven Development with Python, because testing is important and you should atleast have tests in mind when writing you code, even if you dont write them first. I like this one, because it's very hands-on.
• Head first java by Sierra and Bates, good introduction to programming with languages that offer object orientation and not as dry as the gang of four book, but definitely aimed at beginners
• Fundamentals of Software Architecture by Richards and Ford, working as a programmer often means talking with big picture people or being one yourself, and they have their own strange language.
• Domain Driven Design by Evans, for a similiar reason as Fundamentals of Software Architecture.
• Neuromancer by William Gibson, because fun is important ;)

Shredder's Revenge was a lot of fun, if this has local coop i'll buy it on release and visit my brother to punch some dudes :)

define "adhd meds".

Not taking a stimulant shouldn't cause anxiety or depression, but going cold turkey for antidepressants might after a short while and just not taking those is nothing i'd recommend in any case.

https://github.com/j6t/kdbg might be to your liking, but it is still a gdb frontend.

depending on the language you use there might be an IDE with a good debugger for it, if so i'd have a look at that.

have a look at venv for your future projects :) there is also some tooling to help with all the warts around python and packaging.

last bigger python project i was part of used poetry, but it's been ages, so there is probably a new cool thing i am not aware of.

Pike strikes me as more highbrow than that.