We want to create stronger ties between Philly’s technology and sports communities. That’s why Philly will be joining Boston and Montreal in hosting a Baseball Hack Day, a one-day event to encourage the development of baseball-related tech projects, partnerships and experiments. It kicks off March 28 at CityCoHo on 24th and Walnut.
Philly joins Boston and Montreal in hosting 2nd annual Baseball Hack Day
Launch when you aren’t ready
I launched my site knowing it was far from perfect. It wasn’t responsive. It didn’t display any particularly appealing animations. It was lacking polish in several places. Regardless of this knowledge, I still chose to launch.
As a father of two and full-time designer, my time is limited, as is my energy level. Releasing a site, even when I know it isn’t perfect, encourages me to continuously work to fix the glitches. I strive for perfection and expect no less from my personal site. I therefore force myself to continue to work towards improving it and including any missing details I might have originally omitted.
I hope to establish a regular rhythm of continuously improving my site. While there is much effort put into that initial launch, the goal is to keep writing articles and updating my designs. This habit will not form solely from the initial decision to make my site live – in order to continue, I must establish a pattern that I will seek to repeat.
The web is constantly changing and evolving. It should be a place for us to watch each other grow as both professionals and human beings. I miss creating projects for myself during my free time, and I hope this site will serve as my platform to once again do so.
DIY Design Sprints
Before each design sprint that I lead, I formulate an initial plan in order to feel confident about the schedule going into the sprint. admit that this process is a bit haphazard. To frame my plan, I reflect back on prior sprints to analyze what went well and what needed improvement.
Converting to Jobs Stories
We have used user stories as part of our design and development process for many years. You could find several mentions of them throughout our playbook. We used user stories to give designers and developers context to the problems that the user is having and give space for them to solve that problem while building the product.
The difference between perfection and iterating
A college ceramics professor once conducted an experiment amongst her students. She split the class in half and assigned each group a separate task to complete over the duration of the semester.
The first half of the class was to be graded based on the number of pots they could create throughout the semester. The more pots they made, the higher their final grades would be. The students from this group immediately began churning out pots as quickly as they could make them.
In contrast, the second half of the class was told that their grades depended on the quality of a single pot; it needed to be their best possible work. Each of these students tirelessly worked to create the perfect pot to submit for grading.
At the end of the semester, the professor asked the students from the first half of the class to present the last pot they created, while the second half turned in their single pot. Outside artists were then commissioned to critique the quality of the students’ work and overwhelmingly declared that the craftsmanship of the pots from the first half of the class was far superior to those of the second half.
I admit that I’m unsure of this story’s origin. If you know it, however, please reach out to @kylefiedler.