Andrew Stellman

Working on a specification for https://lnkd.in/g-pBfAQv. Then I can verify it with tests and https://blprnt.tech/. I'm reminded that wormwood is optimized for readable source code, not UX. There is very little syntax validation.

4

The article discusses various strategies for preventing users from making mistakes or taking dangerous actions in user interfaces. It covers different methods such as modal dialogs, two-factor authorization confirmation, delaying actions, the undo option, and inline guards. The article also discusses the concept of a "danger zone" for grouping critical actions, as well as the idea of second-person confirmation, where an approver is involved in the process. Read it at https://lnkd.in/gq6GEw2D

2

Imagine having a co-pilot in your testing process that ensures efficiency and comprehensiveness. Spec2test, as discussed by Scott Aziz and John Ferguson Smart on TestGuild, offers just that.   It's not only about improving your user stories but also about automatically generating test cases that cover all bases—from functionality to security. This tool exemplifies how AI can act as both a guide and a guard in the software testing landscape.   Learn how to make AI work for you, elevating your testing strategy to new heights. Catch the full episode now! 👇👇👇 https://lnkd.in/ejHm25ui   #BDD #behaviordrivendevelopment #ai #aiintesting #Aidriventool #Spec2Test #softwaretesting #userstoryoptimization #testgeneration #InnovationInTesting #AIDrivenSuccess #testautomation #automationtesting #testguildpodcast

37

1 Comment

Discover a transformative conversation on systems thinking with our special guest, Michele Sollecito, in this episode of the Mob Mentality Show. In "Michele Sollecito on Systems Thinking: Seeing the Interactions Beyond the Parts," Michele shares valuable insights and practical examples that can revolutionize your approach to system optimization and organizational management. https://lnkd.in/gFE4DuAD https://lnkd.in/gyHPmNYB ### Topics Covered: **Systems Thinking:** - **Seeing Systems Everywhere** - **Focus on Interactions** - **Person Issue vs. System Issue** - **Animated Causal Loop Diagrams** - **Sub-System Optimization** - **System Fracturing from the Top** - **Trunk Based Development (TBD)** - **Benchmarking and "Copy-Paste" Pitfalls** - **Defensive Posture vs. Experimentation** - **Changing Core Beliefs** - **Leadership and Fake Experiments** - **Data vs. Emotion** - **Comfortable Inefficiency** - **Team Dynamics and Failure** - **Culture of Continuous Improvement** - **Managing Resistance to Improvement* **Software Architecture:** - **Specialists vs. Generalists** - **Technology Obsession** - **Distributed Systems** - **Coordination Strategies** - **Paired Product Ownership** - **Autonomy vs. Consistency?** **Ensemble Programming:** - **Resistance** - **Paradigm Shift to Fun** - **Early Adopters** - **Collaboration and Virtue** - **Sustainable Development** - **Avoid Echo Chambers** - **System Level Relationships with Mob** Don't miss this enlightening conversation that can transform your approach to systems thinking, software architecture, and ensemble programming. Listen and engage with Michele Sollecito's insights on the Mob Mentality Show! Huge thanks to Peti Koch who recommended Michele Sollecito come on the show 👍 #SystemThinking #Leadership #TrunkBasedDevelopment #TBD #Benchmarking #Experimentation #Vulnerability #Data #Blame #Fear #ContinuousImprovement #Habit #Silos #DistributedSystems #SelfOrganization  #ProductOwnership #CollectiveOwnership #Autonomy #Deadlines #MobProgramming #PairProgramming #EnsembleProgramming #Teaming #Teamwork #Collaboration #Fun #Burnout #SustainablePace #EchoChamber #Learning #Growth

12

3 Comments

This is a great little mini-series on the myth of "No CGI" and "Practical Effects Only" in movies. It's fascinating to see both CGI so good no one notices it and to see how blatantly movie producers and promoters lie about using CGI https://lnkd.in/gtmvib82

4

1 Comment

As mentioned in my previous post, here's our first of our video versions of our podcasts that we're releasing - and interview I did with Ken Rubin. https://lnkd.in/gWSmKiba

5

Applitools released a new Playwright SDK recently that makes integration with Playwright even more seamless, utilizing Playwright fixtures for that. It also "supercharged" the standard Playwright HTML reporter, making it integrated with the Applitools dashboard. In the two new videos, I show how to make this integration and core Applitools features, such as match level adjustment and cross-browser testing using Ultra-Fast Grid. Links to the videos are in the comments.

35

3 Comments

