HNHacker News
TopNewBestAskShowJobs

nickm12

1,290 karma · joined April 4, 2012

submissionscomments
nickm12··on California unemployment rises to 5.5%, worst in the U.S. as tech falters
hear hear! I've worked with exceptional people from all sorts of backgrounds, but pound for pound, Waterloo CS grads are significantly better on average than grads from any other CS program. They start off way ahead, but also maintain that edge throughout their careers.

Disclosure: I'm a US citizen with multiple CS degree from MIT and my son is studying CS at Waterloo now.

nickm12··on Do we understand how neural networks work?
I was, for a time, a neuroscience major and have had this same thought. I'm concerned that we're treating these systems as engineered systems when they are closer to evolved or biological systems. They at at least different in that we can study them much more precisely than biological systems because their entire state is visible and we can run them on arbitrary inputs and measure responses.
nickm12··on Goodbye, Six-Figure Tech Jobs. Young Coders Seek Work at Fast-Food Joints
The article compared to biology and art history. It's my impression that art history doesn't lead to good job prospects, but is it actually true? A good article would provide support for that choice rather than rely on stereotypes in the reader's head. Or better yet, compare to the median using some data set
nickm12··on The Article in the Most Languages
...and I would have gotten away with it if it weren't for you meddling kids!

I find it interesting that the whole scheme might not have been noticed had he been more modest and not tried to translate the pages into rare languages. We don't know the motive, but if it was self-promotion, these additional languages were presumably of negligible value yet risked the scheme.

nickm12··on How we replaced Elasticsearch and MongoDB with Rust and RocksDB
> it shouldn't be a problem for you establishing a space even without going to the office.

No, this was nothing to do with company culture. This was just my own mental response to just always being at home. Admittedly, the pandemic accentuated this because we weren't going anywhere even on weekends and evenings. But even as things opened up and we resumed our normal socialization, I returned to the office long before most people because I needed the mental and physical distance.

I know I'm atypical. In those early days,I estimated fewer than 5% of people in my office were voluntarily returning and even today when we're at RTO 3 days a week, most people do exactly that and no more.

nickm12··on Goodbye, Six-Figure Tech Jobs. Young Coders Seek Work at Fast-Food Joints
I find these types of articles from the Times very frustrating. Most of this article is filled with sad anecdotes, but no indication of how those people were chosen. Were they the biggest sob stories found that fit the narrative? Even the data in article is presented in a useless way. CS grads unemployment rates are compared to biology and art history grads (why those in particular?)

I don't doubt that it is much harder to get big salary entry-level work in programming these days. My guess is this is due to a combination of high interest rates / lower investments, flattening business curves, and AI, but the article doesn't try to make a causal case. It just puts forth a bunch of anecdotes sprinkled with a few facts and leaves the reader to infer the causes.

nickm12··on How we replaced Elasticsearch and MongoDB with Rust and RocksDB
> This idea that 'work life balance' should mean that the two should be compartmentalised to specific blocks of time seems counterproductive to me.

Different people are different and can have different preferences.

For me, having different physical spaces helps me focus on work at work and my family at home. When they are the same physical space, both suffer. I'm not saying everyone should feel this way.

nickm12··on How we replaced Elasticsearch and MongoDB with Rust and RocksDB
You can't reduce the in-office or remote experience purely to commuting. It's just one aspect about how and where you work and work life balance in general.

But since you asked, yes, I actually enjoy commuting when it is less than 30 minutes each way and especially when it involves physical activities. My best commutes have been walking and biking commutes of around 20-25 minutes each way. They give me exercise, a chance to clear my head, and provide "space" between work and home.

During 2020, I worked from home the entire time and eventually I found it just mentally wasn't good for me to work and live in the same space. I couldn't go into the office, so I started taking hour long walks at the end of every day to reset. It helped a lot.

That said, I've also done commutes of up to an hour each way by crowed train and highway driving and those are...not good.

nickm12··on NASA satellite that scientists and farmers rely on may be destroyed on purpose
I don't see what argument you're trying to make. This satellite is producing data that is a common good (not unlike the Bureau of Labor Statistics data). There are lots of use cases for such data. Just because one use case doesn't cover the whole cost to collect the data doesn't mean it's irrelevant to point out the loss.
nickm12··on Writing a good design document
To add a little more color, each section also has a branch of possibilities. Given a problem, there are many possible functional specs that could solve it. Given a functional spec, there are many possible implementations. The act of choosing from among these possibilities is designing and the design doc should lay out the choices made (and sometimes the choices not made) and why.
nickm12··on I know when you're vibe coding
The parent comment was talking about the "abstraction offered by compiled languages over assembly". I quote an alternate form of "compiled" from that sentence.
nickm12··on Writing a good design document
I generally read "optimal" to mean "optimal according to some objective function". In the case of a technical design, the objective is not something you can readily formalize, because there are so many considerations.

