Romain Asnar

Crafting software, Pocket Monsters collector, 改善

[Mathis Hammel-Brylinski @MathisHammel]

🧶THREAD - Un programme de 15 lignes de code Python arrive à rivaliser avec les meilleures intelligences artificielles !

Cette drôle de découverte vient d'être publiée par une équipe de chercheurs canadiens, et risque de bouleverser le monde du Machine Learning.

Explications ⤵️

[Uncle Bob Martin @unclebobmartin]

@OLoterio Properly applied, MVVM is really MVC mixed with The Humble Object Pattern. I suppose you could call it Humble MVC.

[Romain Asnar @romsi94]

Best description of what the VIPER architecture has turned out.

[Sarun W. @sarunw]

Explaining a codebase that uses VIPER.

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

#NoCodeReview
#NoPullRequests

Mob/Ensemble program instead. Yields much better results without the bottlenecks and waits.

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Code-review-as-inspection is ineffective. Don't just inspect, pair or mob with the person who wrote the code and fix the problems. Right then. No delay.

Ofc, if you had done that when the code was fist written, you wouldn't need the review. 😄 Quality cannot be inspected in.

[Uncle Bob Martin @unclebobmartin]

You WILL make architectural errors early on in a project. Every time you realize such a mistake but don’t correct it, you move one step closer to hell.

[Romain Asnar @romsi94]

Can we please do that?

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

I'm no Scrum guy, but ISTM you pick a Sprint Goal and then do whatever works to move you towards that goal. What you do doesn't matter much. Given that, I don't really understand all the obsession surrounding estimating stories. Why bother? Pick something valuable and work on it.

[Romain Asnar @romsi94]

@everton_dev @klmitchell212 @nicklockwood Apply SOLID principles instead. Clean Swift is based on Clean architecture with a rigid approach. You don’t need 1 View controller, 1 presenter and 1 interactor all the time. I found very useful to read Clean Architecture book by Uncle Bob to avoid these boilerplates.

[Romain Asnar @romsi94]

@everton_dev Gather together those things that change for the same reason, and separate those things that change for different reasons. Make sure your app is testable (dependency inversion) and your tests are fast enough (< 5sec). Don’t follow one particular pattern, be pragmatic.

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Both stakeholder-driven development (SDD?) and CEO-driven development (CDD?) are anti-patterns. It's best if they focus on strategy, not tactics, IMO.

[Romain Asnar @romsi94]

@MaisterJuli @pepibumur 🤣 I feel the same. It reminds me that at my university, you had to use eMacs without syntax coloring the first month.

[Romain Asnar @romsi94]

@ProJavaOrlovsky @unclebobmartin It’s not 100% functional but SwiftUI enables to make complex UI with a functional programming approach.

[Romain Asnar @romsi94]

@k_ebrahem_ @AmiraultTony Let’s do a part 2 and go more in dept. For those who are interested about clean architecture, we will release the conversation in video soon.

[Simon Sinek @simonsinek]

Intelligence uses what is known to solve problems.

Creativity uses what is unknown to discover possibilities.

[Romain Asnar @romsi94]

@unclebobmartin @mortezaadi Removing capabilities from the programmer and imposing some kind of extra discipline.

[Suhail @Suhail]

Back to learning about ASICs. I will post learnings and progress here as I go. This is all just for fun to help improve my first principles understanding of hardware to help with @MightyApp down the road.

[Romain Asnar @romsi94]

@mortezaadi @unclebobmartin I thought it was about paradigm and not language.

[Romain Asnar @romsi94]

And not draw systematically boundaries between each classes.

[Uncle Bob Martin @unclebobmartin]

The primary strategy of architecture is the drawing of hard boundaries between high level policy and low level detail such that the high level policy is entirely ignorant of the low level detail.

[Uncle Bob Martin @unclebobmartin]

The purpose of architecture is the minimization of manpower for development, deployment, and maintenance.

[Romain Asnar @romsi94]

It is clear to me that test last is a bad idea compare to test first.

Starting with a failing test prove the absence of the requirements.

Adding your tests after your production code can't prove the presence of the requirements. Unless you change your code to make test fails.