davidsabine, to epic
@davidsabine@mastodon.social avatar

Reminder: you're allowed to NOT use jargon.

The most misused, misunderstood terms: , , , , , , , , , , , , , , , and .

ConfluxHQ, to random

🚀 SOLD OUT! 🎉 See the Programme ➡️
We're thrilled to announce that today's CTO MASTERCLASS at 12:00 pm GMT is officially SOLD OUT! 🙌 To the amazing attendees: We can't wait to welcome you!

Get your 📚notebooks ready!

1 hour to go!! You can find today's 🗓️Programme if you Swipe➡️
See you all at noon for a day of learning, networking, and transformation!
Let's unlock tech flexibility and agility together! 🌟


Thanks again, to everyone involved!

image/png

ClayDowling, to random
@ClayDowling@techhub.social avatar

After watching my team drowning in an agile transformation when I joined, it's amazing to see how much adding a few simple technical practices made it easier.

TDD, ensemble programming, and a proper CI/CD pipeline doubled our throughput, and did it quickly.

We also switched to one week sprints. That gave us incentive to focus our stories into something small and easily achievable. We spend a lot less time doing story breakdown and sprint planning.

We no longer keep a deep backlog. If we aren't going to play the story in the next two weeks, we don't do more than the highest level of planning for it. Our short sprints gave us the clarity that the work that was needed would change before we could play a story planned a month in the past.

An needs to incorporate the technical first, before it looks at the change in project management. The technical changes give us the ability to make the useful forecasts about when things will be ready.

ConfluxHQ, to random

🇩🇪

Entdecken Sie das Geheimnis effizienter Teamdynamik und Produktentwicklung mit Team Topologien! 🚀 Neugierig? Jetzt eintauchen. 🌐 https://cdi.digital/team-topologies/


🇬🇧

Unlock the secret to streamlined team dynamics and product development with Team Topologies! 🚀 Curious? Dive in now. 🌐


Dave_von_S, to random

Over the last few months I’ve been dabbling into , , , etc and the red line in all this is ‘good and best practices often fail, because software development is complex’.

I fully recognize this, but it got me thinking ‘when does software development become complex?’. A ‘hello world’ should be simple (ie predicable) in any language (if it isn’t, you’re using the wrong language) and there are definitely things where best practices exist (eg alt descriptions for images).

I also don’t believe it’s the first moment where we introduce logic; any if/then/else or while loop can be specified, so that’s at most complicated, right?

So from a philosophical point of view; are there pointers that indicate the move from complicated to complex?

Is that even a code related thing or more about communication? And if that is the case, can you then state that a single developer can never arrive in the complex domain?

Yes, I understand that this is highly theoretical and in reality far away from situations we work in, but I’m curious if I’m the only one who thinks about this…

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • GTA5RPClips
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • everett
  • Youngstown
  • mdbf
  • Durango
  • slotface
  • rosin
  • thenastyranch
  • kavyap
  • modclub
  • anitta
  • cubers
  • tester
  • osvaldo12
  • tacticalgear
  • ethstaker
  • ngwrru68w68
  • khanakhh
  • Leos
  • normalnudes
  • cisconetworking
  • provamag3
  • megavids
  • lostlight
  • All magazines