Phill

Pessoa desenvolvedora de software.👨🏾‍💻

[Yegor Bugayenko @yegor256]

"Static methods are as big a mistake in OOP languages as NULL, or maybe even bigger. Static methods should never have been present in Java and all the other OOP languages in the first place, but they are there. We shouldn't have to know about such things as static keywords in Java, but alas, we have them. I don't know who exactly authored them in OOP, but they are pure evil. The static methods, not the authors. I hope." — Elegant Objects, Volume 1 (2016)

[Chef Dan Galhardo @chefdangalhardo]

Caralho.

VSR HABLOU AQUI HEIN?

[Dr Milan Milanović @milan_milanovic]

𝗘𝘃𝗲𝗿𝘆 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗹𝗲𝗮𝗿𝗻𝘀 𝘁𝗼 𝗱𝗲𝗯𝘂𝗴 𝗰𝗼𝗱𝗲, 𝗯𝘂𝘁 𝗮𝗹𝗺𝗼𝘀𝘁 𝗻𝗼 𝗼𝗻𝗲 𝗸𝗻𝗼𝘄𝘀 𝗵𝗼𝘄 𝘁𝗼 𝗱𝗲𝗯𝘂𝗴 𝘁𝗵𝗲𝗺𝘀𝗲𝗹𝘃𝗲𝘀

There is one trait every superintelligent person has: metacognition. It's just noticing your own thinking as it happens. You catch the thought instead of getting carried off by it.

The time flows, and you just go with it. Sometimes, you get defensive in a code review before the comment has even landed. Sometimes you're three hours into a bug, and something in you refuses to walk away from it. Someone floats an idea in a meeting, and you've shot it down before they finish the sentence.

None of that is a decision. It's a reaction that fired before you looked at it.

The whole skill is catching it while it's still firing. The second you think "wait, why did I react like that?", something shifts. You're not running the reaction anymore. You're watching it run.

That little bit of distance is everything you get to work with. It's the space between doing the thing on reflex and actually choosing to do it.

I've been building software and leading teams for 20+ years. The people who kept growing weren't the most talented ones. They were the ones who could catch their own patterns in the act, which is the only reason they could change them.

You do this for systems every day. Try turning it on yourself.

One good exercise is to practice meditation, 5-10 minutes every day. This can significantly improve your metacognitive skills. Also, try to have weekly reflection sessions. I do this every Friday at 17h, where I try to understand what I did during the week and what I can improve.

#SoftwareEngineering #Leadership #CareerGrowth #TechWorldWithMilan

[htmx.org / CEO of We Are So Back (same thing) @htmx_org]

https://t.co/a6kTxZtpf3

[Joran Dirk Greef @jorandirkgreef]

Software is pure “thought stuff”. One person can write code and billions can run it. If anything, our linear time produces exponential value.

Therefore, I’ve never personally believed that developer time is expensive, that we have a “typing” problem. Or that English is somehow a better way to express code than a language as explicit as Zig.

Granted, there’s tons of (non valuable) bespoke software that LLMs can now create. But the valuable thought stuff? Great systems coders are becoming more valuable than ever.

In the land of the blind, the one eyed man is king.

[Yegor Bugayenko @yegor256]

The daily standup isn't a status meeting, it's a confession booth. Lining engineers up to recite yesterday, justify today, surrender tomorrow — that isn't management. It's the ritual an insecure manager performs to disguise the absence of a real communication channel.

[Kit Langton @kitlangton]

An obvious tip for software design with or without AI that's nonetheless easy to get wrong:

Purge all foreknowledge of implementation and edge case from your mind and imagine the platonic user-land API. Think first in terms of high-level intentions.

Then see if it's achievable.

[Mo @atmoio]

The Unethical Guide to Surviving AI Layoffs

[Phill @phcostabh]

@ryanvogel @evilrabbit_ @kitlangton @jlongster @opencode 👌🏾

[Yegor Bugayenko @yegor256]

Most developers think productivity comes from writing more code faster. In reality, productivity comes from writing less code with fewer consequences. Every line you add increases maintenance, complexity, and future risk. The best engineers are not the fastest writers, but the most selective ones.

[Mo @atmoio]

Zuck is officially the most evil man in AI

[Yegor Bugayenko @yegor256]

Speed without structure doesn’t scale. I mean, what works for a team of five breaks at fifty without clear ownership and boundaries, and fast decisions turn into inconsistent ones. The challenge is building systems that remain coherent as you grow.

[Yegor Bugayenko @yegor256]

Refactoring is frequently postponed because it doesn’t deliver immediate business value. However, every postponed refactoring becomes a hidden cost in the system. Complexity accumulates silently, until simple changes require disproportionate effort. What is delayed today becomes a constraint tomorrow.

[siddharth ☻ @siddharthkp]

staff/senior engineer thought:

[The Other Alistair @TotherAlistair]

I've tried for years to draw layers vs hexagon, this is the best I've been able to manage on my side:

[Yegor Bugayenko @yegor256]

Most teams believe that speed comes from moving fast and iterating quickly. But speed in software is cumulative: decisions made early either accelerate or slow down everything that follows. A poorly designed system doesn’t become fast with time, it only becomes expensive.

[Sebastien-console_buche 🪵 @Console_buche]

Ce site est un bijou. Une raison de plus d'apprendre Effect. https://t.co/MmUIxKjaZf

[Ben Dicken @BenjDicken]

Database table size impacts performance in more ways than one:

a) B-tree depth. Using 8k pages and a 16b uuid:
1 level = ~370 rows
2 levels = ~138k rows
3 levels = ~50m rows
4 levels = ~20b rows

The lookup cost on a table with 100k rows is not the same as one with 1b rows. This can apply both to the table itself (MySQL cluster index) as well as the indexes. Sometimes a single query requires many of them.

b) Small table → fits in RAM → fast reads. The larger the table, the more likely to read from disk plus churn the cache.

c) # of indexes. Each adds maintenance overhead for insertions, and for Postgres vacuum overhead as well.

Keep an eye on this! It's useful to take regular stock of your tables + indexes. Clean bloat. Remove unused indexes. Partition if needed.

[LINUXtips @LINUXtipsBR]

eu sei que você tava esperando por esse momento! vai ter live sobre system design com o @fidelissauro no canal.
vamos entender arquitetura de sistemas, falar sobre carreira, o livro do Matheus e muito mais. então já deixa salvo na agenda dia 14 a 16 às 19h no canal, te espero lá

[Téo Calvo @teomewhy]

Obrigado pela confiança galera. Somos +50.000 no YouTube