@nick_tune@hachyderm.io
@nick_tune@hachyderm.io avatar

nick_tune

@nick_tune@hachyderm.io

Staff Engineer

Callback enthusiast

Trainee Francophone 🇫🇷🇨🇭(DELF B1)

This profile is from a federated server and may be incomplete. Browse more on the original instance.

nick_tune, to random
@nick_tune@hachyderm.io avatar

A wooden table is made from wood.

A glass table is made from glass.

Why is a coffee table not made from coffee?

This is actually relevant to domain modelling: sometimes we name things after their properties and sometimes their purpose.

And sometimes we're talking about the same physical thing from the perspective of a different subdomain where it has a different name.

These factors also play a role in determining how we decide to shape boundaries.

#ddDesign #domainDrivenDesign

nick_tune, to random
@nick_tune@hachyderm.io avatar

VS Code is really nice and amazing for a free IDE. But still nothing beats the mighty JetBrains tooling IMO.

nick_tune, to random
@nick_tune@hachyderm.io avatar

After 3+ years in the making I am now the happy owner of physical copies of my book Architecture Modernization.

It's not really fair to call it "my" book because much of the content is real world stories provided by industry experts, so I would like to share this moment with all of the contributors:

cont’d….

#architectureModernization

nick_tune, to random
@nick_tune@hachyderm.io avatar

Elon Musk keeps showing us who he is and what a danger to society he represents, and people keep posting on Xitter and directly supporting him?

Just this week alone, he has been openly supporting the German far right, mocking the leader of a country being invaded, and downsizing the elecition integrity team.

Meanwhile he continues to support the likes of Tucker Carlson and DeSantis.

Not sure I can respect anyone who keeps tweeting through all of this as though nothing is wrong.

jeremydmiller, to random
@jeremydmiller@hachyderm.io avatar

This has been forever, but a few warning signs that your new job might not have been a good decision:

  1. The entire previous development team had all quit. Not laid off (but that's scary too), but quit
  2. Your new employer, a small software company, has a 20 page annotated dress code guide

Anyway, we all quit on a random Wednesday morning a few months in.

nick_tune,
@nick_tune@hachyderm.io avatar

@khalidabuhakmeh @jeremydmiller A 20 page annotated dress code guide?

Were you working as an actor in Bridgerton?

nick_tune, to random
@nick_tune@hachyderm.io avatar

Just published: Forming an Architecture Modernization Enabling Team (AMET)

This was written in collaboration with @eduardodasilva and tries to convey some of our key learnings in 2023.

Always happy to receive feedback on this article or suggestions for other topics that we need to cover.

https://medium.com/nick-tune-tech-strategy-blog/forming-an-architecture-modernization-enabling-team-amet-50d70a789331

nick_tune, to random
@nick_tune@hachyderm.io avatar

“But if we don’t force uses to watch ads and steals their personal data our business model will not be profitable“

Who Cares Larry David GIF by Curb Your Enthusiasm

nick_tune, to random
@nick_tune@hachyderm.io avatar

“Some of the most widely shared examples can be found on Twitter, posted by subscribers with a blue tick, who pay for their content to be promoted to other users.”

https://www.bbc.co.uk/news/world-europe-66113460

nick_tune, to random
@nick_tune@hachyderm.io avatar

Should you create a separate team to work on modernizing the legacy monolith while other teams focus on building new features outside the legacy?

This is a topic I've discussed on multiple occasions recently, and it's not an uncommon modernization question in general.

I'm generally cautious of this approach because...

1/n

#architectureModernization #legacyRefactoring #softwareArchitecture #ddd #domainDrivenDesign

nick_tune, to random
@nick_tune@hachyderm.io avatar

I recently spoke to a senior technology leader at scale-up company in the appointment bookings space. He said they had their most successful quarter because they delivered more features than they ever have before.

I think there are so many things wrong with measuring features deliver per-quarter (FPQ), but I'd like to hear the other side of the story and be proved wrong.

1/2

#productManagement #metrics #developerProductivity

nick_tune,
@nick_tune@hachyderm.io avatar

For me, FPQ is a terrible metric because it is easy to game, may lead to perverse incentives, and overall a feature tells nothing about the value delivered or the level of technical debt created.

It seems like a clear-cut sign that the organization sees software development as a feature factory.

2/2

nick_tune, to random
@nick_tune@hachyderm.io avatar

The cloud is just someone else's servers... and engineers who are the most talented in the world.

Moving from the cloud is not just buying cheaper servers like DHH keeps implying.

nick_tune, to random
@nick_tune@hachyderm.io avatar

Every new feature has at-least 3 costs:

  • cost to build
  • cost to maintain
  • increased cost of adding other new features

I think the 2nd two are probably the most important, whereas I feel the majority of people in tech only think about the 1st (especially feature factory companies).

nick_tune, to random
@nick_tune@hachyderm.io avatar

One of the most enjoyable aspects of writing my book architecture modernization was working with industry experts to write case studies.

It's something I want to continue. I'm going to set up a website for modernization info with a section dedicated to case studies.

If you'd like to share a modernization case study (or if you're just curious) then please contact me directly. I'll work with you closely at each step to create a polished article.

