Heshitha Hettihewa

🇱🇰

[Sunny R Gupta 🐰 @sunnykgupta]

https://t.co/mzCSKYGpvB

[OpenChoreo @openchoreo]

Introducing support for self-hosted GitLab repositories!

You can now seamlessly connect your self-hosted GitLab repositories to Choreo, allowing you to create, build, and deploy components.

[Raul Junco @RaulJuncoV]

In 2011, Netflix was in trouble.

They have dozens of internal services; if one fails, the error will break the UI.

20,000 requests per second, about 1,000,000+ requests from the API into upstream services in 10s.

They have no choice but to increase resiliency.

The solution was brilliant; they went beyond the classic CircuitBreaker.

3 strategies that will help you make your system resilient:

Fail Fast

You use this strategy when no reliable fallback mechanism is available.

Instead of trying, the system halts the operation when as soon as an error an error happens.

Providing immediate feedback to the other systems, saving system resources.

But it could impact the user experience.

Fail Silent

This strategy comes into play for optional or non-essential data.

In case of a failure, the API would return a null value or a default value instead of propagating the failure.

This way, the failure does not propagate, and the user might only notice if the data is critical to the operation.

Custom Fallback

Use this strategy when local data is available, for instance, in a cookie or local cache.

Instead of calling a failed service or DB, the system uses local data to provide a fallback response.

The user still receives a response even if it's not the most up-to-date or complete.

These strategies are not one-size-fits-all; you must find the one that fits your system.

The more you know your system, the better you can prepare it to bounce back from failure.

[Alex Brogan @_alexbrogan]

Most people suck at decision-making.

Let's change that.

Here are 15 of the best decision-making mental models I've found:

[Sagar @code_sagar]

Too much information will ruin your life and peace.

Nemo is a 22 year old fresh CS graduate from BITS and just started living in Bangalore

After two years in Bangalore Nemo meets Shahrukh Khan at Church Street Social

Shahrukh Khan a serial entrepreneur makes $10 Million a year, selling mobile apps.

Nemo asks SRK, how can Nemo too earn like him?

SRK replies: Just start writing online, learn about marketing, content creation, audience building and you will get there.

But, Nemo is a FullStack Engineer fluent in JavaScript, Java, Distributed Systems and DSA

The last book Nemo read was "Designing Data Intensive Applications."

Whatever SRK said Nemo had never done those in his life and doesn’t interest him as well.

Confused Nemo.

Years passed Nemo is now 28

Nemo is on his evening walk with his then girlfriend in Kasol.

The himalayas are glowing in the golden hour accompanied by the sound of Parvati River and chirping birds.

Nemo suddenly bumps into Sundar Pichai

Excited Nemo asks Sundar his take on life and money

Sundar makes $30M a year from his job as the CEO of Google

Sundar says: If you want money, you have to work hard, get a degree from a premier institute, and deliver some of the best products of the world like Android, Chrome, etc.

Nemo is now motivated to delve deep into his passion of engineering.

He studied and gets a job in a FAANG as a Senior Software Engineer building some crazy products for billions

Happy Nemo.

Few years passed,

Nemo is now 30 years old, he has a lovely wife and a beautiful daughter

They are spending weekend night having dinner at Ritz Carlton, Bangalore.

All laugh and giggles suddenly Ritesh Agarwal (OYO Founder) enters the same hotel in his swanky car and cool outfit

Nemo saw Ritesh and thinks he should have started 10 years back and killed it like him. Now he is bound with a family and can’t take much risk.

Sad Nemo.

10 years later,

Nemo has $10M in net worth and so much passive income from his investments that he doesn’t need to work, and he's just 40.

Nemo has a lovely family and a very comfortable life if he starts something new it’d just be for fun or for a greater good.

Yet Nemo has an unanswered question

How does Nemo make $10M a year?

Every day he asks himself -

Did I take the right decisions?

Am I a failure?

What if I left my FAANG job and started on my own?

Sadly, there’s no SRK, Sundar or Ritesh to answer his questions.
He is all alone and have to decide for himself.

Nemo is Finding Nemo.

-------

From a lens of an average person, Nemo is living a fantastic life, yet questioning himself everyday the question that are not worth it.

From Nemo’s journey we see that

- Nemo has a unique life, so does SRK, Sundar and Ritesh

- Nemo made huge money for himself. Eventually every honest work gets paid

- Too much information without context stole Nemo’s peace

So, how do Nemo save himself from these flood information and comparison that steals his peace?

1. Discard information like crazy

