• 2 Posts
  • 319 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle



  • Most of the laptops I’ve had open lately have had about the top third be the motherboard and the bottom two-thirds be battery, with maybe some ports and speakers tucked down the side. So I’d expect that last of replacements to include the battery, too.

    I might check whether the hard drive survived - a decent M.2 is small, expensive and reusable - and maybe the RAM if it’s not soldered in.



  • I’d imagine that they’re unproductive because of the long hours that they spend in the office. It’s been a source of mystery to me (European) how our offices in America manage to put in 60 hour weeks every week, often with a crazy commute before and after, and yet never seem to make fuck all progress on anything. Better to concentrate on how to be as productive as possible for time that you are there, than to fetishise the total amount of time?


  • Having had one of the old Windows phones with a keyboard dumped on me at an old workplace, can confirm it’s completely possible for a phone to have a keyboard and be a complete piece of shit.

    A good phone with a good keyboard may have some use cases. If you do a lot of writing but not any more computing power or screen space than a phone has, plus you want to be doing that on the move, then yeah. For me, can shitpost on forums using my phone in my spare time, and dealing with on-call work issues - having multiple tabs of Jira and Slack open, for instance - just isn’t really practical on a small screen.

    If your job is very email-centric, then yeah, sure. Blackberry were very good for just having the stuff you need - email, vpn, ‘corporate’ office documents - in a form that worked.







  • Writing in ASM is not too bad provided that there’s no operating system getting in the way. If you’re on some old 8-bit microcomputer where you’re free to read directly from the input buffers and write directly to the screen framebuffer, or if you’re doing embedded where it’s all memory-mapped IO anyway, then great. Very easy, makes a lot of sense. For games, that era basically ended with DOS, and VGA-compatible cards that you could just write bits to and have them appear on screen.

    Now, you have to display things on the screen by telling the graphics driver to do it, and so a lot of your assembly is just going to be arranging all of your data according to your platform’s C calling convention and then making syscalls, plus other tedious-but-essential requirements like making sure the stack is aligned whenever you make a jump. You might as well write macros to do that since you’ll be doing it a lot, and if you’ve written macros to do it then you might as well be using C instead, since most of C’s keywords and syntax map very closely to the ASM that would be generated by macros.

    A shame - you do learn a lot by having to tell the computer exactly what you want it to do - but I couldn’t recommend it for any non-trivial task any more. Maybe a wee bit of assembly here-and-there when you’ve some very specific data alignment or timing-sensitive requirement.




  • My workplace is a strictly BitBucket shop, was interested in expanding my skillset a little, experiment with different workflows. Was using it as a fancy ‘todo’ list - you can raise tickets in various categories - to remind myself what I was wanting to do next in the game I was writing. It’s a bit easier to compare diffs and things in a browser when you’ve been working on several machines in different libraries than it is in the CLI.

    Short answer: bit of timesaving and nice-to-haves, but nothing that you can’t do with the command line and ssh. But it’s free, so there’s no downside.


  • Ah, nice. Had been experimenting with using my Raspberry Pi 3B as my home Git server for all my personal projects - easy sync between my laptop and desktop, and another backup for the the stuff that I’d been working on.

    Tried running Gitea on it to start with, but it’s a bit too heavy for a device like that. Forgejo runs perfectly, and has almost exactly the same, “very Github inspired” interface. Time to run some updates…



  • Most common example would be a bicycle, I think - your pedals tighten on “in the same direction the wheel turns” as you look at them. So your left pedal has left-hand thread, and goes on and comes off backwards.

    The effect of precession also means that you can tighten the pedals on finger tight and a good long ride will make them absolutely solid - need to bounce up and down on a spanner to loosen them.