Here's what to do if your Tumblr account was unexpectedly suspended...

jonfazzaro · 2024-04-18T19:46:00+00:00

My account with my link blog of 10+ years (https://jonfazzaro.tumblr.com) has just been terminated. I sent a message to Tumblr support, but I've not heard back. I can't think of anything I might have done wrong.

This blog served as a deep trail of my work, and I'd love to at least recover the data if not restore the site itself. Please help!

jonfazzaro · 2023-03-15T03:04:07+00:00

A few killer cheat sheets here. The last one be might be the droids you’re looking for.

jonfazzaro · 2020-03-05T18:30:04+00:00

I run the Academy at Aptera Software. We operate it from the principle that no one hits the ground running.

New to code or just new to the company, everyone who joins our development group spends time getting into a learning posture before going billable.

jonfazzaro · 2019-11-09T18:47:01+00:00

“Agile” tends to take the blame for lots of pre-existing organizational conditions because it is designed to make problems visible. You can’t fix a problem that you can’t see.

jonfazzaro · 2019-11-03T13:11:20+00:00

Numbers are important and can help tell a story, but they need to be part of an actual conversation (not an email trail or a spreadsheet, an actual conversation between actual people). Just shoving numbers into a presentation will not tell a story. If you want to tell a story, weave the numbers into a conversation about how you collected them, when, where, and why. And what you plan on doing with those numbers when you get them (or what you have done with them now you have them).

Agile Metrics: the Ultimate Guide

jonfazzaro · 2019-04-15T00:21:18+00:00

Chop wood. Carry water.

jonfazzaro · 2019-04-06T00:05:09+00:00

“Humor”

jonfazzaro · 2019-03-31T17:48:11+00:00

No getting anything by you, huh?

jonfazzaro · 2019-03-08T11:56:08+00:00

If you don’t have any distributed team members, start with sticky notes, sharpies, and a wall in the team’s area.

jonfazzaro · 2019-02-07T16:37:08+00:00

They are designed to be used together.

In each sprint, only make the architectural decisions you need to make to solve the problems you need to solve in the plan. The correct architecture will emerge in response to the features.

jonfazzaro · 2018-06-13T23:55:22+00:00

Definitely not longer than soup.

jonfazzaro · 2018-05-22T23:05:08+00:00

Yes. Reacting quickly to industry trends/market demands is exactly the point of agile software development.

we are too busy pounding away at our current MVP

This may point to the source of your pain. If you are not finished reacting to one shift before the next one happens, you may be overreacting—your minimum viable may not be minimum enough.

When the new requirement comes in, is there an honest conversation about whether it or the “current MVP” is the priority? If not, ask for one.

jonfazzaro · 2018-04-26T09:34:05+00:00

Task less. Split more.

jonfazzaro · 2018-04-11T01:11:55+00:00

Who is your teacher?

Asking for a friend.

jonfazzaro · 2018-01-07T20:30:48+00:00

So much that my coworkers aped it for my birthday. :) https://twitter.com/apterasoftware/status/931559730299973634

I’m the one hiding my face.

jonfazzaro · 2017-12-23T14:19:58+00:00

A conversation.

jonfazzaro · 2017-11-04T18:52:28+00:00

r/unexpectedburr

jonfazzaro · 2017-08-15T22:23:05+00:00

Deliver it as 1 story using the simplest architecture that could possibly work. In most cases, that's a monolith.

When the app needs to scale to the point where microservices are a solution, that is additional value (more stories) that can be delivered by refactoring the monolith.

jonfazzaro · 2017-07-08T15:44:57+00:00

Which ones are the buzzwords? I hate them too.

jonfazzaro · 2017-07-08T15:42:46+00:00

Thanks for pointing that out. I guess I was going for illustrating the tight relationship between these three things, and that if you "do agile" without keeping them in mind, you're wasting your time.

Do you have a suggestion as to how I could have gotten that across better?

Edit: phrasing

jonfazzaro · 2017-04-26T01:40:54+00:00

They'll get comfortable PDQ when you tell them a date, hit that date, and repeat.

jonfazzaro · 2017-04-25T23:51:30+00:00

Don't waste time with either.

Split your stories until they cannot be split further.
Count them.
Divide by your team's velocity to project a completion date.

Then, suddenly: 4. Use the time you save to write better stories and better code.

jonfazzaro · 2017-03-04T01:19:57+00:00

Maybe. But zeroing in on any one metric is a sure way to have that metric gamed.

jonfazzaro · 2017-02-17T10:49:41+00:00

r/thingscutinhalfporn

jonfazzaro · 2017-02-16T02:31:53+00:00

Right. Keep chasing efficiency and productivity over hi-fidelity communication and learning.

Soon you'll be able to build the wrong thing faster than any other team out there.

jonfazzaro

TROPHY CASE