For example, suppose you are designing a network service to meet some use case. Yes, it needs to meet the use case, but there are other things you care about like simplicity of the code, latency, cost to operate the service, and others.

For any design you propose, there might exist an alternate design that is strictly better by some criteria-maybe it works exactly the same but has much better latency characteristics. If an oracle gave you this design, you might agree it was more optimal and choose to implement it, but I don't think it means you failed if you come up with a (sub-optimal) design that solves the problem within the constraint.

nickm12··on Writing a good design document
Yes, agree with all of that. I don't think every design doc needs every possible section, but if readers would benefit from the background or the an enumeration of stakeholders, that belongs up front, before the design.
nickm12··on Writing a good design document
The structure I prefer for a technical design document is like a three-layer onion.The first layer is the problem statement, goals, non-goals, and requirements, both functional and non-functional. The next layer is the functional specification, which describes precisely how the system will work from an external perspective. The third and final layer is the technical specification, which describes the internals.

Each section should follow from the previous. The design doc should justify to the reader (and author) that the problem is understood, the requirements are necessary and sufficient, the functional spec meets the requirements, and the technical spec implements the functionality and non-functional requirements.

As a corollary, if one section has a fatal flaw, there is no need to read on. If the problem is misunderstood, then the functional spec is likely wrong. If the functional spec doesn't meet the requirements, then the implementation is moot.

The issue I see very frequently is technical design documents that provide only the final section—a simple description of the system that will be built. As a design reviewer, there is limited feedback I can provide on such a design. Sure, it's a system, but will it solve the problem? Does the team even agree on the problem to be solved?

nickm12··on Writing a good design document
> The goal of a design document is to convince the reader the design is optimal given the situation.

This is a nitpick, but I don't think the goal of a design is to be optimal so much as sufficient.

Software systems design, like any design, is about coping with constraints and tradeoffs. The design doc should clearly lay out these out and present an approach that meets the requirements and constraints with acceptable tradeoffs. Where multiple reasonable alternatives exist, they should be make explicit along with a justification for why one option was chosen over the others.

Will it be perfect? Probably not, unless it is an easy problem or you over-designed. And even if it's a good design, it can hit unforeseen issues during implementation. The goal of design is not to eliminate all possibility of such issues but to mitigate risks and communicate to the stakeholders what we're building and why we're building it that way.

nickm12··on Hyrum's Law
I don't think that's quite right. CPython dicts only started preserving insertion order in 3.6. There were concerns that other Python implementations might not be able to do this or it would be a performance bottleneck, but by Python 3.7 these were satisfied enough to make it part of the spec.
nickm12··on I know when you're vibe coding
This is a false analogy. LLMs do not "compile" natural language to high level code in the same way that a compiler or interpreter implements a high-level programming language in terms of machine instructions (or, for that matter, how a CPU implements machine instructions in hardware).

Programming and machine languages aim for a precise and unambiguous semantics, such that it's meaningful to talk about things like whether the semantics are actually precise or whether the compiler has a bug in failing to implement the spec.

Natural language is not just a higher level of abstraction on our existing stack. If a new model comes out, or you even run an existing model with a new seed, you can get different code out that behaves differently. This is not how compilers work.

nickm12··on Python can run Mojo now
Being a Python superset and being fast are fundamentally in tension. It would be possible, maybe, to have a Python superset where you get the highest performance as long as you avoided the dynamic features of Python. However, I suspect it would make the user base grumpy to have a hidden performance cliff that suddenly showed up when you used dynamic features (or depended on code that did the same).
nickm12··on Infinite Mac OS X
Thank you! The blog post really should hyperlink or define "Infinite Mac" so it stands on its own.
nickm12··on Possibly a Serious Possibility
Anyone else find the standard "probability yardstick" very misleading on the "unlikely" side? I know the whole point of the article is that English speakers can interpret these phrases differently, but calling a 1-in-3 chance "unlikely" seems off. I would shift that whole side down—30% as "a possibility", 10% as "unlikely", 5% as "highly unlikely".
nickm12··on CONL: "Markdown" for your config files
> it’s really hard to comment out a line in a JSON file, because you end up with an extra trailing , on the previous line

Every other language has figured this one out: just support trailing commas. JSON5 supports comments and trailing commas.

https://devblogs.microsoft.com/oldnewthing/20240209-00/?p=10... https://json5.org/

