le duc quang

[le duc quang @ducquang98]

@systemdesignone Leetcode

[Bernie Sanders @BernieSanders]

Totally insane. First, a gym full of people. Then an overflow crowd. Then an overflow-overflow crowd, and an overflow-overflow-overflow crowd.

More than 9,000 people came out in Warren, MI to say NO to oligarchy & NO cuts to Social Security, Medicaid, and VA programs.

[Santiago @svpino]

Does anyone go to StackOverflow anymore?

I'm trying to remember, and I think I visited the site once over the last few weeks. It was probably muscle memory.

I only use Google when I want to find a website, but I never use it for answers anymore. That's what Claude and ChatGPT are for.

For coding, Cursor and Copilot do a much better job than StackOverflow ever did.

I just don't know how they can stay relevant any longer.

StackOverflow is a dinosaur going extinct right before our eyes.

[Ryan Peterman @ryanlpeterman]

If you want to become a better software engineer, read these blogs from top companies (Meta, Uber, Stripe, OpenAI, Netflix)

I spent hours curating my top 22 from a list of over 681 different blogs so you don't have to:

[Bytebytego @bytebytego]

10 Good Coding Principles to improve code quality.

Software development requires good system designs and coding standards. We list 10 good coding principles in the diagram below.

🔹 01 Follow Code Specifications
When we write code, it is important to follow the industry's well-established norms, like “PEP 8”, “Google Java Style”, adhering to a set of agreed-upon code specifications ensures that the quality of the code is consistent and readable.

🔹 02 Documentation and Comments
Good code should be clearly documented and commented to explain complex logic and decisions, and comments should explain why a certain approach was taken (“Why”) rather than what exactly is being done (“What”). Documentation and comments should be clear, concise, and continuously updated.

🔹 03 Robustness
Good code should be able to handle a variety of unexpected situations and inputs without crashing or producing unpredictable results. Most common approach is to catch and handle exceptions.

🔹 04 Follow the SOLID principle
“Single Responsibility”, “Open/Closed”, “Liskov Substitution”, “Interface Segregation”, and “Dependency Inversion” - these five principles (SOLID for short) are the cornerstones of writing code that scales and is easy to maintain.

🔹 05 Make Testing Easy
Testability of software is particularly important. Good code should be easy to test, both by trying to reduce the complexity of each component, and by supporting automated testing to ensure that it behaves as expected.

🔹 06 Abstraction
Abstraction requires us to extract the core logic and hide the complexity, thus making the code more flexible and generic. Good code should have a moderate level of abstraction, neither over-designed nor neglecting long-term expandability and maintainability.

🔹 07 Utilize Design Patterns, but don't over-design
Design patterns can help us solve some common problems. However, every pattern has its applicable scenarios. Overusing or misusing design patterns may make your code more complex and difficult to understand.

🔹 08 Reduce Global Dependencies
We can get bogged down in dependencies and confusing state management if we use global variables and instances. Good code should rely on localized state and parameter passing. Functions should be side-effect free.

🔹 09 Continuous Refactoring
Good code is maintainable and extensible. Continuous refactoring reduces technical debt by identifying and fixing problems as early as possible.

🔹 10 Security is a Top Priority
Good code should avoid common security vulnerabilities.

Over to you: which one do you prefer, and with which one do you disagree?

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/FIzCeaWsZV

[Compounding Quality @QCompounding]

10 sources of wisdom to never forget

1. Experience:

[le duc quang @ducquang98]

@samokhvalov @readwise save thread

[le duc quang @ducquang98]

@NaveenS16 @SaveToNotion #Thread

[le duc quang @ducquang98]

@deararchitects @stripe @sheenbrisals @level_out @OReillyMedia @readwise: save thread

[le duc quang @ducquang98]

@svpino @readwise save thread

[le duc quang @ducquang98]

@samokhvalov @PostgreSQL @readwise save thread

[le duc quang @ducquang98]

@kareem_carr @readwise save thread

[le duc quang @ducquang98]

@kozlovski @readwise save thread

[le duc quang @ducquang98]

@svpino @readwise save thread

[le duc quang @ducquang98]

@milan_milanovic @readwise save thread

[le duc quang @ducquang98]

@milan_milanovic @readwise save thread

[le duc quang @ducquang98]

@svpino @readwise save thread

[le duc quang @ducquang98]

@georgeselkhoury @readwise save thread

[Lior Alexander @LiorOnAI]

This is amazing. PanoHead is a new model that generates 3D textured models from a single image.
Github: https://t.co/KcrPxP3ga7
Paper: https://t.co/JGkIbLLIWx

[le duc quang @ducquang98]

@davefarley77 @readwise save thread