Also, introverts need time alone. Quiet time. This is equally true for parents. It's not just a preference; it's a need. Without this, introverts are literally incapable of taking care of themselves or another human being.
451 karma · joined October 4, 2013
Whiteboard sessions focused on algorithms and data structures will probably resemble CS20X college courses.
* Committing to dates and then being accountable for the results
* Spending time planning, rather than "doing"
* Admitting to business leaders that much of their work time is not spent writing lines of code, but dallying in all the interesting byways of the field, favorite websites, pet projects, and random semi-related technology interests
* Sitting in meetings of any sort (sprint planner and retrospective)
* Having spoken, out-loud disagreements and negotiations in order to arrive at a consensus (sprint point estimations)
* Having their mistakes, miscalculations, lack of planning visible to everyone on a big monitor (sprint board / retro)
* Getting out of their chairs to go talk to someone else in order to remove a blocker or understand a dependency (task estimation and completion by end-of-sprint)
* Anyone involved in the process that isn't a coder (Scrum Master, Project Manager)
As a manager, how do I know how long a Kanban task should take? How do I know how long it's been in-progress, or how much is left? (With sprints, the idea is that every task should be defined as completable within N weeks. So it's pretty simple to estimate when deliverables will be done.)
Sprints can work very well if you need to:
A) Estimate the time it will take to complete a large project B) Compare productivity of different teams so you can shift or add people C) Get continual feedback on the work quality and the workflow process
Over time, I've seen sprint teams become very accurate at estimating their work throughput ahead of time. This can be extremely valuable to the business delivering on its goals on time and committing to the right amount of deliverables.
If you have a large task, one that's either too complex to estimate accurately or with too many unknowns or outside dependencies, you should be breaking it up into smaller tasks.
Developers decide how many points they can do in a sprint, AND they decide how many points each task gets. There's no rushing involved here.
Rather unfortunate that the corporate world seems to be seeing its own absurdity in the mirror, but then choosing an unrelated scapegoat to point fingers at.
It also seems totally not necessary to pick on the practice itself or to single out yoga from the universe of things that are mis-used, appropriated, ripped-off, and marketed by the corporate world.
Couldn't agree more. Someone in every meeting needs to be taking notes and sharing them to Slack.
In an agile environment with many changes in-flight each sprint, or doing daily hand-offs (for a follow-the-sun support model), the communication overhead becomes significant. It's tough to keep up with what N other coworkers are doing every day, plus do your own work.
In my group I've seen some pretty bad resentments build because of the perception that people were left out of the loop. Or, because someone didn't overcommunicate his changes and broke something downstream.
Coupled with the fact that there's a 12+ hour turnaround time on even simple communications between the sites, people can feel pretty frustrated.
We use a Slack channel for daily standup updates and changelog; that helps if people are disciplined about it.
The worst thing though is "othering" -- it's human nature to point fingers at the group across the hall, in the next building, and definitely across the ocean. If you have immature or problematic personalities on the team (don't we all), rifts will occur and deepen without regular face-to-face contact.
And, we do know we're about to hit a point of no return in terms of climate and the viability of the civilization.
Monoculture (conventional corn or soybean for example) uses huge amounts of synthetic fertilizer to increase yields per acre far beyond what the soil can naturally sustain. Wide swaths of American farmland has lost literally feet of topsoil over the past 50 years. The soil is largely sterile, and depleted of minerals. Monoculture also means the ecosystem that can replenish the soil is absent.
So why do we need new phones then? "People don't know what they want until you show it to them." ~ Steve
Also, as others have noted, they turn on new features that could incur more cost, but they don't really provide RBAC, so anyone on your (maybe huge) team can start using those features.
Also, it's the bees knees for tech meetups and generally being an active technologist.
But honestly, it's oppressively expensive if you're not making well over $150K. Forget buying a home here. And renting, you'll just know every day that you're getting screwed. Even if you can "afford it," it doesn't feel good to know so many Americans are struggling and meanwhile you're burning money to live here.
Having lived here myself for over 8 years, I can say that culturally the city has been decimated. Only the rich can play here now. Students, teachers, artists, normal people of all kinds are priced out. For me, that means 90% of the friends I've had over my lifetime cannot afford to live in my city. It's not a good feeling.
My other experience has been that the city is no longer friendly, most store clerks and other folks you'll interact with on a daily basis are stressed out because they are commuting from 60 miles away to work here (serving the rich). Don't even get me started about the Uber drivers.
Despite all that, it's a beautiful place, and easy to romanticize, and I still love calling it home.
https://www.fasebj.org/doi/abs/10.1096/fasebj.29.1_supplemen...
Certainly the crush of additional cars double-parking in bike lanes, making illegal turns constantly, and driving poorly on unfamiliar streets has reduced the quality of life in SF -- speaking as someone who has lived there for nearly ten years.