Attention Alchemist
@alexbunardzic
Followers
4K
Following
15K
Media
3K
Statuses
54K
In pursuit of sophistication It's not possible to understand the problem before we try the solution/
Cascadia
Joined January 2009
My article on best TDD practices now published in . #tdd #mutationtesting #softwarepractices #SoftwareEngineering #Softwaretesting.
opensource.com
In my previous series on test-driven development (TDD) and mutation testing, I demonstrated the benefits of relyin
7
18
108
Next thing you know, we have the much dreaded "not my problem" mentality. Next thing you know, the pride in one's work and ownership disappears. How can anyone expect quality if there is no pride in one's work?.
0
0
0
Not only do developers in many companies not talk to customers, but they are not allowed to even take a peek at the production environment. They have willfully been sealed off from the production. That approach breeds indifference.
1
0
1
Vibe coding improves the feedback. Paper takes anything, so when crafting those user stories, we get zero feedback. I'd recommend vibe coding instead.
0
0
0
Vibe coding is getting a bad rap because no one factors in how much fun and discovery it affords those who do it. You get to learn much more about your problem domain when vibe coding than you get to learn when creating those pedestrian "user stories".
1
0
1
Also, increased frequency implies increased feedback, and without feedback we have no way of knowing if things are moving in the desired direction. Postponing the feedback is a surefire way to increase the risk.
0
0
1
The frequency of changes to production is directly proportional to the absence of risk. The larger the batch that contains the changes, the greater the risk.
1
0
4
Violate any of those XP principles by letting AI take the wheel and go fancy on us, and we'll suffer the very unpleasant consequences. Learn and master XP before you dip your toes into AI-assisted software development manned by the fanciful genie.
0
0
2
All the things we've learned from applying the principles of Extreme Programming (XP) remain 100% valid and applicable in the age of AI-assisted software development.
2
1
6
RT @christianhujer: Please stop prefixing interface names with "I". Like, "ISuiteListener". That the type is an interface is an implementat….
0
1
0
There is a reason why dynamic, competitive teams release to production many times per day.
0
0
0
In software, the "let the sleeping dogs lie" risk aversion mindset ironically produces higher than expected risks. Digital rot never sleeps, and sluggish teams are exposed and very vulnerable to inevitable outages and defects that even the mere passage of time creates.
2
0
0
Technical excellence means changes to the system are deployed to production frequently. The more frequent the deployment of the changes to production, the higher the degree of technical excellence. Frequency beats speed any day of the week.
0
0
1
Anyone who thinks that the value and outcome that may directly impact their business has nothing to do with technical excellence is playing Russian roulette with their business.
0
0
0
It always comes as a surprise to me when I realize how many people prefer speed over frequency.
0
0
0
That's how people who push back against AI talk. Any new technology elicits such or similar responses. Be it the printing press, telephone, radio, cinematography, TV, computers, the internet, smartphones, social networks, you name it.
0
0
0
Taking public transit makes you dumb. You don’t learn anything, you just kill critical thinking and any potential to grasp the skill of driving and navigating the city. Say no to public transit!.
2
0
0
Instead, blame the fool who refused to learn the craft.
0
0
1
Let's make one thing clear: AI is not your babysitter. AI is a tool, just like any other tool. If someone does not know how to use the tool and is yet foolish enough to use it, when the tool creates damage, it is unfair to blame the tool.
2
1
1
