The first Terminal event is HERE 👀
Welcome to an excursion with Pizza, Beer, and @WunderdogOfcl Developers!
Come spend an evening in the heart of Helsinki, talk about software development with us, and enjoy pizza and drinks!
https://t.co/EGgVEZux6l
“Surrounded by idiots” or “Idiootit ympärilläni” is a fraud.
"How Swedes were fooled by one of the biggest scientific bluffs of our time”
https://t.co/4FxpcxomOl
Feature programming:
1 day:
~1000 lines of code.
Bug fixing:
1 day:
~10 lines of code
Performance fixing:
7 days:
1 command line flag in a config file inside of docker file
Anything you work on is a "product." It has users & is designed (by you & others on your team) to achieve an outcome. This is true for policies (e.g., HR's unlimited vacation policy), initiatives (Finance's cost cutting drive) & processes (Procurement's vendor onboarding)
I don't like the clean/dirty metaphor applied to software. A dirty knife is a sign that the knife has been used to make food. “Dirty” software is a sign that the software has been used to make more software.
A classic that can be recommended for everyone in product development. Total of 175 principles justified using economics and engineering as a framework.
Check it out, the Defense Innovation Board has come up with 6 questions to see whether a project fits the term agile or is "agile BS" ! I'm personally pretty happy with these questions: If you had to change one or more, what would you choose?
https://t.co/9oWiO2JZqm
First have the vision and guiding principles figured out, after then only go for the details: roadmaps and backlogs. "Prioritize product blueprints over product roadmaps" https://t.co/y7isCjog2P
@johncutlefish Psssst...
You can demo things that aren't done.
You can demo things that aren't code.
You can demo things that don't work.
You can demo things you haven't started.