Published

I was working in a new project that had a microservice architecture at TomTom since January. I was enrolled in the Course_ Cloud Native Entrepreneur - Patrick Lee Scott since December. In this course he teaches about cloud native (microservices and devops) and entrepreneurship. I was thinking about solving my problem of better highlighting / note-taking while reading. I enrolled in the Course_ Advanced Distributed System Design - Udi Dahan where I picked up the idea that deciding which things are deployed on the same machine can be decided later Oh and a year I learned CQRS and eventsourcing, mainly from Greg Young’s materials...

(https://m.youtube.com/watch?v=RyTQ5-SQYTo) Juniors only need to be good at their job. They get training to do a good job. People get promoted when they are good When they are promoted they stop being responsible for the work they are responsible for the people that are responsible for the work They don’t get little or no training on how to lead people. They micro-manage because they know how to do the job better, that’s why they got the promotion....

Model: Grouping tests (src: Video_ Structure and Interpretation of Test Cases - Kevlin Henney)

Naming tests snake case is more readable than camel case (when > 30 characters, which tests usually are) “should” is like training wheels name tests as propositions name test as Method_input_result (src: Video_ Structure and Interpretation of Test Cases - Kevlin Henney)

(https://www.youtube.com/watch?v=tWn8RA_DEic) Model_ naming tests snake case is more readable than camel case (when > 30 characters, which tests usually are) “should” is like training wheels name tests as propositions name test as Method_input_result Model_ tests must clearly express required functionality Article: Model_ Grouping tests

(https://www.youtube.com/watch?v=tMW08JkFrBA)

Continous Delivery Sounds Great - Jez Humble ( https://www.youtube.com/watch?v=SjVV3xuYKJs ) Model: software = design + delivery design= unpredictable delivery = predictable lean 6 sigma doesn’t fit on software ; because software is 2 things 6 sigma tries to get all variability out of a system great for delivery, not great for design xp lean software development unix inventor of unix pipe (2) = microservices (3) = deliver early & often (4) = automate, tool based...

March, black swan picture taken Call to action: work & school from home by the end of the week [ ] Article: Why your company isn’t profiting from remote productivity create connection between efforts and customer value Hawthorne effect: measuring something ups the numbers for a while because of the attention proxies -> maybe / maybe not? metrics between customer and team direct connection -> see lack of satisfaction...

https://martinfowler.com/articles/agileFluency.html Lens: Model_ estimates in Agile Fluency Lens: Model_ team composition in Agile Fluency

I am looking for a job 1. in a growth company (not a company in a declining market) 2. in a team we can grow into a high-performing team 3. where I can apply technical excellence (continuous delivery, devops, agile) 4. practice & learn writing adaptable software (aka ‘agile code’ or ‘maintainable code’) (1) growth company, is what most recruiters know (2) team culture, is what some recruiters partially know (3) technical excellence, is what few if any recruiter knows (4) adaptable code, is what no recruiter knows...