HNHacker News
TopNewBestAskShowJobs

alexhutcheson

3,780 karma · joined February 17, 2013

Nothing I post reflects the views or policies of my employers, past or present.
submissionscomments
alexhutcheson··on Don’t Confuse a Bug’s Priority with Its Severity
The post doesn't answer the biggest question, which is "What would I do with this additional information"? In concrete terms, what actions would your team take for a P2S0 that would be different from what they would do for a P2S3?

If anyone has a workflow where "severity" is important for your decision-making, I'm curious to learn about it.

alexhutcheson··on Twitter Thread: Experience at Lambda School for UX
There are significant differences:

- 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.

alexhutcheson··on Twitter Thread: Experience at Lambda School for UX
> We can make it milder like forgiving interest or converting it to some sort of a capped ISA.

That exists: https://studentaid.gov/manage-loans/repayment/plans/income-d...

alexhutcheson··on Gilbert Strang Teaches Linear Algebra
Very loosely, you can think of "Linear Algebra" as "the type of math that computers are really good at". For this reason and others, it's really heavily used in many of the most interesting sub-fields of software development: ML, statistics, HPC, etc.

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!

alexhutcheson··on Gilbert Strang Teaches Linear Algebra
> Unfortunately Coding the Matrix is no longer available on Coursera.

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/

alexhutcheson··on Generics in Go with Ian Lance Taylor (2019)
You also end up writing patterns like Pimpl[1] into your codebase, which are really just contortions to get faster compilation speed at the expense of readability, maintainability, and (some) runtime speed.

[1] https://herbsutter.com/gotw/_100/

alexhutcheson··on GDB Frontend with C Pointer Visualization
I haven't tried cgdb. Based on the screenshots they look pretty similar.
alexhutcheson··on GDB Frontend with C Pointer Visualization
For those who aren't aware, gdb has a curses-based 'Text User Interface' (TUI), which can be launched using 'gdb -tui': https://sourceware.org/gdb/current/onlinedocs/gdb/TUI.html#T...

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...

alexhutcheson··on 62% of general counsels use Excel and email to manage contract data: survey
Google Sheets has this: https://support.google.com/docs/answer/190843
alexhutcheson··on Experience report on a large Python-to-Go translation
https://godoc.org/github.com/glenn-brown/golang-pkg-pcre/src...
alexhutcheson··on Tools you’d miss if you left a company
It sounds like for your case, the answer to "Do I have a technical problem that's legitimately unusual and faced by very few other businesses?" is "yes", so you probably have to build it.

The point is to only build things that are necessary for your product, not to avoid building anything.

alexhutcheson··on Tools you’d miss if you left a company
I chose it as an example of a company that is unusually resource-intensive (in compute, network usage, storage, etc.) for how many engineers they have, so it can make sense to spend engineering more engineering resources on infrastructure than other similarly-sized orgs.
alexhutcheson··on Tools you’d miss if you left a company
Do the math - maybe it works in your case. I'd say a key question to ask is "Do I have a technical problem that's legitimately unusual and faced by very few other businesses?" If the answer is "no", then you should identify how other businesses are solving the problem and come up with really convincing reasons why you could do it cheaper.

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.

alexhutcheson··on Tools you’d miss if you left a company
For 99% of engineering organizations, internal engineering tooling is not your source of competitive advantage. Your advantage in the market comes from understanding the needs of your target user better than anyone else, and building a product that meets those needs.

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).

alexhutcheson··on The limits of high-speed rail
There are two sets of huge mountains in the way: https://en.wikipedia.org/wiki/California_Coast_Ranges

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.

