emuneee

The lack of a dashboard used to bother me. I wrote/prompted my own as a standalone Mac app over the past few months that works better for me, at least from a "what pull requests do I need to review right now" standpoint. It was hard to find this on GitHub.

https://github.com/evanhalley/beet

This times 1000. I loved their deeply technical reviews and articles. I got hooked early on their CPU and GPU deep dives and their mobile deep dives in the 2010s.

I've been reading them since before my teenage years and they got me interested in the insides of tech enough for me to pursue and gain my degree in Computer Engineering. It definitely changed when Anand and Brian left, but end of an era now that the site is shutting down.

I saw this article and fed ChatGPT a bunch of questions I've seen before in my coding interviews. It nailed most of the algorithms, however, it failed completely giving me test cases it would run to test the function it just regurgitated. ie...it gave me an input then mostly incorrect/invalid expected outputs.

Google Fiber has steadily been expanding it's footprint in my area of North Carolina (Raleigh-Durham-Chapel Hill). I've been a customer for a little over two years so it's good to see there's still momentum to expand into new areas.

I feel the same way. I wouldn't classify myself as a 10x developer, but I'm the most experienced and most senior developer at a smaller company and I have no peers, technically. It's good in some aspects because I get to work on secondary skills like mentoring/coaching and such, but it's a step back, technical experience-wise. I consume a lot of technical content like blogs, books, conference records, meetups, and podcasts so I can continue to get the learning I'd normally get from a peer. Side projects also help to a certain extent.

It is lonely because I have no one on my team to go to for different views on most technical or software decisions I make in my everyday work. I like being challenged because that's where a lot of my learning happens.

I'm currently contemplating moving to a larger company (or a more mature software org) where I can have some peers to lean on.

And I thought this building was where E(vil) Corp was staging paper records to rebuild their database this whole time. Who knew?!

As a Pixel user who has sent their device in for repair, how does the repair tech get past the device authentication and into the device? (I'm assuming the user had a device password/passcode set). If possible, this seems like a glaring security issue for Pixel users.