buffet_overflow

Agreed. I've found the insistence my college professors had on writing everything yourself and not using libraries or modules for common tasks to be in the end counter productive. Namely for the reason you described. To reference Carl Sagan, I didn't have the stamina in the beginning to build the universe before I made my apple pie.

Additionally, code is more collaborative than that, and it shows in a lot of engineering departments when people aren't trained on how to look at the shelf for existing parts before building something new.

This is a nice approach. I generally leave a project specific email in the request headers with a similar short summary of my goals.

>unless they were cutting scary amounts of corners no sane person would want them to cut?

This doesn't stop nearly as many people/companies as much as I wish it would.

This is the first hardware Kickstarter I've backed, and I've been really impressed with the frequency and depth of their updates. Makes me very excited for the final product.

If it weren't for this comment, I would have missed this one. Thanks for the flag, and a +1 to this being worthwhile.

Agreed that it's difficult to responsibility of these companies on the individual. There's a background assumption that "if they exist in this form, they are allowed", otherwise, what are the US government (regulatory functions) doing?

Another reason it's difficult to impossible to collectively fight back is when you read articles about how Amazon strongarms companies into never undercutting the price on the Amazon storefront. It adds an insidious reason to "wow the manufacturer is so silly, it's cheaper on Amazon with free shipping than on their own website!" when in reality it's a dark pattern we don't control and a vast majority don't think about as they "get by".

>The core pursuit of computer science is how to best design and harness computers"

This is why I've been quite happy with the Information Science major. I joke that it's "watered down compsi", as it avoids higher level topics like OS design and anything beyond the introductory Data Structures. Instead, the major uses that time to introduce psychology, sociology, and user experience/interface design. As a professional, I've found that focus on "how we interact and best use technology" to be useful.

My favorite bumper sticker goes something like, "If loud pipes save lives, imagine how it'd be if you learned how to ride the thing"

80% of my problems are communication problems. Does X team know about Y team's initiatives and work? Does A team know about B team's weird use cases when they develop their platform?

The rest are resource management. It's difficult to hire the "best and brightest" and task them with mundane maintenance and general housekeeping, but those things still need to be done too. It's about striking that balance between exciting greenfield projects and making sure our older services don't rust away.

I'm genuinely grateful that Amazon has at least pulled those and other even smaller stores into an age of much easier online ordering and delivery.

Cost of living most likely. A retirement goes further in some countries.

What have you seen in that space so far?

An aspect that appeals to me is interchangeability. If you needed to replace an engine or other major components, even just to similar items in the manufacturers lineup, there's definitely a "golden era" of late 80s to early 2000s cars where that is feasible for the...more enthusiast home mechanic. While not impossible for modern cars, it is far far more difficult.

He's been wrong before. His statements should be taken as marketing, not gospel.

We've had to ban the application entirely from our work machines. At least when we went through review, even the "clean" versions packaged things that tripped our antivirus software, and at that point, we as an organization decided to stop trusting the author entirely.

There's quite a lot of forum posts where the author defends this practice, so we don't see this reversing any time soon.

I still know people that pre-emptively buy toilet paper "because hoarders might buy the rest of it" with absolutely no introspection.

I can't help but wonder if a large part of this is the advice of "pick your battles, don't engage with others you disagree with, you're just wasting your energy" and similar being applied far too broadly.

I genuinely wonder about the effects of later generations growing up in these conditions. It feels ripe for learned helplessness. "Well it's just always been bad" is a common, if ineffective response.

Agreed, I had a similar takeaway.

>...faded lineprinter paper show that the bulk of the work on OMU dates from March/April/May 1984... by mid 1984 I had a perfectly usable O/S

It's impressive that Hosgood made what he did when he did. It's equally impressive for an entirely different set of reasons that modern CS students can burn through that in a semester. Or you could look it up on WikiHow.

I think this would be an interesting experiment, and I'd happily follow it. However, a complication here is that some sites/services still track you/modify their offerings without the need for an account.

I wonder if you did this across multiple devices, you could start noticing differences based on what you used for what. A/B test them back.

>They can be poor for stepping back and thinking “is this really the best way to satisfy that person’s needs?”

This is something I stumbled onto recently. I've been hellbent on making sure I had no distractions and could hit that 5 hour flow state, only to find smaller chunks gave me more points to reflect on the state of the work and redirect it more effectively.

Thanks for capturing it into words.

If you get tired of painting, you could insert a layer change filament swap (M600 gcode, or manual option in Slic3r) to swap from black to white as you reach the notch cutout, and back to black once you clear it. You should then be able to see the white color from the front.

Wow, what was the trigger for that, if you don't mind me asking?