#architectureModernization

nick_tune, to random
@nick_tune@hachyderm.io avatar

Should you start an architecture modernization journey by building something completely new outside of your existing systems?

This can be effective as a way of demonstrating what's possible in your proposed "new world".

Faster time-to-market, better reliability, improved compliance, more efficient delivery etc.

1/n

#architectureModernization #techStrategy #legacyModernization

nick_tune,
@nick_tune@hachyderm.io avatar

Seeing this in real life can really blow people's minds who are used to traditional or legacy-constrained ways of working, which can then lead to buy-in for real modernization.

But, by not touching your legacy systems you can end up creating a false sense of the effort needed to modernize.

You also miss out on uncovering key challenges, and validating that your new and old worlds can co-exist as you modernize.

Getting decisions like this right can make or break the whole initiative.

2/2

nick_tune, to random
@nick_tune@hachyderm.io avatar

Zuck announcing Threads and Mastodon interop is imminent

nick_tune, to random
@nick_tune@hachyderm.io avatar

I've just published a new article: Beyond Problem and Solution Space: Better models for modern product development

I find the terms problem and solution space confusing so I've summarized the works of Indi Young, Marty Cagan, Teresa Torres, and John Cutler which can help to address this problem.

Please let me know if I've misconstrued, misunderstood or inaccurately represented any ideas.

https://medium.com/nick-tune-tech-strategy-blog/beyond-problem-and-solution-space-better-models-for-modern-product-development-4ad3d5d5cdc4

nick_tune, to random
@nick_tune@hachyderm.io avatar

nick_tune, to random
@nick_tune@hachyderm.io avatar

One of the most fascinating things about software architecture is how choices in the past can have such a strong influence on the system for years to come.

You might make a decision that seems trivial at the time, but new features get layered on top of your design's assumptions.

These bakediin constraints limit how you can evolve the system,...

1/2

#softwareArchitecture #architectureModernization #ddd #domainDrivenDesign #ddDesign

nick_tune, to programming
@nick_tune@hachyderm.io avatar

One thing I liked about Scala was the ability to work fairly seamlessly with possible nulls using map, flatMap, orElse, getOrElse and so on....

My first impressions are that it's not so smooth in typescript out of the box to work with optionals.

Hopefully I'm just missing a few key concepts.

nick_tune, to random
@nick_tune@hachyderm.io avatar

What do I think was missing from the book Architecture Modernization? Great question from @eduardodasilva yesterday as part of an interview that will be published soon.

While designing a great architecture, prioritizing areas with the most business impact, and having an effective migration plan are essential to get right, so are all of the small things that happen on a day to day basis.

1/3

#architectureModernization

nick_tune,
@nick_tune@hachyderm.io avatar

This is covered in the book, notably the chapter on AMETs. But it's a great topic that I would love to have covered in much more detail - delivery management, change management, leadership etc. in the context of architecture modernization.

It will probably be the focus of future blog posts and talks (I'm definitely not writing any new books). I appreciate any recommendations for existing resources on the topic

https://esilva.net/articles/architecture-modernization-enabling-team

3/3

#architectureModernization

nick_tune, to random
@nick_tune@hachyderm.io avatar

It was wonderful watching @yellowbrickc facilitate a DDD/architecture workshop yesterday at PayFit France.

She demonstrated one of the most effective, and simplest, techniques to perfection "Talk me through a concrete use case".

She quickly helped a group map out the details and then make a decision about their architecture. It was really impressive.

If you want to become a good facilitator then I recommend getting good at this skill.

1/2

#ddd #ddDesign #softwareArchitecture

nick_tune,
@nick_tune@hachyderm.io avatar

.....helping business and technology people map out specific scenarios.

This technique also forms a key part of Eric Evans Model Exploration Whirlpool which is also highly recommended.

https://www.domainlanguage.com/ddd/whirlpool/

2/2

nick_tune, to random
@nick_tune@hachyderm.io avatar

I just went through the slides for one of my talks from 2017.

I assume that all of my old content from years ago is terrible and usually I'm ashamed to even look.

But today I opened the slide deck of what I consider to be my worst ever talk. I was prepared for a cringe fest.

But it wasn't actually as bad as I feared.

Lesson learned: I don't know. Just thought I’d share this.

nick_tune,
@nick_tune@hachyderm.io avatar

@matthewskelton it definitely is, but there are a few things that I had also forgotten along the way which could still be relevant today.

For example:

matthewskelton, (edited ) to devops
@matthewskelton@mastodon.social avatar

Prediction: at least 90% of orgs doing "cloud repatriation" (aka "how hard can it be to run some infrastructure, ffs?") are going to get a nasty shock when they re-discover all the reasons that people moved to cloud in the first place: running infrastructure at even modest scale is absolutely not trivial.

Combine that with re-discovering all the basics of hand-offs, on-call, and other DevOps 101 stuff, it's going to a wild fscking ride 🏇

nick_tune,
@nick_tune@hachyderm.io avatar

@matthewskelton Bring back the good old days of managing operating systems with regularly security patch updates.

What do you mean the developers aren't delivering anything this sprint because they have been dumped with a bunch of infrastructure tasks?

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