alexhutcheson··on Hard negotiations: why a softer approach yields better outcomes
Agreed - you should always look at all-in costs, including financing. Normally better to get financing somewhere else ahead of time if you have good credit.
alexhutcheson··on Hard negotiations: why a softer approach yields better outcomes
If you negotiate an all-in price that's a $1000 lower than a typical customer, that's straightforwardly $1000 they don't get. The fact that your price was lower doesn't cause their other sources of revenue on the sale to go up.
alexhutcheson··on Hard negotiations: why a softer approach yields better outcomes
That changes the negotiation strategy for the dealer, but doesn't really change it for you. Even with a "nice" dealer who's planning on making money later in the car's lifecycle, your incentive is to get the lowest price possible, and there are no negative consequences from negotiating a price that is "too low".
alexhutcheson··on Hard negotiations: why a softer approach yields better outcomes
They're unhappy that they made less selling the car than they expected to.
alexhutcheson··on Hard negotiations: why a softer approach yields better outcomes
The appropriate strategy is context-dependent. Your strategy is appropriate for most cases, but there are some situations where your interaction is a one-off, and you don't expect to have to interact with your counterparty at all after the transaction. Buying a car is a typical example here: If you're able to negotiate a car dealership down to a price that's minimal profitable for them, the dealer will be unhappy, but there are no negative consequences for you. In those situations you should absolutely "try to win" - an extra 1-5% off is money in your pocket, and there are no negative consequences beyond some uncomfortable interactions with the dealership staff.

TL;DR - Don't buy a car or house using the same negotiating strategy you would use to negotiate a professional services contract.

alexhutcheson··on Show HN: Regex Cheatsheet
Agreed that rx is nice, but really only useful if you're writing elisp. 90%+ of people who need to interact with Emacs regexps aren't writing an elisp program - they're using Emacs interactively, or even using another program (busybox, GNU find, etc.) that uses Emacs regexps for historical reasons. For those people the differences in syntax between Emacs regexps and "normal" regex dialects are a pain.
alexhutcheson··on Show HN: Regex Cheatsheet
RE2 syntax[1] is a pretty good option to learn, because it's mostly a "lowest common denominator" - if it works in RE2, it should work in PCRE, Python, Javascript, etc. The reverse isn't true - there is a bunch of syntax that RE2 doesn't support by design, often to constrain performance bounds.

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....

[1] https://github.com/google/re2/wiki/Syntax

alexhutcheson··on The Rise and Fall of the OLAP Cube
Your users want their dashboards and reports to contain data that's as up-to-date as possible. No one is happy about waiting 24 hours or more for a batch update to run if there are decisions they need to make right now. The difference vs. OLTP is that it might be acceptable for events to take minutes or even hours to be reflected in the database, vs. ~seconds or less for a transaction where the user is interacting and waiting for a confirmation.
alexhutcheson··on Alpine makes Python Docker builds slower, and images larger
https://xkcd.com/1987/
alexhutcheson··on Proposals for Go 1.15
absl/strings is really great in the interim: https://abseil.io/docs/cpp/guides/strings
alexhutcheson··on Sarcastic comments boost creativity, a study finds (2015)
A recent paper found that people who endorsed cynical beliefs were more likely to be treated disrespectfully by others: https://marginalrevolution.com/marginalrevolution/2020/01/th...
alexhutcheson··on Bring your monorepo down to size with sparse-checkout
Have you tried the --shallow_submodules flag? I haven't used it, but it seems like to should do what you want.
alexhutcheson··on Bring your monorepo down to size with sparse-checkout
Using sparse-checkout by itself will still download the entire repository and its complete history into .git. If you additionally use the "partial clone" feature, then you can restrict what gets downloaded and stored in .git as well - it will download only the objects that are needed for your selected directories (along with their complete history). On big repositories with long history this might still be too much data, so you might also want to use the "shallow clone" feature (via the --depth flag) to restrict how much history you download.
alexhutcheson··on Bring your monorepo down to size with sparse-checkout
The author of the blog post is on the git team at Microsoft.
alexhutcheson··on Bring your monorepo down to size with sparse-checkout
Honestly most orgs (with "most" weighted by org, not by headcount) could handle entire-org repos without using any of these features. It's still worth simplifying the workflow and training experience for projects and orgs that grow beyond that, though.
← PreviousPage 10 of 29Next →