8 Photos and videos
How I align tech initiatives to business goals:
open.substack.com/pub/itzy/p…
45
CTO Logic is booting up ...
I write about how to operate professionally at the intersection of software engineering, tech management, leadership, and business.
open.substack.com/pub/itzy/p…
1
50
However, accessing some deeper paths still works, e.g. linkedin.com/feed/
2
41
C-suite people: Your CTO is probably lying to you.
OK, she's not actually lying, but she does need to represent the truth in a way you can handle.
Otherwise it would be too difficult for you to trust the development process.
world.hey.com/itzy/the-inver…
#CTO #CEO #founders
43
.@agazdecki
Is @microacquire friendly to foreign acquirers who don’t want to end up owning a US corporation?
Do you have a standard solution for this?
E.g. transfer ownership of the *product* and related intellectual property, rather than sell the *company* that owns it?
3
1
9
1200 microservices just to render the Twitter timeline. Or is it "just" 200?
Microservices are a double-edged sword.
Like everything else in engineering, they are a trade-off.
If anyone can decide on a whim to create a new microservice, you’re doing it wrong.
ALT Public argument about the number of microservices required to render a Twitter timeline. Is it 1200 or 200?
1
Creating a new service must be a carefully considered decision.
The more trivial the functionality, the more it should be combined into a related pre-existing service.
Done right, you end up with “macroservices,” which each handle a complete functional or business domain.
1
Welcome to the Popular Front for the Revival of Monoliths!
Personally, I think we need to popularise what you might call "macroservices" rather than complete monoliths.
Part of today will be turning off the “microservices” bloatware. Less than 20% are actually needed for Twitter to work!
1
Many software engineers don't realise:
❌ We are NOT paid to write code.
✅ We're paid to SOLVE BUSINESS PROBLEMS.
Ask until you understand the business problem behind what you’re working on.
You'll make better decisions & possibly be able to offer alternative solutions.
1
3
Summary:
1. Identify adventures early & discuss
2. Cost-effective & appropriate for business problem
3. Direct costs, current & future
4. Indirect costs, esp. complexity
5. Degree of lock-in
Have pity on your future self.
Keep things as simple as they can possibly be.
1
I hope you've found this thread enlightening.
Follow me @itzysabo for more.
Like/Retweet the first tweet below to spread the message:
x.com/itzysabo/status/158522…
Do you go on engineering adventures & expeditions?
“Shiny object syndrome” can cause engineers to skew solutions towards the less optimal.
This is how to stay at the bleeding edge, but in a realistic and measured way: →