Well I have a tentative outline of the Event Sourcing book. It may look familiar to those who have taken my class.
How closely I stick to it ¯\_(ツ)_/¯ when writing things sometimes change. Thoughts?
It has been very weird having calls about possible job opportunities. I have literally been told some of the most wild things.
That I do not understand cqrs/event sourcing was definitely the most funny :-D "could you look up for me quickly who named 'cqrs'"?
There are no "full stack developers". Its a silly buzzword. Sadly working on kernel issues, a real time networked embedded system, or implementing a TCP stack is a different world than building an advertising website in PHP on MySQL.
If this word had a more direct translation to English I think we would need a software book titled it!
Verschlimmbessern : to make something worse in an honest but failed attempt to improve it
@ZeForener
I have a weird one for you here. Writing provably correct code. EG: using theorem proving ... formal verification of a state machine etc etc.
This is something you are highly unlikely to learn being self-taught.
I am slowly losing my grip on reality.
I was proactively offered a Jr level position on a team working on an event sourced system.
I thought I must be somewhere modestly above a Jr Developer role?! But I also did not realize that event sourcing was invented two years ago.
I emailed the author of the quote asking for permission to use it to open my book with. It is perfect.
"The universe is made of events not objects.", Carlo Rovelli
Its getting into evening on a Saturday night. Time to reflect on the week.
What was your most ridiculous interaction?
I was told I don't know what CQRS is .. by a non-technical recruiter.