If anyone has a workflow where "severity" is important for your decision-making, I'm curious to learn about it.
3,780 karma · joined February 17, 2013
If anyone has a workflow where "severity" is important for your decision-making, I'm curious to learn about it.
- With the Lambda ISA, your remaining balance is forgiven after 2 years of payments, while the federal income-driven repayment plans require 20-25 years of payments.
- Lambda ISA has a fixed dollar "cap" (currently $30k), but the "cap" for income-driven repayment plans is however much you borrowed + interest that accrues over the life of the loan.
- Most importantly, the Lambda ISA is for a much smaller amount of money. Very few of the news articles about student debt profile students with a balance of only $30k. The horror stories tend to be students who borrowed >$100k, often for graduate study.
That exists: https://studentaid.gov/manage-loans/repayment/plans/income-d...
It's also a topic that most people are unlikely to pick up on their own, even if they are somewhat motivated. Working through the exercises in a math textbook doesn't give most people the "feeling of accomplishment" feedback loop that e.g. playing with a new web dev framework does.
For those reasons, I would highly recommend taking it in college, because the structure and commitment mechanism of a college course will help you get yourself through the material.
One major caveat: In my opinion, courses that only cover pencil & paper "theory" exercises are much worse than courses that have a combination of pencil & paper work and problem sets that require the use of software tools like Matlab, Octave, or Python/NumPy. In the real world, you're always going to use software tools for the actual number crunching, so it's extremely valuable to get familiar with actually using them. It can also help you on problem sets in your other courses - using Matlab or Octave on your laptop is much faster and more pleasant than keying numbers into the matrix interface on a TI-84!
The book itself is still for sale, and the website has course slides and auto-grading software for some of the exercises: https://codingthematrix.com/
The interface is surprisingly good, and it's what I recommend to new gdb users if they aren't using an IDE. I still prefer the Emacs integration[1], but I don't recommend that to people who aren't already experienced Emacs users.
[1] https://sourceware.org/gdb/current/onlinedocs/gdb/Emacs.html...
The point is to only build things that are necessary for your product, not to avoid building anything.
When doing the math: A common mistake is to calculate the cost of "build" as SUM(compensation of developer team on the project) over the time it would take to build the thing. You should actually use SUM(business value created by developers working on the next-highest impact items on your roadmap). In a well-run business the latter should be much higher than the former.
For every piece of infrastructure or developer tooling you need, you have to make a buy vs. build decision based on cost/benefit analysis. Your cost to "buy" needs to include the upfront cost of developer time to configure the software for your needs, and the ongoing support cost to make sure it continues to work. When you include this, even open source software isn't "free", although it may be cheap. Your cost to "build" includes the upfront engineering time to design & code, ongoing support time to keep it working, and opportunity costs incurred because until the system is actually ready, no one can use it, and they have to either meet their needs in some other way or simply block until the tool is complete.
Very large engineering organizations like Facebook, Netflix, etc. can amortize the cost of tool and infrastructure development over thousands of developers and an enormous infrastructure budget. If a tool would make most of Facebook's developer's 3% more efficient, than it's worth staffing a team to build that tool. If better caching infrastructure could reduce Netflix's network usage by 3%, then it's worth staffing a team to build that infrastructure.
If you're a small- or medium-sized business, then that math doesn't pencil out. A 3% (or even 10%) developer efficiency improvement doesn't even pay for the opportunity cost of one developer. A 10% decrease in a single dimension of your AWS bill probably doesn't pay for the developer time either.
If you're at a mega-corp with a huge engineering staff: Yes, absolutely invest in tools that make your engineers more productive, especially if you've identified truly unique needs that can't be met by off-the-shelf software.
If you're at a smaller business: Focus your developer energy on your user-facing problems, and almost always prefer to "buy" instead of "build" (where "buy" includes using open source software).
That's the core issue. CHSRA never had a credible funded plan for building either crossing, and instead chose to tackle the easy part in the Central Valley first. Unfortunately, HSR in the Central Valley is effectively useless without a mountain crossing at at least one end.
TL;DR - Don't buy a car or house using the same negotiating strategy you would use to negotiate a professional services contract.
Emacs regexps are unfortunately their own weird beast - they handle parentheses differently than other regexp engines, because Emacs assumes that you'll be running regexps on Lisp code a lot and want to easily match parentheses. The best documentation on that syntax is (confusingly) in the Elisp reference manual: https://www.gnu.org/software/emacs/manual/html_node/elisp/Sy....