The success that
@EventModeling
and
#eventsourcing
enable is incredible. Please feel free to share this with others if they are not convinced that they can improve their projects this way. Thank you to Jason, Fran and others at
@ShedSuite
for an incredible journey together!
NEVER use
🚫 "git reset --hard".
If you want to clean out your modifications, ALWAYS use
✅️ "git stash -u"
I've been saying this for over a decade. It sucks to see people suffer. Git reset is the only common command that does not have the usual git safety net of the reflog.
Everyone is getting help from
#AI
. You are not getting ahead by just adopting it. Did email make one company better than another? No. Your core competencies need to be ahead of everyone else - just like always. So if you think you are going to automate your system better than
I have >100k on
@StackOverflow
for >1000
#git
answers and I'm one of 3 people with the gold badge for version control.
I still look things up on Google.
Don't tolerate people that use this knowledge to make you feel like an imposter.
Also: 'curl '
Don’t let people make you feel bad for looking out obscure Unix commands, weird git commands, or need help rebasing stuff that you don’t use every day. We all look stuff up.
You can tell them I said so. Send them here. 30 years, still looking up stuff every day.
I did a podcast episode focused on
#programming
and running your own company. If you ever wanted to get off the employee arrangement in IT and were considering going out on your own, I hope this inspires you!
#software
#development
#journey
Meeting the man more important to computing than Gates & Jobs combined is a defining moment in my life. Thank you,
@Linus__Torvalds
for talking to me about our passion for
#git
and the next chapters in that story like
#OSSummit
@linuxfoundation
#AI
is revolutionizing the way we work, making us faster and more efficient. However, if we continue to use outdated or ineffective approaches, we risk falling behind by entrenching ourselves as experts in irrelevant practices - AI will make us good blacksmiths in a world that's
It's been 8 years since I started
@adaptechgroup
. We're about to open another office in Quebec! What a great feeling being able to help so many clients and free them from the dysfunction of the software industry. They are ready for an incredible future!
Our clients:
- don't
7 years of doing just
#EventSourcing
for 100s of projects is enough to convince me that it's the best default approach to any system automaton. The traditional approach should be the exception.
@jamonholmgren
I had this really sick feeling in my stomach. I didn't know why. I felt like I was really needed somewhere to help avert a disaster but couldn't get there in time.
Do event sourcing by default. Make short streams. Don't require replaying all events to regenerate your projections. There is no better default way to write systems.
Monolithic ≠ spaghetti 🍝!
Modular code transcends deployment models.
#EventDriven
approaches make this even easier to realize. Events have been too tightly associated with distributed systems via microservices. You should be doing the same thing within services themselves.
Happy 53rd Birthday to my hero/role model Linus Torvalds - rescued the entire computer industry from monopolies. He's the single person responsible for me wanting to remain to fight for open source and open platforms.
Today I was privileged to help save someone's life. No one was stopping to help this older gentleman who suffered a heart attack. Not many people were in the area at all and people would pass by knowing that it was unlikely that someone else would happen to go to this spot. It
Argue that events (or facts) aren't part of most systems. They are. They are part of all systems humans use to manipulate information. If you don't have events as a default core abstraction, you already set yourself back right at the start.
Just because there is 50 years of
Wow! Finally bumped into
@ElectroBOOMGuy
, Mehdi! One of the best YouTube creators out there. If you haven't seen Mehdi get zapped, you haven't experienced the full joy of the internet yet 😄
I’m only speaking from my personal experience, no data, no stats. 100.00% of the time a person has voiced a criticism of TDD, they go on to describe and criticize something that isn’t TDD.
I'm SO glad I didn't need to be part of any stand ups, sprint planning sessions or retrospectives for years now. I don't know how anyone puts up with that crap.
Just finished
@Zimareff
's
#CQRS
/
#EventSourcing
book and there's nothing better out there. Don't let the
#DDDesign
title fool you. An enthusiastic 5 stars and review coming up on Amazon!
No matter what language you program in, THIS IS A MUST HAVE!
🥳🎊 Today marks the 7th anniversary of
@adaptechgroup
. It's a dedication to only developing using
#eventsourcing
. We invented
@EventModeling
along the way which now helps 100s or 1000s of organizations globally in their efforts to adopt
#eventdriven
systems automation. 🥳🎊
Would anyone be interested in a public discussion about
#TDD
,
@EventModeling
and other related topics with me and
@davefarley77
? There definitely good reasons against TDD and they have been dismissed without looking into them. Also, there are huge difference between
Just uploaded: Introduction to
#CQRS
and
#eventsourcing
with
@gregyoung
that was recorded at the meetup yesterday. For those that were not able to attend, you can see it here.
Linux is best for dev. The Macbook is just hype and status branding with a lot of problems. Sad to see so many programmers waste time and money on Apple.
The sunsetting of agile has begun. I'm seeing realizations like this in many places:
"I have almost never seen kanban done properly. Agile was a trojan horse that promised quality but delivered just empty ceremonies, more waste, and ultimately more
command-and-control."
The biggest scam that agile pulls is the idea that the solutions will be kept flexible as they grow. Nothing could be further from the truth. Subjective design through abstraction level and refactoring by many gets a heterogeneous coupling soup. Those unit tests are cement.
Do kangaroos and koalas know how to do
@EventModeling
? They will soon! Come take the workshop in Sydney or Melbourne to learn to design your systems collaboratively and quickly.
Nov 29th, Melbourne:
Dec 6th, Sydney:
🐨🦘
@ThePrimeagen
Rebase is to be used rarely. It's not a skill issue. It's mental masturbation for developers. A merge+reset workflow allows accountability of what and when changes happened. Rebasing adds the risk of applying changes into a state of code it was not developed in with consequences.
It's come to the point that if a game doesn't run on SteamOS, I'm not interested in it.
I've had it with the rip-off schemes of other platforms on console, hand-held and PC. I'll put money behind something that runs on an open platform in the best usable form factor.
#steamdeck
@PierreJoye
@davefarley77
1.
#TDD
requires refactoring continuously with no visible end in sight for when that will stop. So each iteration, a developer makes a solution with quality oversight at a minimum knowing in the back of their head that they will have that code rewritten. This is a major issue
#TDD
is a bad way to design most software. I'm throwing out the concepts I clung onto for too long.
#UnitTests
are still needed and should be written first, but to design software by refactoring around a growing number of tests will grind you to a halt. 20 years to realize this.
You know how to get rid of imposter syndrome? Get rid of needless names for concepts you can use plain English for. Drop DDD, hexagonal architecture, agile, and everything else. It's doing more harm than good. You better have damn good excuse to introduce a new term.
#EventSourcing
is a game changer. Imagine capturing behaviour as data with 100% accuracy. We've had affordable storage long enough for this to be the default. _All_data_ in your application has the superior option to be temporal and remember everything.
Rob Pike 1989:
"Data
Why
#EventModeling
and
#EventSourcing
succeed better than any other approaches:
Event Modeling is role-agnostic.
Event Sourcing is tech-agnostic.
No matter what your job title, you can understand the solution and you can contribute to the solution. No matter what tech stack
I'm working on a prompt to give you an
#EventModeling
engineer. You can play with it here if you are on GTP4:
I'm hoping you can just feed transcripts of your brain storming sessions and it will give you an event model to start with.
I love my work now.
#ChatGPT
brushes away the garbage of swimming through new JS frameworks, etc.
#Linux
brushes away the proprietary garbage from the other OSes.
#EventModeling
brushes away all the obfuscation in coordinating and lack of design.
#EventSourcing
brushes away
DRY ("Don't Repeat Yourself") is for _knowledge_, not code -
@tjaskula
Great insight about
#dddesign
and a huge parallel and better way to say what we've been trying to say in
@EventModeling
And great application of the idea from
@VaughnVernon
this morning!
Huge shout out to
@jetbrains
for all the hard work over the years. I hope the tech community stands up to the BS shade thrown at them in their ill-written article.
While I actually like writing in OO languages, the mindset about state in their communities makes me cringe. You can write functional code in these languages from the perspective of immutable state - if you don't, you get an unmanageable mess that ends projects as death marches.
I feel sorry for people that tied up their IT careers to promoting TDD or agile - and some are incredibly smart. What a waste to push that much energy and talent to what has surpassed any reasonable point of diminishing returns.
Nobody gives a sh*t about the value of office buildings. One silver lining from COVID. Some of the worst people I've dealt with in business were in commercial real-estate. This is like watching parasites being burned off with a hot knife.
Remote work risks wiping $800 billion from the value of office buildings in major cities worldwide by 2030 as the post-pandemic trend pushes up office vacancy rates and drives down rents, according to a new report
Renamed the YouTube channel. It's now the "Event-Driven Information Systems" channel.
Here's the 3rd installment of
@gregyoung
's Intro to
#CQRS
/
#eventsourcing
talk from the Meetup earlier this week.
I see IoC, DI and mocking still being discussed and wrestled with. I'm glad I don't do this anymore. So many problems simply don't exist. If you're trying to continuously improve something that you don't need, you'll run in circles forever.