883 karma · joined August 20, 2017
Signal: @jasondclinton.11
[ my public key: https://keybase.io/jasondclinton; my proof: https://keybase.io/jasondclinton/sigs/DL7kLNV4-17_G3NlqgNDOzGigaqZ72Z8MDwwBybZT9k ]
That's a good question. Right now the market is reacting to on-the-ground realities. The follow-on question you are asking gets to: what will be the aftershocks?
The thing that I'm concerned about is the amount of risky business loans[1] that have been handed out in the past decade because rates were so low and mutual funds were looking for high returns. If a lot of businesses go bankrupt and that, in turn, puts the banking system at risk, then things would be ... bad.
[1] including businesses taking "no covenant" loans to—in some cases—pay their earlier investors dividends!
> Google had to overlay the repo[1] tool to scale past git
It was created to allow for a forest of git repos to all coexist in a world in which git submodules wasn't suitable yet OR the repos spanned security domains. However, almost all of the shortcomings of submodules have been addressed and so—at least—the team that I lead now is considering migration to it from Repo.
> cross-repo commits are not atomic
Yes, that is a feature. But I think you meant that there's no cross-repo coordinate in the timeline to sync to. However, there is. That's exactly what a Repo tool manifest snapshot is. Our CI system ensured that change that had deps across repos were committed and a Repo manifest snapshot only was taken with all inter-commit deps satisfied.
> Good luck bisecting a breaking change across millions of lines of code and build files
The team that I led implemented this. We simply snapshotted the forest at every T time intervals. For bisection, we walked the snapshots. Once a specific manifest snapshot was identified as the culprit, we further bisected within repos for a specific change.
> Pulling source took 1/50th the time a repo sync took.
Yes, that's what the partial clones (the article you replied to) and sparse checkouts solves. Once these two things are widely available, I don't see any benefits to P4 remaining.
We're getting ahead of additional Coronavirus impacts now, though, by establishing team chat channel and expectations for virtual presence and having discussions about how to maintain software engineering productivity on a remote laptop. Next thing on my list is to establish team culture of it being okay to quickly jump on a VC for high bandwidth information exchange and leaning-over-the-shoulder type stuff.
I see a lot more written communication in the future, too.
* Fractional scaling of monitor outputs
* Multi-touch gestures for e.g. switching desktops
* Security sand-boxing of apps
* Tear-free video
As the original link shows, though, the architecture has much better abstractions for software engineers to work with so developer quality-of-life is improved, too.Missing a word there. Now I'm in suspense.
> An Obligatory Public Service Announcement
which is an argument that:
> Linked lists are as niche and vague of a data structure as a trie.
The author then goes on to state that many people have contacted him to argue that linked lists are not niche and he puts each of those arguments under a heading:
> Mumble mumble kernel embedded something something intrusive.
is one such heading. Inside of it, he continues the argument that linked lists for embedded no-heap scenarios are niche and—to continue his argument—we therefore shouldn't be teaching undergrads linked lists just like we don't teach them tries.
I'm a big advocate for meditation but the study is skewed by survivor bias. Almost half of participants dropped off responding after 6 months.
However, the real reason that the ad money (and engineering effort) is going to apps is that app platforms do not protect privacy at the same level that the open web does. There's so much more tracking available on mobile platforms than there is on the open web.
After spending weeks fighting with Java's GC tuning for a similar production service tail latency problem, I wouldn't want to be caught having to do that again.