jmaw
jmaw on Hacker News
Yes, the data comes from the US Social Security Administration from 1936–2025
Source: The expandable "How we measured it" section at the bottom of the page
> This is consistent with the observation that girl's names are more dynamic.
Interesting, I wonder what causes this? In the US, is more common to name the first son after the father. Given this data comes from US social security information, that definitely has an impact.
I see the same thing. It looks like the height of the "My accidental pnmp forkbomb" screenshot is causing it to jump to the second page
An even bigger printing issue that exists on some sites is the use of scrollable elements. I haven't done extensive testing, but I tested on one site that uses `height:100vh;` around the main content of the page, with sub-sections using their own scroll settings. Printing the page only captured roughly what was visible in the browser window, but did NOT capture any of the internal scrollable sections. I imagine this would be more of a problem for web apps, as opposed to blog/article type content. But I imagine many blogs fall into this trap too.
CSS-Tricks was sold to Digital Ocean a while back. Now it's been purchased by an individual again. Someone who used to work on it back in the day
Not a web noob, but I'm wondering the exact same thing!
I definitely shift the average some!
I laughed out loud at the weekday example! How is that the best example they could come up with, haha
I agree 100%. I did enjoy writing code, but at the end of the day, it's the building/designing/problem solving that I enjoy. Whether it's related to software, woodworking, small engines, etc.
I'm not super familiar with heavy equipment like dozers and such, but some of them may also have a single motor to pressurize hydraulic fluid and valves to articulate the various pistons. So may be able to make the argument there too
> I stand by what I said
> thrownaway561
Interesting.
Yes, but it may be hard to justify the "experience of coding" from a commercial standpoint.
Casey Muratori had a take on a podcast that I liked comparing writing code vs. using an LLM to generate code to playing guitar by hand vs. playing digital music. Although it's arguably more efficient to play an mp3, people still enjoy the art of playing the guitar.
It definitely varies person-by-person. People who enjoyed l33tcoding, the act of programming, and the building process feel one way vs. the people who are in it for the end product, or enjoy the design process feel another. In a way, it's almost like those who enjoy the journey vs. the result (although the design process is also a journey).
Personally I enjoyed the act of programming/building. I'm struggling to put this into words, but software engineers have often been interested in solving technical problems, rather than business problems. At least I've felt this personally. I'm working on shifting that enjoyment toward the requirements gathering/design process. At the end of the day, it's still problem solving (which is the root of what I enjoy). But now it's more focused on solving business problems vs. technical problems. Which at the end of the day, is what is valuable to the business.
From the business perspective, this is great, because the end goal of software for the business is "business value". But it is a tough shift for some people to make (me included).
Edited to add:
Writing code vs. designing software are both creative. Writing code has a much more concrete/objective feedback loop though.
I also particularly hate the feeling of AI being shoved down everyone's throat.
And I don't enjoy digging through the mess that AI creates, whenever I have a particular bug that it can't quite get right.
I think this is a great one that a lot of people overlook. Also, doesn't cost $40+ like a lot of people are saying in different comments. Plus, it actually does some good in the world.
I've heard a lot of negativity around this book, and haven't read it yet. Did you feel like it was positive in the sense of genuine niceness, or negative in the sense of trying to be manipulative, etc.?
Are you going to call the HOA on the government to enforce them to maintain their fence?
I was stunned when I noticed the publication date. 2003.
I've never played with these DVD menus, but I do remember the days when people took advantage of YouTube annotations and interactive elements to make choose your own adventure style videos!
If my counting is correct (the results wrap across multiple pages), 13 companies applied for the .agent TLD.
There are few things nicer than seeing a PR with a lot of red!
I think you're probably right. However I attribute the lack of upfront design in software is due to the relative ease of changing it after the fact.
I would argue that the technical limitations should be considered during the creation of the design doc. In my experience, writing design docs can help me simplify the implementation because I've through through a lot of the headaches ahead of time.
But I will say I've seen many projects get ended by customer request or reorg. I think it's a cost-benefit analysis where you should consider the size of the project (and how long it will take to implement) vs. how long it will take to write the design doc. If it's a 2 day task, that is easy to change after the fact, then no need to write a design doc. But if it's a 2 month project that will have public endpoints that other teams or products will use, it likely is worth a 2-3 day design doc.
I think the design doc still has some value after it has been created. For me it almost acts like a checklist of things to be completed, and it's nice to have it in one place in bite-sized bits. My design docs will also have links to external resources and it's nice to have them in one place so I don't have to track them down later.
But I 100% agree that the majority of the value is gained in the writing of the design doc, and the decisions/tradeoffs that have to be thought through during that process. Which is why I strongly push back against suggestions of using AI to write design docs. Since delegating the writing to AI causes over half the value of the design doc to be lost.
Simply send your cable through the center of the earth and boom, latency reduced by ~1/2. Remember me when you make billions of $ from my idea.
My processing power is also weak :(
At the very least, should be a 429
I heard they can't figure out how to fix it with ChatGPT down.