Engineer I guess... Thief is the objectively better enterprise programmer option but I don't know why I always forget about it and just write a ternary ¯\_(ツ)_/¯
Xiaomi makes Android phones, what would they get out of trying to make iPhones look better.
Most likely explanation is the voltage difference people have mentioned
"You can never tell with Americans"?
What does that even mean lmao. Do people outside of the US not make jokes or lie?
Played the demo on steam, and the games were really fun. This pack feels a little different in that the couple of demo games were very "oh wow we could actually sit down and play this game" vibes vs. Just a quick thing to throw on in the background of a party.
This makes a ton of sense and I think you probably solved this mystery for me.
"Oh I need to iterate over something, and keep track of new information as I do it, therefore I should be able to create 'dynamic variables' as I progress."
I distinctly remember asking this question during a 100 level programming class but I just can not remember why I'd ever want to do this?
What problem could I have possibly have been trying to solve where this would seem like the answer.
Ok boomer
I feel like you're missing out on a ton of awesome features by not using a debugger? Step backs are super useful, inline/live commands save you from re-running the code to see a different value, you can change values on the fly.
And it's nice to say "think about your code more" but when you're working with large teams, on legacy codebases, you don't often have the opportunity to "think about your code" because you're trying to decipher what someone wrote 3 years ago and they don't even work with the company anymore.
Its wild to me that some people hear "your code should be self documenting" and take that to mean "never write comments".
All self documenting should mean is I can look at a method and get a general understanding of what it does, and it shouldn't have any unknown functionality. Specific implementations, design quirks, choices that might only make sense if you know business context should all be comments in your code.
On the other side of all that I worked with someone who insisted methods were documented college style, the "authors" name, date it was written, what it does, why it's here, our star sign. I hate that just as much, so much clutter.
What part of wefwef would cause an issue? Unless the wefwef devs are using visual assets from Apollo that are not free to use, there's no issue.
You can't sue someone for... What? The visual placement of buttons? How the animations work? The entire software industry would collapse overnight if we couldn't re-use design patterns.
My problem with trunk based development is I feel like people treat it as the solution to a problem that is fundamentally a developer culture problem.
You need to commit small changes, frequently, which requires you to only change small sections of the code and make incremental changes, something which can be a difficult habit to get used to.
This is really the main benefit of trunk based development, and it's something you can get with feature branches as well, you just have to make sure everyone on your team starts reducing scope of their features and merging in smaller and smaller features sets.
There's nothing inherit in the trunk based development model that stops someone from sitting on changes for a month, never pulling, and then trying to pull and ending up with a bunch of conflicts anyways. So it really feels like "yeah use trunk based development" boils down to "integrate continuously" which can be done with a branching model.
Letterboxd is pretentious, which is a good way to find ✨cinema✨, but if you just want to turn your brain off and watch an Adam Sandler movie or something, letterboxd is not the platform to look at reviews