There’s a thing I picked up from my dad and the fitters who worked in my grandfather’s workshop: own your tools. That way you’re not tied to your employer, you can take your tools and your skills to another job any time you please.

I was once on the position where the only laptop I had access to was owned by my employer. It made my teeth itch.

It’s just one more reason I am deeply suspicious of LLMs for coding. And all the other rented software out there, for that matter.

Grandad insisted that his fitters owned their tools, by the way. He’d help them buy the stuff they needed if they were starting out. He died nearly forty years ago and there are still a couple of folk working for the family firm that he hired, so we presume he must have been doing something right.

@pdcawley
Back in the 80s when we were a family run electrical contractor, we provided all our staff with tools and college training. The basic tool kit was theirs to keep, while we owned the bigger bits of kit and test equipment, to be booked out as needed.

Our aim, as a small company, was that our staff would eventually leave us for self-employment, or a bigger employer, taking not just their tools, but the experience that they gained.

Later in life I heard that in bankruptcy a court can take away a trades' person's belongings to pay a debt, but not their tools as it is their means of earning a living.
No sure if that is true or still applies.

@pdcawley sidebar: know how to *make* your own tools. That’s another skill that’s slowly disappearing.
@pdcawley Just struck me that people going all-in with LLMs for coding are essentially choosing to move into a company town. And companies that do it are choosing to become wholly owned neighborhoods of a larger company town.
@wordshaper is not thought of it on those terms, but yes, absolutely.

@pdcawley i dig it. My first laptop was a Toshiba 3100, that one with the red gas plasma display that sucked so much power that the thing was not really a "portable." A laptop that has to stay plugged in!

I didn't see why we spent all that damn money.

@pdcawley Your implied analogy doesn't hold water for me.

Did your employer somehow prevent you from having access to any other laptops on Earth?

Also, I've NEVER been required to provide my OWN laptop for any job I've had. Would you prefer that? Because I don't believe I would.

"Your own tools" is a flabby, vague concept here that's not transporting well in this analogy. A hammer is one thing, a computer quite another.

@wesdym @pdcawley For most work that involes a computer (including phone), owning your tools/using your own for work is an entirely untenable proposition for both parties. It breaks privacy/confidentiality in both directions, and exposes both parties to major risks from things the other party does that should not affect each other.
@dalias I wouldn't want my employers to provide me with a computer for private use, for that very reason. If it's not really mine, then I can never really know if they'd be snooping. It's not worth it to me.

@wesdym @pdcawley

Did your employer somehow prevent you from having access to any other laptops on Earth?sometimes people can't afford (or otherwise cannot replace) laptops?? that's a thing, you know.

@aud Yeah, and I can't afford MOST of the stuff at my various jobs, but that doesn't imply that I'm entitled to any of it, or that anyone should provide me with it because I'd like to have it.

Are you serious?

@wesdym do you struggle with reading comprehension or are you just being an asshole? Because I'm happy to help with the first.

@aud Well, you failed the test, but I expected you to. I do try to give everyone a chance. But only one.

You need to grow up.

@pdcawley the first "rule" of the Right to Repair movement is "If you can't fix it, you don't own it" ... Back when the Maker/Hacker/Punk scene was closer together the motto was "DIY or DIE."

Our grandparents generation isn't that far off from Apprenticeships & Union Shops where they passed down & shared their knowledge instead of paywalling it and competing for promotions.

https://www.ifixit.com/Manifesto

Self-Repair Manifesto

Let's take back our right to repair! Help us get this manifesto posted in every workshop, hacker space, and garage in the world!

iFixit

@pdcawley This is one of the core problems involved in Luddism -- one of the ways it's so relevant again to This Moment, and not in the tedious, reactionary "bwah people are Luddites" way.

The more landlords and tool renters we create… well, bleh.

I keep doing experimental work with local models. I think we'll see serious progress there. What I wonder is, how small an epsilon will there be, in X years, between them and frontier models? No idea.

@pdcawley

Interesting. I made it a non-negotiable point that my employer provide my computer. What I do with my personal equipment is my business, not theirs.

@pdcawley It's why I have thought of owning a sticker printer before I even any sticker sales (💧).

Of course, the thought of owning another printer has doused my enthusiasm. I am also trying to self-host as much as I can.

@pdcawley @aj Working in IT it always blew my mind the number of people whose work computer was the family's only computer.

They gave their work computers to their kids to play with FFS. Who could have done god knows what with any corp information! Deleted things accidentally etc!

@bastardsheep @aj @pdcawley I have memories of coding in Turbo Pascal and playing Sierra games on a somewhat boxy 286 laptop belonging to my mum’s employer.
@acb @bastardsheep @pdcawley We had a C64 and then an Amiga 500 at home, but my folks sometime bought home a very early black and white Win 3.1 laptop from work occasionally over long weekends.

The big difference back then was there was no internet. (I don't think those laptops even had Trumpet Winsock installed?)

@bastardsheep I once made my stepfather's 486 work laptop unbootable by messing with the config.sys. Was able to rectify the mistake by using my mother's similar (but not identical) work laptop to create a MS-DOS boot disk and revert the config.sys changes...

@pdcawley @aj

@rainynight65 @bastardsheep @pdcawley The big difference in the days of DOS and Windows 3.1 was that the internet wasn't really a thing back then. (At best, it was email, Usenet, gophers, and FTP over dial-up.)

An order of magnitude less scope for harm than an internet-enabled laptop today.
@bastardsheep @pdcawley @aj I certainly would not want to be using my personal computer for work. All the security cruft that needs to be loaded on for compliance etc, has no place in my private use.

While the initial justification has merit, it cannot be extrapolated across all industries.