> The first version of CONL used # as a comment token, but I quickly ran into issues. URLs contain #, so my next version...

Every other language has figured this one out as well. Wrap strings in quotation marks.

> That led to a data-model where each value is one of scalar|list|map (Compared to JSON’s null|bool|number|string|object|array, this felt good).

I'm not sure what a "scalar" is in CONL (is it always a string?) but a config file format having fewer types than JSON does not feel good to me. Even JSON's hand-wavy "number" type is problematic (whether "1" is an integer or float or some some other type is implementation-defined). TOML got it right to distinguish integers from floats. TOML got this right.

nickm12··on CONL: "Markdown" for your config files
As best as I can tell, "An INI critique of TOML" is a subtle parody, not something to take inspiration from.
nickm12··on Why Companies Don't Fix Bugs
I don't see much mention in this discussion of how agile development impacts both the rate of bug creation and bug fixes. I only have my personal experience, but I suspect agile both encourages buggier software and longer-lived bugs than other methods.

The problem I see with it is the time-boxed sprints.Developers are rewarded for completing "stories" on time, not for the quality of that work. If a bug is found, they are rewarded for fixing it on time in another story (but only if it is high enough priority to warrant making it on the sprint board).

My experience is that getting it right the first time takes meaningfully longer than getting it nearly right, and agile rewards getting it nearly right. This is fine in the short term, but eventually the system grows a lot of subtle bugs, which add up to some big bugs that are expensive to fix. These take all the bug fixing time and the subtle bugs languish for attention.

nickm12··on 23andMe files for bankruptcy to sell itself
The industry chose the default of "data that is stored in durable storage is probably important". Sorry, I just don't see how that is bad for users when compared to the alternative default of "data that is stored in durable storage should be irretrievably deleted immediately".
nickm12··on Xee: A Modern XPath and XSLT Engine in Rust
This is fantastic to see! I've used XML off and on since it was the red hot tech of the early 2000s. I wouldn't choose it today for a green field project, but it's still around in so many places, so we definitely need a high-performance, high-quality library written in Rust for this.

This could become a great foundation for a typed, (mostly) etree-compatible, python library built on top of this. I've used lxml for years and it's still my goto, but there are lots of places where it could be modernized.

nickm12··on Three Tribes of Programming (2017)
I like this taxonomy, though it is reductive to try to cram programmers into disjoint "tribes". Individual approaches to programming generally combine from all three, though in different proportion to different individuals.

Personally, I am driven most strongly by the "maker" approach, in that I write programs to be used. I also care deeply about correctness, simplicity, and performance in that order. I hate buggy, unmaintainable programs and the best way I know to make useful programs is to build them out of small, simple, correct components.

Performance is generally a more distant concern, but it really depends where you are in the stack. As you go down, performance becomes essential to usefulness, but the need for correctness doesn't disappear.

nickm12··on 23andMe files for bankruptcy to sell itself
Says someone who has never experienced a data loss bug.
nickm12··on Performance of the Python 3.14 tail-call interpreter
Thank you for your efforts in improving Python and especially thank you for helping to set the record straight in such a clear and visible manner.

Some of the sibling comments are saying there's "no need to apologize". One way this might be read is "no need to hold yourself to a higher standard". If this is the sentiment, then I disagree—we live in an age where accountability and intellectual integrity are undervalued. Being able to say that you and your team should have investigated a too-good-to-be-true result further before reporting it is setting a higher standard for yourselves.

But another way to read this is "no need to feel bad" and on this I agree. We all often fail to sufficiently challenge our own work, especially when it looks like something we worked hard on had a big impact.

nickm12··on Clean Code vs. A Philosophy Of Software Design
buried at the end: there's a planned second edition of Clean Code! Given Bob's intransigence in this conversation, I wonder what he'll change.
nickm12··on Clean Code vs. A Philosophy Of Software Design
This was a fun read. I read APoSD for the first time a couple of months ago and found myself nodding enthusiastically as I read. I have a few quibbles, of course, but overall it matches my experience in how to write software that is correct, maintainable, extensible, and understandable.

I've never read CC, but I've read some of the take downs[1]. I was worried that the take downs were attacking a strawman, but no, Uncle Bob believes this stuff, including that comments are evil and you just need to read all the code and keep it in your head.

Even if that were true, the code I write is better for having written the comments, especially interface comments, because the writing helps my thinking. Moreover, it helps my code reviewers—without written interfaces. If all you have is the code and not a description of what the code is supposed to do, how can you know if it is correct? I think most code reviewers are verifying the code against what they infer the interface to be. It helps us both to just be explicit.

[1]: https://qntm.org/clean

← PreviousPage 3 of 17Next →