I've actually followed learnopengl.com before, but I was looking for something more focused on the structure of a game engine. I have a book I'm following now, but it's skipping huge parts of the codebase and I'm having to reverse engineer the author's github. I'll just keep following that for now and maybe read Game Engine Architecture, too.
I told every employer who wanted me to take a timed test to fuck right off. One Sberbank (biggest bank in Russia and THE techbro company neck and neck with Yandex) interviewer started talking nonsense about git rebase destroying data and I called him a retard and hung up on him + 5 observers. (They'd wanted me to shutter my business as a condition of employment.)
Last time I was looking for a job, I answered "lmao idunno lol" to these. I'd considered having SOLID and OSI open on my screen but decided against it, and now I have a rewarding job and the greatest boss ever (no he's not reading the Farms). The bulk of the winning interview was me autistically talking about my collection of Django recipes and writing a data model for public transport timetables.
It's been awhile since I've done game stuff myself, but I would imagine pygame is probably still good.
Godot would be a good fit for you. GDScript is python like in syntax and you can easily start from templates if you just want to get something up and running.
Ahh, DB systems lectures, those really were the good times.
Have you looked at Qt?
I really don't find value in learning anything in programming like it's a certification test you've got scheduled for next week.
Tailwind is great if you are generating your HTML and don't want to write in CSS. Really all that Tailwind does is bundle a bunch of common styles into classes, it allows you to mix and match style classes locally on your tags rather than going back and forth between your display code and CSS files. If you're writing static HTML though you will want to style two elements the same way and quickly develop a throbbing pain in your head as you write out the same
class="a b c d ..." stack in every single element.
Bootstrap is a lot better. Having to "compile" your stylesheet classes can become a hassle if you want to make quick design changes if you are building out a UI.
I would say yes.
item, _ := someCollection.Find("whatever"), this has bad code smell), and you check for nil pointers (try to avoid using pointers in general unnecessarily), you won't have too many surprises, and when you do have a surprise, it's not hard to fix.
I'm liking Go a lot. It's like C in that I have the power to do basically anything, but it's like Python in that I also have the power to let the compiler figure a lot of it out. Control when I need it, ease of use when I don't.
" somewhere in your code.
I'm using it for my latest project after not having used Go for anything in many years. I really like writing it; it's easy and makes intuitive sense as a lifelong C programmer. Go has goroutines and channels (basically just queue structures), which make async programming a breeze. Plus, it's a Jewgle thing, so its support for web services is excellent.
type structA struct {
fieldA someType
fieldB someOtherType
}
func (a *structA) someMethod() {}
type structB struct {
structA
fieldC yetAnotherType
}
// Then you can access structA fields and methods through an instance of structB.
// Suppose b here is an instance of structB. I don't feel like writing out a proper def.
someVar := b.fieldA
b.someMethod()
Go's concurrency model is actually really good imo. Clojure's core.async uses a similar model and it's genuinely nice to work with
