Deleted Comment
People seek him out because of his skill, but then upon being told that it might be £600 for interior door to be made, or more, suddenly want him to fit a store bought one. His daily rate is low, but a lot of rich people still don't want to pay for a job to be done properly.
Quite sad to see people buying amazing historic houses and then filling them with ready made fittings, after tearing out the old hand made stuff.
I also find it quite interesting that you mentioned git specifically, because I’ve been going back and forth for the last few days with myself about whether I should spend the rest of Winter Break and next semester (I’m an undergrad with one semester left) learning git internals deeply. So, this felt somewhat validating of the perspective that I should learn about git more deeply so I can have enhanced practical knowledge, which could translate into more economic value for the company I’m working with after graduation.
Once a decision is made in this regard, I then have to figure out the best way to actually learn it. I’ve considered trying to follow the mailing list[0] and contribute code to the git project, thinking that would force me to learn it very deeply. But at the same time, I feel like trying to go that deep might have diminishing returns and might stress me out. I like the idea of being an open source contributor to such a huge project and gaining more experience that way, but I also worry about the potentially high time cost.
I imagine I could alternatively read the Pro Git Book[1], the git documentation[2], and/or some other specific git internals resource someone has curated, but I haven’t decided what would be best yet.
[0]: https://git.wiki.kernel.org/index.php/GitCommunity
For less of a time commitment, Git from the inside out [2] is a really nice explanation of the internals, from initializing a repo and the files that creates in the .git directory, all the way to pulling from and pushing to remotes.
[0]: https://wyag.thb.lt/
[1]: https://news.ycombinator.com/item?id=19386141
[2]: https://maryrosecook.com/blog/post/git-from-the-inside-out
All in all, very cool product, and congrats on making a living from it!
This is all the more reason to delegate responsibilities, rather than tasks (as argued in Little Tasks, Little Trust [0]), so programmers actually get the necessary experience with UX, design, interacting with customers, etc., and exposure to the consequences of what they build, in order to grow into full-fledged product engineers.
I fear though that such roles, and consequently such engineers, are few and far between.
> Explosives were used to deploy the parachute, so care had to be taken that there were no late detonations. [0]
Precisely what you guessed it to guessed it to be.
[0]:https://mobile.twitter.com/girlandkat/status/133551478006118...
For a product that is supposed to be simpler and save people time compared to the alternative, increasing time using the service might mean people like it and are getting more done so using it more... or it might just mean that it's getting harder to use. Then again, maybe they've graduated from doing simple things with it to complex things, and even though interactions take longer, they're still saving more time and effort overall compared to the alternative and are happy.
I guess the bottom line is I think you have to slice and dice the data a lot of ways and think about what it actually means for your product to be using that data effectively.
I doubt there are too many people in tech making this mistake, but without numbers there’s a good chance you fall prey to people’s inaccurate perceptions or explanations for their own behavior.
On the other hand, without those first-hand accounts, it’s all too easy to tell a mistaken story about your numbers. In particular, your users’ sentiment towards their time spent in your app is a guess, unless they tell you.
I think timescale is another crucial dimension to evaluating time-in-app, and whether it’s a positive indicator for your business.
For instance, driving up engagement has doubtless been good for Facebook’s financials in the short- to medium-term. Arguably though, that relentless focus has led to the present political climate where they’re fighting off regulation. Whether that’s an existential threat is yet to be seen (one can only hope), but it certainly casts the metric in a different light.
As you say, it comes down to the fact that there is no silver bullet metric; there’s no substitute for thinking about and dissecting the data you collect.
This is like being burned by a candle vs being burned by a nuclear fucking explosion.
Again, the amount of effort our system puts to punish and criminalize these people is not at all comparable to the protections they offer to the companies that do have that nuclear explosion level damage on everyone.
You're missing the entire point, and this thread is basically a great example of why we keep fucking up like this.