obfk

git push origin gh-pages

There's nothing to say the two events are correlated. As far as we can tell, they could have been underperforming sales people who were let go. Hiring/firing is _not_ based off the single criteria of raising money. There are complex business decisions between events like this, regardless of the coin in the coffers.

As someone fairly new to Clojure I agree entirely. There's a freshness about the language that has brought a new sense of joy and curiosity back into the programming world. The language forces you to rethink, relearn, and reevaluate the way you fundamentally understand programming. I think for the better.

Agree with the notion that turning standup into a static status meeting is a poor use of time. If you're blocked you should speak up. If the team wants to know the state of your work, they should defer to project management tool. That said, "standup" is less to do with what you did or immediate blockers. It's about planning for the day. "Here's what's going to get done today, and here's the relevant information for my team." It's a tool for synchronizing, getting on the same page, setting you and your team up for success on a daily basis.

If you don't feel like that's the case, you're probably right in that going async would be a better use of your time. I suspect this is a process dysfunction that has less to do with standup and more to do with a misunderstanding of the value proposition associated with a properly executed standup.

Edit: not everything is an immediate "oh sh*t" type of blocker. If you're working in a collaborative organization, you most like have "low tier" blockers or knowledge that can and should be shared with the team. Face to face makes this easy.

Agree that support is hard, especially when dealing with a very technical product, with very technical users. As far as fixes/enhancements go: every company has to prioritize somewhere. That means not everything gets done. Limited time, limited resources.

We'll have the drones bring you what you need.

Buildkite is a dream. Their technology is spot on, and it's changed the way we develop/integrate/release.

+1 for Knapsack. It's cumulative savings for our CI/CD has been tremendous.

Two years later: not looking back. It's not that bad, just get a set of bluetooth headphones and stop complaining.

Quantum computation will prove much more about the limitations of these cryptocurrencies that we expect.

#shorsalgorithm

WHY would you even considering composing your own diffing structure for updating a components state when that's entirely against the paradigm React proposes. Pass props from the parents and let the tool do the heavy lifting. State is an abused and misunderstood interface in React.

Anyone looking for an additional read should check Chasing the Scream by Johann Hari.

The Thorium Dream (Documentary): https://www.youtube.com/watch?v=GQ9Ll5EX1jc

One of the most enjoyable and mutually effective interviews I had included a one-hour pairing session which was language agnostic that required me to describe how I'd implement a basic data structure. The interviewer drove and implemented. This was then followed by a day long session of pairing on real problems with a number of different interviewers. Lunch was spent with some of the other team members, where we discussed basic things like culture, day-to-day affairs, and each of our histories.

This was a great approach to me, because it didn't particularly focus on anything outside of the present. We worked on solving real problems, and contributing to the project. It's a great, low-stress, method of gauging if someone has the chops for what is typically the "day-to-day" life at the given shop.