One time we got around the security for a shared windows folder (Win98). Another time a couple of us printed fake midterms for ourselves on official headered paper. But the one that sticks out is this trojan program I got from my older brother called deepthroat. I put it on a couple of other people’s computers that I wanted to mess with, and proceeded to open their cd tray, pop up fake warnings/errors, and other random stuff that a friend and I thought was hilarious at the time. It all stopped when I popped up a message that said “Contacting [name]'s parents…” on this girls computer and she got the teacher’s attention about it. He knew what was up and scanned all the computers. He was mad but we didn’t really get in trouble. We also did the fake desktop screenshot stuff :D

Must have forgot to write it down

Sorry, it’s supposed to be a gif. https://media0.giphy.com/media/8MKZszt2zP7KR3LtTX/giphy.gif

I’m not. How bad was it?

My understanding of trunk based development is that it allows for short lived branches and keeps longer work behind feature flags as it is merged in pieces. The common CI approach with pull/merge requests having to pass tests still applies.

Jerboa is pretty good so far. I wish it had its own browser built in though, like RiF did.

You should check that your stuff isn’t undeleted by Reddit. Some other people have reported them doing that.

I returned my $4000 MacBook, I don’t like the keyboard layout and thought it had poor performance for the hardware. I would go for a Linux laptop but other than that I prefer Chromebooks and have been using them for 10ish years.

I would get a higher end Chromebook. They run Linux, have a built in android container, nice keyboards, touch screen, often have 360 hinges if that matters to you.

I’ve got the middle one in that pic and it’s almost as fast as my 24 core desktop. Like others said, get 16 gig of ram. Edit: i use VS code which is less beastly than Android studio, but there’s no need to run an emulator because it’s already built in, accelerated.

I’ve had that article saved for years, it’s still the best way to break down documentation imo.

Another key point for code documentation is that the closer it is to the code it’s describing, the more likely it is to be read and maintained. The book “A philosophy of software design” has a section on it.

I love making a good dev experience, it’s a positive feedback loop of productivity and satisfaction/relief.