Systems Thinker, Agile software developer, XPer, DDDer
Berlin, Germany
Joined March 2009
- Tweets920
- Following0
- Followers114
- Likes621
Ignacy Sokołowski @ignacy@mastodon.world retweeted
The agile manifesto says:
"We are uncovering better ways of developing software by doing it and helping others do it."
NOT
"We know the one true way to manage the software lifecycle. We don't actually write software, but we can certify you."
#agile
Ignacy Sokołowski @ignacy@mastodon.world retweeted
One of the hallmarks of good agile development, perhaps the thing that separates it from poor agile attempts, is the attention to design.
A good agile team will design continuously and refactor to the new designs. A poor team will just bolt on new stuff blindly.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Are you confusing 'refactoring' with 'rewriting'? Stop! Refactoring is about changing the structure without altering behavior. A simple name change can be a refactoring step; rewriting the whole module is not. #Refactoring #SoftwareEngineering #ContinuousImprovement
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Agile isn't dead, but it is widely misunderstood and more unusual than most people think.
a #Thread
1/12
Ignacy Sokołowski @ignacy@mastodon.world retweeted
PRs, statistically, increase risk, assuming that they are less frequent than daily and according to the data from State of DevOps reports. So if the engineer deems the risk to be high, they should avoid them.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
"It's hard to predict what this dice will roll."
"Well, then, you need to get better at predicting."
Conventional wisdom about software development processes - that unpredictable work needs better estimates, not a more predictable way of working.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
CD is literally principle 1. “Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.”
Ignacy Sokołowski @ignacy@mastodon.world retweeted
I confess that I am not a big fan of "The Test Pyramid" so here's a #Thread on what I think is a better focus for your automated testing strategy...
1/14
Ignacy Sokołowski @ignacy@mastodon.world retweeted
"First make the change easy (warning: this might be hard), then make the easy change."
- @KentBeck
Ignacy Sokołowski @ignacy@mastodon.world retweeted
'"Make the code as flexible as possible" up front is the opposite of the #Agile approach.' (Jason Yip).
Future-proofing is waste. You'll never need most of that "flexibility." Instead, make the code easy to refactor by making it as simple as possible.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
In this tweet @christofebert says "optimising for velocity is dangerous" in software development. The article that he references is behind a paywall, so I haven't read it, but here are some thoughts, and some evidence that counters this view.
(A thread)
1/17
As an agile method, #DevOps is used across industries. It connects development, delivery, and operations. Read our overview with a #Netflix case study in #IEEESoftware. One take-away: Optimizing for velocity is dangerous, as it increases technical debt.
ieeexplore.ieee.org/document…
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Now that content is so easy to create we seem to have lost sight of the notion that content should have value.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
It's time to get rid of pull requests for team work, and while we're at that, no more individual work. It's wasteful and inefficient. – at Crawley, South East
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Delete the term "CI/CD". It feels like 90% of people in the industry think that because they have a pipeline that they're practicing CI.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
A way of working
* checking out “clean” (git status shows nothing) and testing clean (“all green”) first.
* commit 5-20 times an hour, just little one-line and two-line changes.
* Pull w/rebase? 3 or 4 times an hour, then test, and if green push to main
* Repeat with next job
Ignacy Sokołowski @ignacy@mastodon.world retweeted
To throw one more fallacy on the bonfire: CI is not the practice of running a building test server. It is the behavior of developers sharing all their code changes frequently, at LEAST once a day.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Suggestion: If you must use the phrase "real life" or "real world," always put the word "my" in front of it, & never "the." I don't use the phrase, but my real world always seems to be very different from "_the_ real world" that some think is universal. It isn't.
Ignacy Sokołowski @ignacy@mastodon.world retweeted
Yes. After-the-fact inspection (e.g. PR-driven review) is ineffective. Quality needs to be built in—an integral part of writing the code. An inspection culture cannot replace a culture of quality. If an inspection finds anything, you're in deep trouble.
This Post is from an account that no longer exists. Learn more
Ignacy Sokołowski @ignacy@mastodon.world retweeted
For debugging and testing, devs have something to learn from proper scientific controlled trials.
- change one thing at a time
- observe each behavior before you change it
- try to falsify your beliefs (test creatively)
And yet…
Ignacy Sokołowski @ignacy@mastodon.world retweeted
The semantic diffusion around CI is fascinating to me. At some point folks conflated build pipelines with CI - as they were all using feature branches, *discontinuous* integration became the commonly understood meaning of CI. How did a negation supplant the original meaning? 🤷🏻♂️