#codefreeze
@teufelsweiblein bin selbst nicht da aber habe aktuell das Gefühl, dass ich das Camp 3-4 Tage im Zelt auch nicht überleben würde... Schon coole Stimmung, was ich so mitbekommen habe. Vielleicht schaust du dir Mal #codefreeze codefreeze.fi an - bin '24 das erst Mal dabei aber ich glaube es wird klein, spannend, ruhig, interessant. Aber halt was ganz anderes...
Less than a month until I am back Nordic Testing Days in #Tallin where I will be speaking about, no encouraging you to start building better testing tools.
I've run previews of this talk now at #Codefreeze and #SoCraCan and in both instances received very positive feedback which makes me excited to share it with a broader audience.
Tickets are still available, and the city and the conference is absolutely worth a visit: https://nordictestingdays.eu/
Anfang April möchten wir das neue Release der #MintApps fertigstellen. Entsprechend unserem Zeitplan beginnt damit heute der #Codefreeze.
Über Hilfe beim Testen (https://kippenbergs.de/mint-index) und Übersetzen (https://translate.codeberg.org/projects/mintapps/) würden wir uns sehr freuen!
(TK)
#CodeFreeze keynote on #resilience (what is it? when do we need it? what is it made of?)
is on video now
https://www.youtube.com/watch?v=rSz85mT0ODg
Debian 12 ‘bookworm’ Reaches First Code Freeze
https://www.linuxtoday.com/developer/debian-12-bookworm-reaches-first-code-freeze/
#codefreeze #Developer #Bookworm #Debian12 #News
Resilience in software dev teams - late-night excerpts from my #CodeFreeze talk
https://jessitron.com/2023/01/16/resilience-and-waste-in-software-teams/
A video of the outdoor activities you can have at @codefreeze:
https://youtu.be/JSDBum5ASQE
Next year will be even more!
#Codefreeze
Writing it was surprisingly easy to do with the JS SDK: https://github.com/codefreezefi/matrix-guysbot-node
Running it on the same instance with systemd was also straightforward.
@coderbyheart unfortunately too far away, but when you happen to be in #munich check out #techsauna - https://nopants.dev - we're at the very beginning and first meetup is Jan 17... And I would love to join #codefreeze but need to see how this could work time wise.
When you bring too many electronic devices with you:
#firstWorldProblems #codefreeze
We will migrate away from the #SoftwareCrafters #Slack and use #Matrix from now on. Here is the guide on how to use Matrix so communication about #Codefreeze can take place there already: https://codefreeze.fi/chat
#codefreeze brought us so much energy, now there a second power outage within a week.
Leaving #codefreeze. Thanks to everyone who made this again a really special event. See you in a year!
So great to be back in-person for #CodeFreeze in #msp again. And hanging out in the side room with @bkoehn and @jessitron was a highlight even if the #rstats package I was looking at would not R CMD check. And of course amazing talks by @jeffsussna and Yolanda Smith
@tdpauw #CodeFreeze seems to be an incredible event and experience. Enjoy!
I never thought my profession would fulfil the dream of someone outside of IT 🤷
X: my dream is to see one day the Northern Lights
Me: I might have something for you, if you don’t mind being amongst passionate and the most kind people I’ve ever met.
X: ???
Me: Well, we have this conference called #codefreeze that’s happening in Lapland, Nord-Finland above the Arctic Circle. Second week of Jan. If the weather is good, we might see the Northern Lights.
X: Yes!!!
So, here we are 😄
This morning at #codefreeze we did a hike up #kiilopää 🇫🇮❄️. Cold but beautiful!
Just saw @jessitron has been tooting their notes from #CodeFreeze and I have all the feels.
I miss CodeFreeze so much.
No, that’s not right, I miss the people.
One day I will be back. 💙
Digging out of the snow: how can take 2 hours to do some work that will give us 4 hours back?
and then how can we take those 4 hours and get 10 hours back?
@jeffsussna #TechnicalAgility #CodeFreeze
To reach Technical Agility, don’t start suddenly deploying 14 times a day. Ask,
What are the best places to improve next?
@jeffsussna #CodeFreeze
Transformation, change in your teams — make this incremental too.
@jessitron @jeffsussna
Damn, this puts #CodeFreeze even higher on my to go list
Microservices trade delivery simplicity for operational complexity.
These platform and technical-consulting teams have to be product-centric, internal service teams.
The standard is set by the commercial cloud providers.
#TeamTopologies
works this out: how can DevOps and flow work in an enterprise?
Platform teams and technical-consulting teams scaffold technical agility at scale.
The core essence of DevOps “you build it, you run it” doesn’t work in a vacuum.
It doesn’t work automatically in an eng org over 30 people.
And it assumes a cloud.
SAFe says “when you’ve deployed code, you’re done.”
Nothing could be further from the truth.
Technical Agility:
Design/Code/Test for Operability
performance, security, reliability, etc and more stuff on the slide
When software is a service, your customers care about it.
Technical Agility:
Commoditize All the Infrastructure Things
ALL of them. not just production. also test, dev, etc
Technical Agility:
Shift Quality Left
(Define “quality” together.)
Tests are software. They’re part of coding; make them efficient.
Change, test, *fix*. Failed tests are an andon cord.
Technical Agility:
Architect for Changeability
Bad:
“A simple change takes a week”
“every time we touch it, something breaks”
This slows flow. That is a business problem.
Technical Agility Principle #1:
Value flow over quantity.
key metric: New Value Cycle Time
how long does it take you to deliver 1 piece of value, end to end?
(fixing bugs doesn’t get you new value, so quality is part of it)
Technical agility can:
* change code easily & safely
* deliver changes as soon as made
* rapidly detect and respond to unintended impact
* with compliance, security, reliability…
* scale all of these
@jeffsussna #CodeFreeze
The Missing Piece of Agility:
To learn from what we’re doing
we need to so something
and then understand what we just did.
@jeffsussna #CodeFreeze
Solutions create new problems.
Continuous Discovery asks, “What new problems did our solutions create?”
The point of a standup is to adapt.
Not to give status, but to change what we’re doing based on combined information.
@jeffsussna #codeFreeze
Continuous Delivery is part of what we want,
but not the sum total of what we want.
@jeffsussna #CodeFreeze
Unfortunate terminology:
Backlog, Sprint, Release Train
… oh, the linearity 😭
@jeffsussna #CodeFreeze
The assumption built into User-Centered Design is: “we’re probably wrong.”
@jeffsussna #CodeFreeze
A long time ago, @swardley
and I fought a losing battle for the phrase “utility computing” instead of “cloud computing” because it’s accurate and says something.
oh well.
@jeffsussna #CodeFreeze
Resilience: the ability to respond constructively to misfortune or change.
“Agile processes harness change for the customer’s competitive advantage” - back page of the manifesto
Sometimes applying automation turns a system from sloppy but resilient to fragile and brittle.
@jeffsussna #CodeFreeze
Feedback: the gap between Actual and Expected.
Cybernetics: circular causality. What’s happening informs what you do, which changes what’s happening.
like steering.