Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D

davidyarbrough

@ davidyarbrough @programming.dev

Posts
3
Comments
11
Joined
6 mo. ago

  • The slumbering pyramid

    Jump

  • It's an outdoors shop. I'll somewhat grudgingly admit that I like what Bass Pro has done with the place, it's an interesting visit if you're in town and like outdoorsy stuff. It's better than what it used to be, which is abandoned. I am disappointed that they didn't put a giant square conference table in the top for arch-villain quarterly meetings though; if I were planning world domination I don't think I could resist doing it in the zenith of a pyramid.

  • Suppose I wanted to build modern GrapheneOS for my old Pixel 3, but didn't know anything about mobile OS development...

    Jump

  • That is a good point, and PostmarketOS is definitely one of the options in the mix. I actually didn't know it had official support, will have to give that another spin. I have Postmarket on another device but I've never gotten it running on a Pixel 3.

  • Suppose I wanted to build modern GrapheneOS for my old Pixel 3, but didn't know anything about mobile OS development...

    Jump

  • I do have Lineage installed at the moment, it works well enough for some projects but GrapheneOS seems like a better long-term target for others. I think another part of it is that it seems hard and I want to see if I can do it.

  • Suppose I wanted to build modern GrapheneOS for my old Pixel 3, but didn't know anything about mobile OS development...

    Jump

  • I am considering that option, but part of the motivation is that I already have the device (two, actually) and I want to see what I can do with them. I don't want to just throw away perfectly good electronics if I can recycle / repurpose them. And since it's more of a hobby pursuit, really the only timeline is how long I can keep the hardware functional. I've already irreparably destroyed two phones, but I have also done a few successful screen / battery replacements, so I think I can get several more years of life out of these if I keep an eye on the batteries.

  • Suppose I wanted to build modern GrapheneOS for my old Pixel 3, but didn't know anything about mobile OS development...

    Jump

  • I think it makes sense that they don't advise it, they have limited resources and I don't blame them for not spending them on older devices. I think the only reason it would make sense to even try this is if you had two Pixel 3's just collecting dust and were hunting for a project for them.

  • GrapheneOS @lemmy.sdf.org
    davidyarbrough @programming.dev

    Suppose I wanted to build modern GrapheneOS for my old Pixel 3, but didn't know anything about mobile OS development...

  • A thought on the useful inefficiency of reading the docs

    Jump

  • A shockingly common approach lol. Like if you just buy every brand of turd polish you can find and apply them all, eventually you'll have something other than a turd. Except all the turd polishes are just the same turd blend in different solvents, so you keep coating your original turd in new layers of turd solution and are then shocked when you wind up with a different, larger turd.

  • A thought on the useful inefficiency of reading the docs

    Jump

  • I use the term in mild jest, relative to the new fashion of having LLMs blast out huge broken tracts of code for me to detangle. I guess "old-fashioned" can mean outdated but that's not what I mean here, just "the manner in which I wrote code before I had access to LLMs"

  • A thought on the useful inefficiency of reading the docs

    Jump

  • Any methodology becomes old-fashioned if it sticks around long enough to see the next new fashion. Though the new fashion has also made me seriously consider the goat herder route. Turns out it's a tough industry to move into.

  • A thought on the useful inefficiency of reading the docs

    Jump

  • I've had good luck with the docs so far, but I only just just got started with them so maybe I just haven't encountered any issues yet. Overall though, for the level of quality they've managed to put on a FOSS tool I'm happy to grant them a few rough patches in the doc.

  • A thought on the useful inefficiency of reading the docs

    Jump

  • I think we'll course correct at some point but I do feel bad for devs entering the field right now. They're getting pressured by the industry to become familiar with these tools because knowing the hot new thing is supposed to be how you get a job, but you skip the "let's figure out how to build something cool with the legos we have" part and move straight into the (IMO much more tedious) "this ball of spaghetti has a broken strand somewhere, lets poke around until we find it" part. And I think, now that I've missed it, I can appreciate how much struggling with the build step helps, with maintenance and future new builds.

  • Programming @programming.dev
    davidyarbrough @programming.dev

    A thought on the useful inefficiency of reading the docs