done
The original Roller Coaster Tycoon is famously written in assembly.
Sawyer wrote 99% of the code for RollerCoaster Tycoon in assembly code for the Microsoft Macro Assembler, with the remaining one percent written in C.
This always blew my mind, especially when struggling around with things like cmu bomblab back in the day.
I haven't thought about assembly in a long time, and not sure if I want to ;P
Looks like a nice detailed walkthrough though!
Do not
There are deployment methodologies that exists to avoid downtime which I posted about in [email protected]
Thanks for the content idea :)
TL;DR;
Rolling Deployment
Canary Deployment
Blue-Green Deployment
A/B Deployment
IDEs for this purpose (android dev) are not small little text editors that work well with limited resources. Keep that in mind. You will also need to consider things like compilation and phone emulation, which can also be resource intensive.
I highly recommend looking for something that is built with a Linux distro by default. This will make your life easier in the long run, although it may not be a simple task up front if you are not familiar with Linux.
I don't actually have a Linux laptop, it is a desktop, but I use my Steam deck as a Linux laptop, and can almost do everything I want to, although steamos will require some weirdness similar to Windows. I use IntelliJ Ultimate on my steam deck and can successfully work on smaller scale Go and Kotlin projects while running IntelliJ low power mode.
Most larger dev shops (in the JVM world) will just hand out whatever is the current top ~$3000 MacBook pro (for reasons). This leads to a lot of devs using OSx at work and Linux (at home) for personal projects. An apple computer of any type can help prepare for this inevitability, if Linux is out of the options. I personally dislike this, as I am not an Apple fan, but this is what I have experienced.
Although I use Windows for some personal development, there are so many hoops that one has to jump through to get Windows working properly for advanced things, it almost isn't worth it and requires heavy windows development knowledge, and is probably best to just get a MacBook (of whatever type).
I have found it quite effective while pair programming (senior to junior mentorship) to say OUT LOUD exactly what I'm changing and why I'm changing that. This allows others to more easily follow your train of thought and can lead to good discussions rather than turning PRs into essays.
However, as other comments have mentioned, this can get exhausting.
After looking at my subscribed, rather the community list as a whole, I'm torn between 1/2
I can help mod IntelliJ
I can't vote due to VPN, but the UBP icons look awesome, and I think using them across the board will look great. With specific language icons, can still use the actual icon with the modified color gradient (like git community is) and still gets the point across and looks great IMO.
not production ready vs. production ready
Yes, usually most things can be tested on a different branch and just set the workflow to trigger from the branch rather than main. There are some cases where this doesn't work great, however, like testing triggers for pull requests, since then you have to have a 2nd branch to PR to the test branch.
There is also nectos/act, although I don't personally use it, I have heard it helps with faster development of workflows (and saves cost if you are not self hosting runners).
Deleted as off topic 😅
I don't want to encourage off topic
~~I will get some baseline rules (nothing intense) added to the community soon~~ done
I am still fairly new to Steam deck (~6 months).
Outside of having the dock to allow for normal USB ports for both keyboard and mouse (without converters and such), this awesome steam-deck-tricks readme/repo is majorly where I have been learning from.
The major catch is rootfs read only and strategizing how to avoid reinstalls after steam updates. I haven't quite gotten all the way there yet since I am using it more for tinkering (linux host on local network) for the time being.