The moment they can read. Sure you can literally define structures and processes before that, but doing the real deal on a computer before you can read... is going to be a disaster.
You need to read your own code to get your bearings of where you are in the file. Anything more complex than 5 instructions is a no-go for non-readers.
Coffee is fine. Butter is fine. Mixing them together is nothing special.
Adding butter does not help you lose weight. At least not directly. It could help you feel satisfied so you end up eating less than you may have otherwise.
Both. Tabs for indents. Spaces for alignments after the indent level is reached.
Everyone can view code with their preferred indent width.
Perfect solution with no flaws or drawbacks. Maybe 1 drawback, it requires advanced tooling (emacs smart-tabs-mode) to automatically handle the indentation/alignment.
Indent width is a visual effect. Mandating an indent width with hard spaces is like mandating the color scheme.
Only drink a reasonable amount (not enough to impair) during special occasions. Never drink on the regular. Small amounts can be evil too if taken regularly.
I know a guy who drank a 6 pack of beer every night. Never drunk. Just drinking on the regular. Until his liver gave out, and he couldn't work. Died at age 34 while waiting for a liver transplant. Left wife and kids behind.
My friend's mom died in her 50's from liver failure. Heavy drinker for decades.
Drinking less is better than drinking lots, but don't think it can't kill you.
Go for the 60k job.
Seriously. This is your best option for your immediate income and future value.
You will have a head start over your peers who won't even enter the work force until age ~23, with college debt to boot. Go for it and don't look back.
The path to career advancement is to have a job, learn everything you can, then hop when you find another offer with a big bump in pay.
Emacs for everything. If I start a using a new language I'll hand craft snippets, wire up with any linters or external completion engines and other tools.
If there is no good completion solution, then I'll cheat. Grep to the definition (or jump with tags), open it in a buffer and I can look at what is there. At that point the members are now available for "dumb" textual completion. I'll create helper function to do this.
Give me a few hours and I can match just about any IDE feature. The mechanical parts of the workflow are crazy fast and fluid.
Unless you're hyper sensitive about work environment, go for the money. It's nice to enjoy your work, but don't screw yourself out of career advancement.
Sure, server side software avoids update issues, piracy, and fits naturally in a subscription model (more $$$ over time). No argument there, but those are considerations for the seller, not the consumer (me).
As the consumer, I don't like server side software when running locally is a more natural fit.
Client side programs will work forever, even after you go out of business. As long as the system it runs on doesn't evolve out from under it.
It has a feeling a permanence. Of an heirloom. Not some ephemeral service. A feeling of ownership like a hammer in your hand.
It may not be as good for you, but if it's software I want, where running locally is the most natural fit, I will glady pay several hundred without blinking. If I really need it I'd pay a few grand without blinking.
You need to read your own code to get your bearings of where you are in the file. Anything more complex than 5 instructions is a no-go for non-readers.