panic()

Software Engineer, intersted in distrubted systems, software architecture and systems performance.

[Ben Dicken @BenjDicken]

Little software design decisions have a big impact on performance.

Array-of-Structs vs Struct-of-Arrays is a neat example. This "small" difference for in-memory state organization drastically changes cache utilization and hit rate. In turn, you can get order-of-magnitude performance differences.

It's similar to the row-oriented vs column-oriented layouts for data systems. Which to choose depends on expected access patterns (OLTP vs OLAP).

Farad's article on this is quick read and easy to follow. Link below.

[Danz 🇵🇹🏴󠁧󠁢󠁥󠁮󠁧󠁿🇧🇷🏴󠁧󠁢󠁳󠁣󠁴󠁿🇨🇩🇸🇳 @zinownh]

black hair so beautiful man but african parents will always find a reason to demonize it

[panic() @fmt_sprintf]

@tetsuoai Can you share direct link to this video please ?

[panic() @fmt_sprintf]

The crazy thing is that most company’s will place you in a week long scrum training and end up not practicing it. Why waste peoples time with things that won’t be religiously adhered to ? 😅

[Bojan Tunguz @tunguz]

Do you guys remember "Scrum Masters"? What was that all about???

[panic() @fmt_sprintf]

Layered architecture is a clear example of useless decoupling.

[panic() @fmt_sprintf]

Coupling is antithetical to change, because it links unrelated things together, things that must change in parallel.

[panic() @fmt_sprintf]

The lack of high cohesiveness in layered architecture is counter productive and counter intuitive. Jumping through many files just to work on a small feature in layered architecture can make you go crazy.

[Phuong Le @func25]

@SoloCr33d Yes: https://t.co/9agOiSoMci. Feel free to reach out if you haven't received the latest version.

[random guy on the internet @KharayKrayKray]

“People are shipping fast with AI, there’s no point in learning how to write code anymore” ~ A lazy goat.

[panic() @fmt_sprintf]

@tanujDE3180 He is a terrible engineer. Fixing a data edge case by hand for 3 years without coming up with an appropriate fix or documenting the process ?. Engineers who build knowledge silos are terrible.

[panic() @fmt_sprintf]

@EngPolymathic An interesting book that also goes into detail on this topic and more: Release It, by Michael Nygard

[panic() @fmt_sprintf]

@malliktwts This is actually a very interesting book with really good examples and it’s also super hands-on, sadly the examples are in Java 😅

[panic() @fmt_sprintf]

Switching my MX Linux tiling window manager to Hyprland is the best thing I have done for productivity boost when using MX Linux

[panic() @fmt_sprintf]

Finally done with this master piece. One of the best books around indexes I have gone through so far.

[Distributed Bytes @DistribSystems]

Top Five Scalability Patterns
https://t.co/BOzmjqWbSM

[panic() @fmt_sprintf]

Mastering the ability to read profiling data and trace the performance bottlenecks it reveals back to the code is an invaluable engineering skill.

[panic() @fmt_sprintf]

@eatonphil 2nd edition? This is probably an opportunity for me to read this book again. Is the second edition good with more new stuff ?

[panic() @fmt_sprintf]

@Akintola_steve This is a very generic question. What kind of logs? Write ahead logs? Commit Logs? OpLog? Replication Logs? Or Logs as we know from observability perspective?.

[panic() @fmt_sprintf]

all that is needed is the right set of mcp tools integrated to all the platforms (notion, GitHub, confluence, Jira e.t.c) your company uses and onboarding will be easy. There is no architectural diagram of the system? AI can generate one (simple or complex)

[panic() @fmt_sprintf]

One of the things I so much love about AI coding tool is not how fast it can help me iterate on an idea or a task but how easy it helps to understand an unfamiliar system.

The era of struggling to onboard on large and complex system will slowly fade away,
🧵