dontJudge
Yes. This is the start and the end. Bankruptcy will stop lenders from making predatory loans. It puts risk on both sides.
Tuition costs will naturally (and quickly) drop. Because there will be fewer people able to pay a crazy loan fueled price without a crazy loan given to them.
If you take merit into account, it could cause an imbalance. For example you may end up with too many Hispanics or women due to their high merit.
If it's the kind of work you want to do, I'd say stick with it.
It uses a rep scheme called "ladders". Ladders allow you to sneak in a high number of reps overall, even using heavy weights. Plenty of rest between sets. On the heavy day you end up doing 75 clean/press with heavy weight per arm. And 75 pullups. I never realized there was so many reps until i actually added it all up.
--Avoid sugary drinks.
--Avoid desert foods like cake, donuts, etc.
--Don't over eat.
Good 2 go 4 life.
Keybinders dream. Custom functions easy to whip up and assign to a key. It has a few arcane keybind ideas like hydra, that aren't even on the radar of other IDEs. The hydra takes vim, spanks it, and sends it to bed.
The place Emacs traditionally falls short as an IDE is intelligent code completion. But with LSP this will get better.
A good example is dogs. Humans controlled their breeding to promote certain attributes. Resulting in new types of animals that never existed in the wild.
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.
:help
:only
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.
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.
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.
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.
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.
Compare pay + benefits - cost-of-living.
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.
One vote for the UI being great just as it is. Mobile and desktop.
Don't apologize for it. Every idea about society has been tried a dozen times over. Capitalism has the best track record. Some of the worst hell holes on earth had great intentions in the minds of their leaders.
Cheating because it's not a lisp. But it was created by a schemer who originally put scheme in the browser (before he created javascript). Not what I prefer, but it's the most lisp-like language I actually use in real projects. The support for closures, lisp-1 invoking functions from variables, and dynamic typing feel very scheme-like.
If your versions are a straight chronological sequence it's straight forward to advance from any past version to any future version. Run each patch till you arrive at the desired version.
If you branch out in multiple forks it can be a little tricky. I've never had this situation, but I would treat each branch as a separate chronological sequence of patches. Unfortunately merging doesn't work with "patch" style development, so this could be a duplication nightmare. I guess nothing is perfect.
If the customer can make unrestricted modifications to their DB (unknown to you), you're out of luck. Versions are no longer under your control and generating with a diff is the way to go. But in that case the diff seems even more dangerous. Will it destroy their custom modifications?
Generation of the deployment script using a diff has so many holes. Renames can be misinterpreted as drop/create. It falls apart with data to insert/deleted. Ordering can't always be calculated.
The nice thing about a shotgun is a large amount of energy is transfered into the person. Unlike a hardball bullet from a rifle that may go straight through like a hot knife through butter. There are special rounds for rifles designed to fragment and dump all the energy into the person (but these are lethal).
You can't list everything. People invent their own self-identities which contradict any pre-defined list. Some categories are not yet politically correct such as people who identify as trans-racial.
If you make a truly complete list then you will get fired. I guarantee it. Some things people identify as are really far out and not socially accepted anywhere.