HNHacker News
TopNewBestAskShowJobs

thcipriani

3,175 karma · joined October 22, 2012

Died tragically attempting to rescue his family from the wreckage of a destroyed, sinking battleship.
submissionscomments
thcipriani··on Find Wikipedia photos needed near you
To be clear, I (OP) did not do this—I just found this. This is a Magnus Manske[0] joint[1].

[0]: <https://en.wikipedia.org/wiki/Magnus_Manske> [1]: <https://bitbucket.org/magnusmanske/wikishootme>

thcipriani··on SomaFM
I still listen to SomaFM on the Logitech squeezeboxes littered around my house. My streaming music experience is stalled out in 2005, but I'm still blown away by how awesome it is. I'm grateful for SomaFM.
thcipriani··on Wikipedia.org Returns a 503 Error
> Investigating - We are aware that many users are having trouble accessing Wikipedia and other Wikimedia sites, and we are investigating. May 23, 21:30 UTC

via https://www.wikimediastatus.net/

thcipriani··on Gitlab – Static passwords set during OmniAuth-based registration (CVE-2022-1162)
To save folks some digging on what exactly this means—it's exactly what it sounds like: https://gitlab.com/gitlab-org/gitlab/-/commit/e2fb87ec5d4e23...
thcipriani··on On the Term “Blameless Postmortem”
The Paul Reed post is excellent. The term "blame-aware" is a useful frame for discussion: it reminds people that the goal is not to blame AND it's human nature to place blame.

Thank you for posting this, and, of course, for the original concept :)

thcipriani··on Why Millennial Managers Are Burnt Out
I've always understood "middle manager" to mean: manager of a manager, but subordinate to another manager. This article uses the term to mean: entry-level manager.

What's the common understanding of the term?

thcipriani··on Ask HN: What to Learn?
If the goal is to better your career, then you should think about two things: interviewing for new roles and advancing in your role.

Leetcode-type problems are only part of the interview process. System design interviews are pretty common -- developing a deep understanding of things like SQL, document stores, CAP theorem, parallel programming: all helpful.

To advance in your role, it's useful to quantify the value of your work. Data analysis is helpful here. Writing is an undervalued skill for advancing your career as well.

thcipriani··on What I've Learned About Writing as a New Engineering Manager
tl;dr: Make sure you have something to say before you write. Try to not make a wall of text. Use few words, mostly small ones.
thcipriani··on The Deployment Fidelity Problem
> If you then add additional stages, you can have it spend 8 hours on each stage, deploying to prod every 8 hours, so a higher frequency, but any given build is still preprod for 24 hours, so frequency has tripled without a change in latency.

Got it, thanks for the clarification. I'd interpreted your argument as: each stage is a deployment, therefore deployment frequency goes up (which also, of course, would mean lead time goes down -- so I was confused).

I like that this scheme could maintain continuous integration by having the "B" staging include the patch under test in "C" -- clever solution!

thcipriani··on The Deployment Fidelity Problem
In your example is A->B->C->D a series of staged release environments in the pipeline? Something like a graduated rollout? If that's the case then I'd say that frequency depends on how you define deployment.

If I've got your model wrong, I'd like to hear more about it.

thcipriani··on The Deployment Fidelity Problem
There are a lot of metrics you could collect about deployment. Most reduce to deployment fidelity.
thcipriani··on Treat code review like work
I studied a few papers about improving code review in big orgs, and they all seem to say the same thing: it's work.

You need to make time for it, and you need to train people to do it.

thcipriani··on Git email flow vs. GitHub flow
I believe what this post is describing is two different integration patterns and not two different workflows: continuous integration[0] vs long-lived branches.

Martin Fowler has a good post on the subject: https://martinfowler.com/articles/branching-patterns.html#Co...

tl;dr: if you make big feature branches and take a lot of time to integrate them it's a painful process.

[0]: <https://www.thoughtworks.com/continuous-integration>

thcipriani··on Missing Movies (2018)
> Piracy isn’t an answer to the problem

If the problem is, "me wanting to watch The Flamingo Kid tonight" piracy absolutely does solve that problem.

Also, the reason for this problem is that there is not sufficient commercial incentive to make a legal solution to this problem. There are fixes for this, changes could be made to copyright law, for example, that would make this problem a commercially viable one to resolve; however, there are few incentives to make changes that would allow this problem to be resolved. Piracy is certainly the easiest answer to this problem, and the only answer at the moment.

thcipriani··on Of Git Commits, GitHub, and Gerrit
I honestly haven't done any investigation of GitLab. It's something that some folks on my team are evaluating for CI use (cf: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering... )

I do find GitLab interesting; however, I am not totally sold on the "open core" business model :\

thcipriani··on Voters say “yes” to city-run broadband in Colorado
it has indeed been quite successful: http://beta.speedtest.net/result/6777148187

it's like that all the time now. Never been down for longer than 15 minutes and I've never been on hold trying to get assistance. All that for $50/mo :)

← PreviousPage 3 of 3