Angus - How To Code It

Part 4 of my deep dive into hexagonal architecture in Rust is live! 🦀 Covering: 🤔 Trade-offs of hexagonal architecture ⛔️ Common pitfalls to avoid 📈 Adopting hexagonal architecture at every growth stage Read & subscribe for updates: howtocodeit.com/articles/maste… #Rust #RustLang

@AstraKernel Thanks for sharing! I'm glad you enjoyed it

🦀 Wonderful talk by Angus Morrison on "How Rust is powering next generation Space Mission simulators" youtu.be/zMxlVEKRonk

My RustConf talk on developing an open-source European Space Agency mission simulator is now live! 🚀 Learn how Rust models 13 billion years with femtosecond precision across 7 astronomical time scales. 🦀 howtocodeit.com/articles/rust-… @Rust_Foundation #Rust #RustLang

@nnrm_04 I know, I know! It’s been crazy over here with RustConf, etc. I’m planning to blast out a site upgrade this weekend to better handle rich, multi-part articles like Hex Arch has turned into, then I can write freely. Thanks for bearing with me!

@how_to_code_it bro when is part 4 coming out 😭

Hexagonal architecture is nearly always a good idea. Hexagonal architecture *in Rust*? That's another level of stability, scalability and test coverage 🚀 Here's my guide to writing ironclad, highly maintainable Rust applications: howtocodeit.com/articles/maste… #rust #rustlang

@SebasDev1 @alicelovescode It’s in the works! Between RustConf, a new job and some much-needed CMS upgrades, I’ve been strapped for time. My RustConf talk will probably be the next thing to be published, along with the final parts of the hexagonal and error handling articles.

@how_to_code_it @alicelovescode When another article? Such good content 🚀

Does anybody know what blog software i'd need to use to get the numerical reference tags inside code blocks like they have in this article? what are you using @how_to_code_it? howtocodeit.com/articles/ultim…

Looking for the path to writing exceptional Rust? Step right this way, towards my macro_rules! guide. 🧙 I’m demystifying three macros that underpin 100,000s of Rust applications 👇. howtocodeit.com/articles/writi… #rust #rustlang

@tomjohnson3 Hey Thomas! I think you’ll find part 4 (out next week) really helpful. It’ll address the relationship between hex arch and microservices in some detail - there’s a lot of overlap and transferrable technique. Thrilled to hear you’re finding the guides useful!

@how_to_code_it ...perhaps there's something from hexagonal architectures that we could get inspiration from as we design this feature? [3/3]

Launching an MVP with “whatever architecture works, we'll refactor later” always ends with “we have an early-stage product that's already legacy”.

@alexelcu Is this equivalent to saying "don't ruin your presentation with fonts that aren't Times New Roman"? If you don't have an eye for design your presentation will look bad wherever you source your images.

@hexwanderer I'm struggling to think of any use case for this? If you could declare `let x: impl SomeTrait`, this would get compiled to `let x: YourImplementation`, so you might as well just write `let x: YourImplementation`.

@how_to_code_it Thanks for your reply! Sometimes I want to just do it at the top level, there isn’t an easier way to do it without declaring a function?

@how_to_code_it hi angus! i have been trying to follow your guide on hexagonal arch, but i frequently run into situations where I want to declare some variable as an impl of a trait, but am repeatedly told that the trait is not object safe. Only way to solve is to pass into fn?

@cereal_learner This is very generous feedback ❤️ thank you for motivating me to continue!

@how_to_code_it Sir, can you kindly take my 🫡 your blog posts on hexagonal architecture are mind-blowing. What I really appreciate is it's not just words-wisdom but code-wisdom. Please keep them coming :-)

@k_pendergrast What other construction do you think would achieve the same tone? 🤔 The intended reading is clear, even if we do have to say a few Hail Marys afterwards.

@hexwanderer If you call `fn f(x: impl SomeTrait)` with `StructThatImplsSomeTrait`, it’s compiled to `fn f(x: StructThatImplsSomeTrait)`. This happens for every distinct type that impls `SomeTrait` – multiple copies of the function are compiled (the technical term is monomorphization). [5/5]

@hexwanderer To do it generically instead, assign a variable of the concrete type that implements `SomeTrait`, and pass it to functions or structs bounded by `impl SomeTrait`. Be aware: `impl` doesn’t indicate any dynamic dispatch...[4/5]

"It's all gone wrong!" How To Code It issue #4 is live in the archives, featuring a definitive guide to error handling, a hex arch showdown, @matthiasendler's guide to adopting #rust, and @timClicks' Rust Forge 🦀🔨 Read and subscribe here: howtocodeit.com/newsletter #rustlang

@kiyov09 Anyone would think I was bitter after years of working in dynamic languages…

@how_to_code_it and funny... x.com/kiyov09/status…

Just learned about @how_to_code_it . Awesome resource dude! 👏👏👏