marcua.net
Hummus, people, and data. Co-Founder & CTO of B12. Previously Locu, MIT CSAIL. He/him.
https://marcua.net/
Queens is the future.
143 posts
2,682 followers
212 following
Regular Contributor
Active Commenter
comment in response to
post
Well well well, if it isn't my good friend, overthinking brain, poking around not-for-public-consumption writing. Happy Monday @skamille.themanagerswrath.com :D.
comment in response to
post
Not going into solutions mode, but just sharing that I’ve been struggling with this for a few years now, and offering empathy. Every post feels like more caveats than content.
comment in response to
post
It's great you're identifying how impactful senior engineers can be on culture! Rather than more/less sway, I suspect senior engineers impact culture more by advice and example whereas managers do it more by advice and process. Both are wonderful and important! :)
comment in response to
post
This was my first time making GitHub Actions that deploy and tag Docker images on a new git tag. Nice to see the tooling that simplifies this!
Also my first time using multi-stage Docker builds. The image to build the project takes ~2.7GB, but the final image containing the binaries is only ~150MB!
comment in response to
post
I’m intrigued about the possibilities…
comment in response to
post
Nice! Not an expert, but this feels like a comprehensive set of best practices, which is exactly what I was looking for. Thank you so much for taking the time to share it! :)
comment in response to
post
I'm also curious --- do CMSs then update the third-party registration restriction list? (Like whatever GitHub is using to create its marketing pages has to restrict people from registering those handles.)
comment in response to
post
That's smart security-wise. What I love about GitHub's approach is that they don't do that, which looks so much more elegant :).
comment in response to
post
That makes so much sense! Thank you! Is there a common list of these somewhere?
comment in response to
post
My brain immediately goes to putting the app server at a different domain (e.g., app.example.com) or prefixing it with a path that points to a different origin (e.g., example.com/app). The GitHub-style URLs are way more elegant, but I can't figure out how they cleanly implement them.
comment in response to
post
Winner! I hope it was great and that you took the lid off:)
comment in response to
post
Did you have a break?
comment in response to
post
That's pretty clear and the tradeoffs seem reasonable. Thank you!
comment in response to
post
TY for sharing! There's nothing to dislike in the announcement, and having alternative infra is strictly better for the network/protocol's longevity. I am curious, though: would bsky.app / AppView (website/mobile app, apologies for terminology) allow you to pick alternate infra beyond a PDS?
comment in response to
post
Congratz @hannes.muehleisen.org! So well-deserved!
comment in response to
post
Very cool! Thank you for sharing this. Personalized models and personal data stores seem nicely aligned!
comment in response to
post
Linear models, with hand-crafted weights
comment in response to
post
stopjava.com
comment in response to
post
I literally took a screenshot of that screen and pasted it into a work Slack :)
comment in response to
post
Nice example! Thank you for sharing!
comment in response to
post
Thank you for sharing this! I’m excited to read more!
comment in response to
post
And hopefully some tiny steps toward a better relationship with our data to come!
comment in response to
post
What if it was easy for a user to create a personal database and authorize an application to access it? The user could maintain control of the database, and the application would gain access to the data for as long as the user wished. The post also covers some challenges to making this a reality.
comment in response to
post
When Ted Codd imagined enterprise databases in the 1970s, storing company-controlled data in a company-controlled database was a reasonable choice. But for consumer applications, sharing your data with an application that then restricts, loses, leaks, or sells it doesn't make as much sense.
comment in response to
post
Oh, I forgot to mention: lower your standards! Waiting until a piece feels as good as you can get it is a recipe for an empty blog and a huge folder full of drafts
I try to hit publish while I am still unhappy with what I've written
comment in response to
post
Get thee to another island, stat!