157 karma · joined December 1, 2011
“A language that doesn't affect the way you think about programming, is not worth knowing.” - Alan Perlis
That is the gist of one of the essays in The Mythical Man Month mentioned in the parent.
I also use Cloudflare as a DNS (free tier).
1. This is your time to talk about whatever is on your mind. If you want to talk about the footy over the weekend, that's fine. If you want to talk about work or issues at home or career progression, that's fine.
2. Sometimes there is not much to talk about - and that's fine too. If they do not have much to say on a particular day and I don't have much to say, it's a short meeting.
3. As said previously, try never to reschedule and never, never forget.
4. It's a really good time as a manager to practice listening. For that reason, I never have an agenda (i.e. things I want to say) at these meetings. Also, I try to contain the impulse to give advice unless they specifically ask for it.
5. I make it quite clear that as far as legally possible, I will maintain confidentiality. The only time that something may be relayed upward is if there is requirement for me to do so (e.g. an employee reporting harassment).
[edit] I reread the explanation and get it now. Only 1 prisoner (40) will actually get to open box 40. I was trying to think of this from the point of view of implementing it in code. I guess the cycle stops when a prisoner finds their own number or reaches 50 attempts.
Unlike more primitive version control systems, git repositories are not linear, they already support branching, and are thus best visualised as trees in their own right. Branches thus become trees of trees. To visualise this, it’s simplest to think of the state of your repository as a point in a high-dimensional ‘code-space’, in which branches are represented as n-dimensional membranes, mapping the spatial loci of successive commits onto the projected manifold of each cloned repository.
(Quoted from tartley.com)
John Smith
CEO and President
John Smith Global Design Enterprises
just does not cut it.I agree as long as we also see some of the benefits - required registration with a professional body - along with a requirement that certain projects cannot use uncertified practitioners (in other words, better pay for Software Engineers).
$ Make me a sandwich
What? Make it yourself
$ sudo !!
Okay