HN user

mdergosits

134 karma
Posts5
Comments43
View on HN

I took the undergraduate version of this course while at Cornell. It was a wonderful course. I taught me a lot how computers work, and how to organize a large (for me at the time) software project.

One of the most painful parts of the the project was using Scala which had ridiculously long compile times which made iterating quite a pain.

My favorite memory was that for one project we had to submit a program written meant to stress test everyone's parser.

I have a couple strategies: - If im hungry I drink a glass of water first. Most of the time I drink something that impulse to eat goes away while satisfying my wandering mind. - I like to eat apples, they are sweet enough to be a good snack but not very high in calories. - I bike to work (4mi each way) which helps if I do eat more than I want.

The bring up isn't actually very painful at all. The devices we are running are armv7, so we can easily just cross compile with the standard go tooling. The syscall package and memory layout of go structs lets us do almost every without C and when need C, cgo is very easy to use.

Go's easy concurrency made developing this really easy, so I think that go would definitely be the choice regardless.

Wouldn't loop detection be equivalent to solving the halting problem? Obviously a naive approach would be disallow recursion/ mutual recursion, but there are valid use cases for those that may not result in infinite execution

There's a CSA I just signed up called Imperfect Produce. They deliver boxes of produce that doesn't meet the aesthetic requirements for grocery stores. Sounds like a more economical version of this.

Somewhat unrelated, but I enjoy the logical dependence chart. It's nice to see the ordering of the topics. Rather than trying to figure that out for oneself

With a conditional move the processor executes both sides of the branch, but only "commits" the side that actually should be taken. Mis-predicting a branch on a modern OOO superscalar processor can be much more expensive than executing both sides.

It would be interesting to see the breakdown on average salary vs experience. As someone just starting my career it would be interesting to see how it compares to having 5 or 10 years experience.

edit: the UK report has that breakdown, not sure why it was omitted from the US report.