jidiculous
Joined 7 years ago
Karma
103
Submissions
52
Member since
Sep 4
Recent submissions
Comment · 5 years ago
It's good that your team is empowered to tailor its rituals to its needs. It seems that a lot of people forget that the Agile manifesto[1] is loose enough to allow for team-specific customization: "Individuals and interactions over processes and tools".
Comment · 5 years ago
I can't imagine (haven't tried it so I'm just speculating here) that Magit functions very comfortably on something like a deep clone of the Linux repo, but I think there would be very few monolithic projects most of us would encounter with that kind of lengthy history in our day-to-day work. Maybe some Googlers could weigh in on how their large repos are handled by Magit?
Comment · 5 years ago
> but the performance profiles & characteristics that we must know about in order to make a choice on which tool to use. And it shouldn't be that each user has to figure it out on their own, dig into PR's or whatever.
That's an interesting take – I like the idea of a catalog of standard tasks with implementations in several languages as well as their performance characteristics. I suppose Rosetta Code gets the ball rolling with this, but it's missing some performance metrics. It reminds me of Ben Hoyt's piece[1] on counting unique words in the KJV Bible in different languages.
Comment · 5 years ago
Yeah, as I understand it (I currently work in another department), anything sub-10k has much less red tape for fed government procurement in Canada.
Comment · 5 years ago
Somewhat related: part of the Government of Canada (ESDC) has started their own pilot for making micro-acquisition opportunities much easier to both set up on the government side, and bid for on the contractor side. https://twitter.com/MicroBuysGC
Comment · 5 years ago
I tend to use my commit messages for things like this.
Comment · 5 years ago
there's an effort to replicate Magit in VS Code: https://marketplace.visualstudio.com/items?itemName=kahole.m...
Comment · 5 years ago
Yeah, that default ruleset is quite sparse. It would be nice to see Go's Code Review Comments (https://github.com/golang/go/wiki/CodeReviewComments) added as a basic ruleset.
Comment · 5 years ago
Are you still maintaining the project? It looks like it's been a while since the last commit or release.
Comment · 5 years ago
Staticcheck for Go kind of does something similar in that it outputs Googleable error codes, but doesn't actually print a link to the pages. It's also included as part of golangci-lint.
Comment · 5 years ago
It is 100% a Google language. Step 0 of their contributor guidelines is to use a Google product (ie a Google account) for authorship of your commits[1]. It's insane to me that this is required for contribution to the language's development.
Comment · 5 years ago
There's a bit of a reporting bias when it comes to BTC's (or even crypto itself) environmental impact. We're only able to say "it uses as much electricity as X country" because there's a well-defined ledger of every BTC transaction.
The question is how much non-crypto "conventional" currencies cost the planet.
That being said, BTC probably isn't the "best" cryptocurrency. I'm not sure about the details because I don't know much about this space now, but other commenters have pointed out that it's more efficient for ledgers to record proof of stake rather than proof of work.
forcepush.tech