[0]: <https://en.wikipedia.org/wiki/Magnus_Manske> [1]: <https://bitbucket.org/magnusmanske/wikishootme>
3,175 karma · joined October 22, 2012
[0]: <https://en.wikipedia.org/wiki/Magnus_Manske> [1]: <https://bitbucket.org/magnusmanske/wikishootme>
Thank you for posting this, and, of course, for the original concept :)
What's the common understanding of the term?
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.
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!
If I've got your model wrong, I'd like to hear more about it.
You need to make time for it, and you need to train people to do it.
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.
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.
I do find GitLab interesting; however, I am not totally sold on the "open core" business model :\
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 :)