jmaw

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?