Backend Development Lead at BEE by Growens
Cremona, Italy
Joined January 2008
- Tweets573
- Following447
- Followers126
- Likes2.1K
Roberto Albertini retweeted
This Instagram image got me thinking. What was the best Windows taskbar?
ALT Different versions of the Windows taskbar. Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, Windows 11
Roberto Albertini retweeted
Dear Software Architects,
If you want to write ADRs, write ADRs. But please also include tracking. If no one reads the ADRs, consider not writing them in future. Time spent writing ADRs incurs opportunity cost. Make sure you're getting something for the price.
Roberto Albertini retweeted
💯 maintaining that ability to iterate is central to the job of software development. Optimise for making it easy to change your mind when you learn new things!
Roberto Albertini retweeted
Spunti tutti nuovi per festeggiare l'anniversario più importante dell'anno nel campo dell'Agilità! Diamo il via ad 'aspettando #IAD23' che ci accompagnerà fino a novembre.
Conosci la pagina ufficiale di IAD23?
link buff.ly/2PM9Sx0
#IAM #AGILE
Roberto Albertini retweeted
The most important practice for continuous integration to work properly is frequent check-ins to a shared version of the truth of your system, on trunk or mainline. You should be committing your code at least once per day, and ideally a lot more often than that.
Roberto Albertini retweeted
I hear that Companies care about money and efficiency first, so they'll replace programmers with AI.
Just like they replaced dysfunctional teams of 250 people with small, cheap teams who can provably produce vastly better software in 1/10th the time.
Wait…
Roberto Albertini retweeted
#OnThisDay thirty years ago, in 1993, CERN released the World Wide Web software to the public.
Proposed by Sir Tim Berners-Lee, the web was originally created to allow scientists and institutes from all over the globe who were working on CERN data to share information accurately and quickly.
Find out more: home.cern/news/news/computin…
#CERNImpact #CERNandSociety
Roberto Albertini retweeted
NEW POST: Many software teams pack too much work into their iterations. Teams will usually run better when they have deliberate slack, as it allows their delivery to be more predictable and gives them time to improve their environment.
martinfowler.com/bliki/Slack…
Roberto Albertini retweeted
The data says working in small teams is one of the keys to success, so what gets in the way of small autonomous teams?
Roberto Albertini retweeted
Estimates are a tool for managing fear. When there is no fear no estimates are needed.
Roberto Albertini retweeted
Individual-performance bonuses (and the appraisals that lead up to them) destroy collaboration. They pit the team against itself. People hoard knowledge to get an advantage. It encourages "heroes," who are bottlenecks. Just don't. Pay everybody well! Problem solved.
Roberto Albertini retweeted
That ability to communicate intent is the whole reason that design patterns are useful. The patterns themselves are not new nor even very interesting; but the ability to name them is a huge advantage.
Roberto Albertini retweeted
I read Dave's tweet to mean you should be doing *some* refactoring all day, not that you should be doing only refactoring. I've encouraged an approach of Opportunistic Refactoring
martinfowler.com/bliki/Oppor…
Roberto Albertini retweeted
TDD does not take extra time. Writing tests _first_ is not overhead because they force you to think through the problem and partition it properly. You’d have to do that thinking anyway.
Testing after the fact IS overhead because you did all that thinking already.
Roberto Albertini retweeted
I'm quite enjoying reading "Building Evolutionary Architectures" so far, but I'd like to replace almost all occurrences of the word "architect" with "team" in the book. I mean, I expect architects to be part of teams, and teams to have full ownership of the architecture.
Roberto Albertini retweeted
A periodic reminder. TDD is a development, not a testing, strategy. I augment TDD tests with micro/unit tests as I work, though. You need both.
