Might as well start with a solid foundation from the start though. The extra work is minimal so there isn't much of a time cost to it. I wouldn't call it overengineering, it's just a different way to write code, and the way many naturally default to without really thinking about it.
How many ~hours per week is expected for the role, and are there any particular day(s) when most of the activity is happening.
I'd be happy to help out.I live in Norway with active hours ~05-22 CEST. For more personal information, feel free to DM. My discord username is the same as this username if you prefer that.
I get the point the author is coming from. When I was teaching first year engineering students programming, the one on the left is how everyone would write, it's simply how human intuitively think about a process.
However, the one on the right feels more robust to me. For non trivial processes with multiple branches, it can ugly real quick if you haven't isolated functionalities into smaller functions. The issue is never when you are first writing the function, but when you're debugging or coming back to make changes.
What if you're told the new Italian chef wants to have 15 different toppings, not just 2. He also got 3 new steps that must be done to prepare the dough before you can bake the pizza, and the heat of the oven will now depend on the different dough used. My first instinct if my code was the one on the left, would be to refactor it to make room for the new functionality. With the one on the right, the framework is already set and you can easily add new functions for preparing the dough and make a few changes to addToppings() and bake()
If I feel too lazy to write "proper" code and just make one big function for a process, I often end up regretting it and refactoring it into smaller, more manageable functions once I get back to the project the next day. It's simply easier to wrap your head around
heatOven()
bakePizza()
box()
than reading the entire function and look for comments to mark each important step. The pizza got burned? Better take a look at `bakePizza()` then.
All it took for me to switch to GitLab was a larger free lfs quota which I wanted for a project. The superior webpage UI made me migrate every old project to it too.
I assume you meant that both Rust and C compiles into machine code? Python compiles into bytecode that is then run in a VM, Rust and C usually doesn't do that as far as I know.
I was mostly curious if it was as easy as in C. Turun's reply answered that question though. Cheers.
The game has just launched and the mod had been released and cracked already. This isn't about making bread, it's clearly a trivial hack for him to do, not something that requires full time job maintenence.
People spend hundreds of hours modding free of charge, what he does is a joke in comparison if we are talking about lost time that could have been spent earning money. The groundwork was made by Bethesda, AMD and Nvidia.
Hexbear is/was the main reason I really wanted a per-user instance blocklist. Even though I never interacted with them, it was annoying to see them flood posts with awful takes. Glad to hear they banned us.
Not all that interested in defederation of the mentioned instance, but I'm curious about the DMCA justification. Do they have active requests they are ignoring, or is it just theoretical scenario for now?
What is the implication of this for future potential defederations. I don't expect instances in Russia and similar countries to care much for western DMCA requests.
Python are fine with whatever number of spaces you want to use. You can use 8 spaces which forces you carefully consider each nest, you can use 1 if you're a monster, or you can use tabs if you're enlightened, python only demands consistency.
VSCode uses electron so it's not exactly a lightweight text editor, way overkill if you just want to read a simple .txt. Add on the fact if you got way too many extension, it will be even heavier.
Nothing you said other than expenses is an argument against nuclear. If anything, the take from you argument is that we should construct even more nuclear, not less.
It'd honestly the funniest thing I've read on this instance. Puts programmer humour to shame. Love it when developers finds the jankiest/unconventional way to solve problems.
You genuinely think it's faster to make a Web query, wait for search results to show up, click and wait for the correct webpage to load, navigate to the download page, download the exe, run the exe and go through the pop up menu than it is to type apt install x?
UlrikHD @ UlrikHD @programming.dev Posts 6Comments 150Joined 2 yr. ago
Might as well start with a solid foundation from the start though. The extra work is minimal so there isn't much of a time cost to it. I wouldn't call it overengineering, it's just a different way to write code, and the way many naturally default to without really thinking about it.