I believe that when people lament about tech debt, it's a misdirected complaint. Engineering teams will always be producing some amount of technical "debt." Even if we write beautiful, well-tested code that fits some noble architectural paradigm and meets every standard we can come up with, it is guaranteed to be deficient in some way--either now or to the team's (or our own personal) future views on what constitutes good code. When we write code, we come to some consensus as a team around what approaches we generally accept and what trade-offs we are generally willing to tolerate. And that's completely normal and unavoidable. But when we complain about tech debt, what we are actually complaining about is a deficient process. All software teams need to have dedicated time to revise our work. Far too often, we prioritize feature development over all other things. The end results of that deficient process are, invariably, twofold: a product with shiny new bells and whistles and a sea of spaghetti under the hood; and a team of stressed out engineers who have to work in a messy, frustrating codebase every single day.

19

11 Comments

Simple explanation of how an API works. https://lnkd.in/eGtW8mHU

3

How to ruin a Developer's or UX's Designer's day. And save the product. Yes, let's explore and use your product. It's obvious...right? uh right? of course! Any child can follow along! Children can think like this until they are trained out of it. Obviously a skit. but how often has it happened in real life? If a person or company has a lot of hubris and doesn't think about and test edge-cases .. well .. at best one can get unexpected results. At worst - a catastrophic failure. ps. I don't know if he is talking to her, or a child off screen, or himself. I was first slightly offended. Then I realized made the skit even more amusing. Developers watching QA test the product. https://lnkd.in/eWZi8W22

1

"Our documentation is great!" said no one ever. It is always interesting to talk to folks about this problem. It'ss a problem that can be hard to grasp, measure, and even harder to solve. That is; unless you think about it in a different way. A little bit of simplification, structure, and even some AI might do the trick. I also found a new AI tool, Unblocked, while at LambdaConf this week. I am excited to start experimenting with Unblocked and think it could be a game changer when it comes to managing documents across an organization. Check out my latest article where I talk about #knowledgemanagment. Dennis Pilarinos Daniel Horton

28

1 Comment

Nice write-up and some great points by Björn Friedrichs. Correlating points to time is a major anti-pattern in estimation. Also other bad practices that put people off story-point estimating are: 1. No baselining. Find a simple feature in your domain (say 'basic auth login'), agree on a point value for it (say '2') and estimate other items relative to that. Do the same for a more complex/larger feature, say an '8'. Now you have a baseline and you can do relative estimation. 2. Finger-in-the-air estimation. You know, when someone thinks for 2 seconds and then says "that's a 5, erm.....a 3, no wait a 5, definitely a 5". Don't do that; instead break down the tasks needed to deliver that item, e.g. create a new db table, add a new component to a view, do some input validation, modify the CI/CD pipeline, etc. Having a list of what's actually needed will give you a much better idea of the difficulty and complexity of getting something done. Which brings me to the next point... 3. Assess the complication *and* the complexity of delivering the item. 'Complex' is not the same as 'complicated'. Complex problems rely on the interconnection of different parts, while complicated problems are just structured in such a way that is difficult to understand or navigate. Adding a web endpoint that aggregates the output of several different internal services, for instance, is not complicated but it's complex, as we rely on orchestrating many simple tasks. Implementing the Smith-Waterman algorithm, on the other hand, is not complex (we're manipulating a single data matrix) but it's well complicated, as there are intricate rules and special conditions that are difficult to grasp. Complex problems are inherently more risky, the error area is much larger. Complicated problems have smaller error areas but may require more time/effort to solve. They should both be reflected in your estimation. #estimates #estimation #storypoints #scrum #agile

6

1 Comment

Interesting article. I firmly agree with the task breakdown and implementation detail. Has anyone tried using number of tasks and average rate to project timing?  https://lnkd.in/e_HysuiJ

10

1 Comment

I need to get better at identifying and coining maxims that I've come to believe. Here's some for pure func prog • Parse, don’t validate • Make illegal states unrepresentable • Errors as values • Functional core, imperative shell • Smart constructor https://lnkd.in/gvJC7f9X This is half the battle at communicating your work and being legible. Without a hook or gateway for people to Reminds me of the not-yet-numerous-enough (but aspiring to be) 95 theses on @sliminality (@slim.bsky.social)'s https://slim.computer Yet, important context gets left behind when tacit knowledge is packaged as quips. "Move fast and break things" and "Perfect is the enemy of done" are for people with a certain proclivity. If you don't have the problem, the advice is not for you. Too often people want to pick apart some quip communicating tacit knowledge, and then claim it's bad advice for everyone. More helpful would be to reintroduce context (either historical or interpretive for the modern era). "This advice only applies if you're in this context."

2

In this video I propose the idea that developers are essentially people pleasers who want to be loved and praised while QAs are essentially sadists who want to prove that you're not as smart as you think you are. Am I wrong? Watch this video and let's see!

11

As I note on Twitter, I don’t know if this is a *good* idea, but I was thinking about creating a free ZIO book from open source examples to help new ZIO developers get going as fast as possible: https://lnkd.in/eZ5Dtgua The basic idea is that if people will contribute their small example ZIO projects with a README file that describes the project, I can do the legwork to create a book (PDF, ePUB, Mobi) from those.

30

5 Comments