Profile avatar
agile-otter.bsky.social
Software, guitars, books and articles, Industrial Logic's own Agile Otter
292 posts 2,442 followers 9 following
Regular Contributor
Active Commenter

Thought: People don't believe that tools and techniques can make their jobs easier & faster. Hence so little uptake on TDD, pair/mob programming, learning to use the editor well, learning the language grammar and standard library, etc. They believe there is no point to it, & nothing gets better.

An interesting problem of AI coding: "You have run out of tokens for this month. Upgrade your account to access more tokens." I ran out of coins to feed the machine while it was in the middle of a task; it left me with unfinished work and an inoperable side-project.

When someone talks about working in "swarms," what does that mean to you?

"The survey findings unveil that [TDD] offers substantial benefits in terms of early defect detection, leading to reduced costs and effort in rectifying issues during the development process. Moreover, [TDD] encourages improved code design and maintainability..." -- Rahman, et al, 10/2024

Stand and sing the anthem of the church of the status quo: "Unless you first prove with irrefutable, undeniable, incontrovertible, highly-relevant, scientific evidence that this will work for this team in this company at this time, we are not trying it."

Just for the record: Agile (nor any given methodology or framework thereof) is not based on "communicating through cards" and "the card" is not the primary means of communication. The primary means of communication and progress is the coded behavior and capability of the product.

I could use a nice trip to somewhere in Europe or the UK. I'd like to sponsor my trip by doing useful work with your company. I have a lot of skill and experience in software delivery, code craft, and team management. Consider contracting me for a few days. I would love to help.

Coming to terms with AI code partners is weird. I shouldn't be surprised that they sometimes un-write code in the craziest ways, leaving things terribly broken.

The technique problem with legacy code is that since it wasn't written with tests, it's hard to write tests without changing the code, and it's scary to change working code without having tests. Writing tests last forces you into this legacy code situation.

"You should have done x" is usually about the speaker's expectations rather than the listener's past actions.

"I bought the same car and suit as a millionaire; this will make me a millionaire, too!" Imitation as manifestation? What is the name for this "expect to achieve by shallow impersonation" cognitive bias? You see it a lot, but I don't know what it is called.

I love articles that say "We don't use agile, what we do is..." and then describe something 100% in line with the Agile Manifesto. I guess they mean "We don't use [SAFe, scrum, XP, LeSS]" but that's not how it's presented.

What are your thoughts about this python code: target = next(account for account in accounts if account.disabled())

Do you remember all those rushed changes that your developers implemented three years ago and how they complained about the design damage they caused to make that happen? It's all still in the codebase. It doesn't disappear. It never disappears.

Asynchronous does not mean Parallel industriallogic.com/blog/parallel-efforts/ There is simple math for this.

Humidifier Review xkcd.com/3044

i thought "maybe I'll see if AI can refactor this..." then I noticed that IntelliJ does it fine. It's all built in. Three or four steps later I'm done.

I needed to dive back into Java after working in other languages for a while, and forgot about reference semantics and mutators. I copied a date (I thought, really just shared a reference), then used the Calendar.add() method which mutates the date and returns nothing, and...