2. Question everything and compare if your life is identical to the other person. Mostly it won’t be, so don’t worry.

3. Take advice from people of your area of interest. Like to build mobile apps ask SRK, want to run hotels ask Ritesh

4. Read books like emotional intelligence, an organized mind, design your thinking. It helps.

Information overload is a huge problem and learning how to navigate this flood of information is an urgent ask of the day.

Especially for software engineers because they are the most exposed profession.

A SWE processes tons of information daily either by learning or meeting new people or news.

Don't let information dictate your happiness.

=====

Like if you like Nemo’s story

Repost if you want to help someone

Comment your views - good or bad put it down there.

I am Sagar, I write notes on Software Engineering and Dev Life to entertain, educate and inspire people.

Join me for more.

[Heshitha Hettihewa @Drifftr]

https://t.co/ALJtpaN0Ax

[Sebastian Sigl @sesigl]

Software design patterns you MUST know:

🧩 Singleton: One instance per class

🚌 Observer: Monitor & notify object changes

🏭 Factory: Method for creating objects

🌉 Bridge: Decouple abstraction from implementation

🎭 Proxy: Interface representing another object

📚 MVC: Separating application’s logic, UI, and data

⛓️ Chain of Resp.: Decentralized request handling

🎈 Prototype: Clone objects for fresh instances

🍂 Composite: Treat individual & group objects uniformly

🖋️ Command: Encapsulate request as an object

🎤 Mediator: Centralize external communications

🍦 Decorator: Add responsibilities dynamically

📦 Adapter: Match interfaces of different classes

💼 Strategy: Define interchangeable algorithms

🪄 State: Allow object’s state to change its behavior

🎢 Flyweight: Reuse objects by sharing common data

🌐 Facade: Simplify access to complex subsystems

⚖️ Template: Prescribe method structure in an algorithm

🛡️ Proxy: Control access to an object or resource

🌲 Builder: Separate construction & representation

Mastering design patterns: the bridge from novice coder to seasoned developer.

Anything else you have used?

Please share 👇

[Alif Hossain @alifcoder]

A Complete Back-End Developer Roadmap:

[ THREAD ]🧵

[Andrew Lokenauth @FluentInFinance]

If you want to increase your income, then master job interviews — This skill will increase your earning potential 10X.

Here are 15 tips with a high rate of return, to get more job offers and negotiate a higher salary:

1) Being good at job interviews will increase your chances of being hired, even if you're not the most qualified.

You may not be the smartest in the room, but you can be the most prepared.

Being prepared will help you feel more confident and relaxed, and not nervous or caught off guard.

2) Always communicate your value proposition.

Highlight your relevant skills, experience, and accomplishments that make you the best fit for this specific role — which are directly related to the job description.

Look at the job posting to understand the specific requirements and responsibilities of the role, and explain how you have the skills to get the job done.

3) Always tailor your resume to the specific role and company that you are applying to — It will help you stand out.

Only highlight your skills and experiences that are relevant to the position you are applying for, and use keywords from the job posting to show you are the best fit for the role.

4) On your resume, focus on your achievements and results. Instead of listing your responsibilities, use examples and metrics to quantify and show the impact of your work and the results you achieved.

Instead of saying "managed a team," instead say "led a team of 10 to increase sales by 20% in 6 months."

5) On your resume, use action verbs to describe your responsibilities and achievements.

Action verbs such as "achieved," "developed," or "designed" can help to make your resume more dynamic and highlight your capabilities.

6) Always use industry-specific language and keywords to show your expertise and familiarity with the field.

Research specific language and keywords used in job postings for similar roles, and incorporate them into your resume.

7) The "Tell me about yourself" Question:

This is an excellent opportunity to give an overview of your relevant background, experience, and skills.

Focus on your most relevant experience and accomplishments (in relation to the position), and how they make you a good fit for the role you are applying for.

8) The "What's your greatest weakness?" Question:

Start with: "I'm not sure what my greatest weakness is in regards to this role, but I can talk about a weakness in the past and how I overcame it"

Highlight a past shortcoming and illustrate how you overcame that weakness with examples.

9) The "What sets you apart from other candidates?" Question:

Highlight your top 5 strengths directly related to this role.

Look at the job description to see which specific strengths they are looking for and give examples of you possessing these traits in prior roles.

10) Always follow up after the interview.

Sending a thank-you note or email is a polite way to show your appreciation and reinforce your interest in the position.

This can be a simple message thanking the interviewer for their time and reiterating your qualifications for the role.

11) Always know your worth. Never be afraid to negotiate for a higher salary. It's always okay to ask for what you want.

