Jira was supposed to help us do the work, not become the work.
We have at least three people employed who's sole responsibility is to pester people about ticket status, apply bulk changes in Jira, define conventions, and ultimately make life harder for individual teams who wanna follow their own processes. As an EM, my higher-ups would rather have me ensuring ticket status is perfect to the T instead of pairing with and assisting my engineers.
I kid you not, we have directors of engineering who spend half their working day making bump/nudge comments on tickets.
Innovation can take place so long as the right people are getting their deserved royalties. In this case, anyone whose code was used in the training set should get a lifetime royalty.
We don't understand education at all. I'm seriously worried for the current cohort. Young children are missing the necessary face-to-face learning and social relationship-building that being in class provides, but it doesn't stop there. Some fresh college students are now paying full-price for 100% online classes, completely missing the college experience in the process, probably getting a subpar education -- if you're gonna play the "college is a normalized scam" card, then now is the time.
It's a shame what is happening, and it's not really clear how to fix the problem. How to safely maintain the social needs of humans during a pandemic is currently an unsolved problem, and no, Zoom isn't the answer. We'll probably see heightened suicide and crime rates for the duration of the lockdowns.
If you're talking about sets, then yes. Doing that on lists would be awful. Lists don't have the same guarantees as sets, so the operator would have plenty of behavioral ambiguity. You'd have to learn the convention of the operator for edge cases where the operation is not well defined.
Your game is faster paced, I like it. One issue I noticed is that the red blocks can spawn right in front of your block, making it nearly impossible to avoid. Rage quit inevitable.
Good call. I'm impressed they implemented it that way. It's hard at first, but once I got used to the sensitivity, I found the mobile version of this game a lot easier to use than the desktop one.
I doubt it. I don't see how more developer agency is a bad thing. If anything, more people will start using Github earlier on in their development cycle and Github will be the obvious platform of choice for when those projects are ready to go public. On the contrary, I think we'll probably see less trash and more quality projects on Github.
Besides, I wouldn't want to live in a world where people want to do X (private repos) but are forced to do Y (public repos) because X is not feasible. Now X is feasible and the landscape will more accurately reflect developer intentions.
I probably won't move to Gitlab or Bitbucket, then. This was the number one reason why I was considering it, now I can finally have personal private projects on Github. Good move on Microsoft's part.
I disagree. If you are writing shippable code in an article, it's because the article is about how to write shippable code. This article is not about that, so writing shippable code risks detracting from the main purpose of the article.
I think he was making a distinction between the app and the site. AFAIK, most Facebook users utilize Facebook primarily through the mobile app. If you look at Google trends[0] for Facebook, you'll notice a linear decline since 2011. I believe this is due to the onset of the Facebook mobile app, but feel free to correct me if I'm wrong.
I second this, I did the exact same thing and it made me a bit mad -- why include interesting placeholders if you can't just "go" with them. So, in its current state, it might be a bit counterintuitive and could have a better UX.
We have at least three people employed who's sole responsibility is to pester people about ticket status, apply bulk changes in Jira, define conventions, and ultimately make life harder for individual teams who wanna follow their own processes. As an EM, my higher-ups would rather have me ensuring ticket status is perfect to the T instead of pairing with and assisting my engineers.
I kid you not, we have directors of engineering who spend half their working day making bump/nudge comments on tickets.