What a great gathering at @bigdatabelfast! 🎉
Last week, we had the amazing opportunity to connect with industry leaders in data and business, exchanging knowledge and insights.
Let us know your key takeaway if you were there!💡
@SusanBrennan4@NIDevConf@Liberty_IT Thanks Susan. It was great fun. What an excellent conference and so well run. It was lovely seeing you and the Liberty IT gang there.
@KarlKyck knocking it out of the park today at @NIDevConf covering Testing Excellence. Great to showcase the mission and HPE practices that help make @Liberty_IT excellent - thanks to Karl for awesome thought leadership 👏
We had a wonderful time at the community open day at Terenure Garda Station! Thanks to the super friendly gardaí for giving us a tour and showing us the equipment they use to do their work, keeping us safe. The kids had a great time! @gardainfo
There is no way to avoid or replace the hard work of thinking. When you write a test you are thinking about how to specify behavior. When you make the test pass you are thinking about how to implement that specification. When you refactor you are thinking about how to communicate both the specification and implementation to others.
You cannot replace any of these thought processes with tools. You cannot generate the code from tests, or the tests from code, because that would cause you to abandon a critical thought process. And may God help you if you use a tool to do the refactoring for you.
The purpose of a tool is to enable and facilitate thought; not to replace it.
NEW POST
While coding assistants like Copilot can improve speed and flow, they can also disrupt it. Birgitta Böckeler looks at two ways in which they can get in the way: amplifying bad or outdated practices, and review fatigue.
https://t.co/UerXbksAqh?
I’ve been reluctant to try ChatGPT. Today I got over that reluctance. Now I understand why I was reluctant.
The value of 90% of my skills just dropped to $0. The leverage for the remaining 10% went up 1000x. I need to recalibrate.
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.
https://t.co/YW7NtxVVt2
I got a message about code health something along the lines of, "How can we convince the business that pursuing beauty in the code is valuable?" You can't. Wrong framing. Offer them something they want instead.
NEW POST
Conways Law has been an important part of my thinking for years. Important enough to affect every system I've come across, and powerful enough that you're doomed to defeat if you try to fight it.
https://t.co/CSl5ejLDik
@tmclaughbos This book describes the nature of complexity in software systems and suggests ways to reduce it. First half is great, second half is controversial. It's a good read: https://t.co/BRPCDELvPf
@tmclaughbos Breaking it up into bounded contexts sounds like a good move. It may be possible to avoid passing unnecessary complexity onto your clients by adding a client facing layer that hides that complexity. Provided the investment is justified of course.