Think about the skills and experience you bring to the table, and how they add value to the company.

Build a case for why you deserve a higher salary.

12) Always use specific examples to demonstrate your value.

During salary negotiations, provide examples of your achievements & contributions

For example, if you increased sales by a certain percentage or implemented a new process that improved efficiency, mention these accomplishments

13) Before you begin salary negotiations, know what the market rate is for the position you are applying for.

Look up salary data for similar positions on websites like Glassdoor or Payscale, and use this information to help you determine a fair and reasonable salary range.

14) I hope this information is helpful.

Whether you are looking for a higher-paying job, improved work-life balance, or more quality time with your loved ones, I wish you all the best in achieving your goals.

May you be blessed with success and happiness in your career journey.

[Rakesh Jain @devops_tech]

Mastering kubectl! 🌐⚙️

A thread explaining 20 imp kubectl commands with brief explanations 👇

[Heshitha Hettihewa @Drifftr]

https://t.co/XxvZqy53dV

[Raul Junco @RaulJuncoV]

Software Development is a game of trade-offs.

Here are 5 tips to consider if you want to make the right trade-off.

[David Boyne @boyney123]

Fundamentals of event-driven architecture

Here are some thoughts I have been diving deep into this year, with things I learn about EDA I wanted to group them into three areas I think can help when you build EDA applications.

Identify and design
Like most things I think you have two options here, start implementing or stop and understand behaviour of your system. Previously I used to just dive in, but now understanding domain-driven design, event-first thinking it's important to map domains, highlight boundaries and design events before diving deep.

Collection of patterns
Once domains are identified, understanding messaging/event patterns can really help. Here we talk about integration patterns (e.g Claim check, splitter, message translator), just having an understanding of what patterns there are, can really help you map these patterns to various uses cases you will come across.

Operational and maintenance
Often overlooked, but how do you keep your EDA applications successful in 12-24 months? Should you be documenting your events/producers/consumers? What about standards in your events/architecture? What about distributed tracing for your events? These things need to be considered to make sure you have a high chance of success.

If you want to learn more I have a visual and extra resources for you 👇

https://t.co/POBQg6XTru

[javinpaul @javinpaul]

Top 5 Things Experienced Java developer should learn
1. Microservice - https://t.co/LpKprotnbY
2. Design Pattern - https://t.co/oRVlhzQ92X
3. Refactoring - https://t.co/8niHbahuJM
4. System Design - https://t.co/oKNpKQR34t
5. Big Data - https://t.co/W8FCEX3J4v

[Vadym Kazulkin @VKazulkin]

"Migrating Netflix to GraphQL Safely" by @NetflixEng https://t.co/GzSz8k0ia9

[Dr Milan Milanović @milan_milanovic]

𝗧𝗼𝗽 𝟭𝟬 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀

I've just released the new issue of my 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿 talking about Software Architecture Patterns to more than 9.000 addresses.

Here we talk about:

🔹𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘁𝗵𝗲 𝟭𝟬 𝗺𝗼𝘀𝘁 𝗰𝗼𝗺𝗺𝗼𝗻 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀?

🔹𝗔𝗿𝗰��𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗳𝗿𝗼𝗺 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗽𝗼𝗶𝗻𝘁𝘀 𝗼𝗳 𝘃𝗶𝗲𝘄.

🔹𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝘀𝘁𝘆𝗹𝗲𝘀, 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀, 𝗮𝗻𝗱 𝗱𝗲𝘀𝗶𝗴𝗻 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀?

🔹𝗔 𝗳𝗿𝗲𝗲 𝗲-𝗯𝗼𝗼𝗸 𝗼𝗻 𝘁𝗵𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗼𝗳 𝗢𝗽𝗲𝗻-𝘀𝗼𝘂𝗿𝗰𝗲 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀.

Check it from the following link: https://t.co/LanOF91RS8.

#technology #softwareengineering #programming #techworldwithmilan #softwarearchitecture

[Nuwan @nuwandias]

Introducing the super cool visual data mapping capability on Choreo: https://t.co/KNUnUZSQJs @ChoreoDev @ballerinalang

[Chayu Damsinghe @ChayuDamsinghe]

Useful comments

[Heshitha Hettihewa @Drifftr]

I found a #cloud #torrent that's awesome ;) @seedrcoil it's FREE just give it a try! https://t.co/8QA4ucADnl

[Heshitha Hettihewa @Drifftr]

I found a #cloud #torrent that's awesome ;) @seedrcoil it's FREE just give it a try! https://t.co/8QA4ucADnl