๐ง๐ต๐ฒ ๐๐ ๐ฝ๐ฒ๐ฟ๐ถ๐ฒ๐ป๐ฐ๐ฒโ๐๐บ๐ฝ๐น๐ผ๐๐บ๐ฒ๐ป๐ ๐ฃ๐ฎ๐ฟ๐ฎ๐ฑ๐ผ๐ ๐ผ๐ณ ๐๐ป๐๐ฟ๐โ๐๐ฒ๐๐ฒ๐น ๐๐ถ๐ฟ๐ถ๐ป๐ด ๐ถ๐ ๐ฟ๐ฒ๐ฎ๐น, ๐ฎ๐ป๐ฑ ๐ถ๐ ๐ฑ๐ผ๐ฒ๐๐ป'๐ ๐ฒ๐ป๐ฑ ๐ฒ๐๐ฒ๐ป ๐ฎ๐ณ๐๐ฒ๐ฟ ๐๐ผ๐'๐๐ฒ ๐ด๐ฎ๐ถ๐ป๐ฒ๐ฑ ๐ฎ ๐ณ๐ผ๐ผ๐๐ต๐ผ๐น๐ฑ ๐ถ๐ป ๐๐ต๐ฒ ๐ถ๐ป๐ฑ๐๐๐๐ฟ๐:
The experience-employment paradox is a perpetual career conundrum in Software Engineering, a catch-22 in which entry-level job seekers need prior work experience to get hired, yet cannot get hired to gain that experience.
Similarly, whenever a new technology emerges, we rush to learn it, but the industry demands people already experienced in that technology, making it extremely difficult to shift your domain.
๐'๐บ ๐ด๐ฟ๐ฎ๐๐ฒ๐ณ๐๐น ๐๐ผ ๐ฎ๐น๐น ๐๐ต๐ผ๐๐ฒ ๐๐ต๐ผ ๐๐ผ๐ผ๐ธ ๐ฎ ๐ฐ๐ต๐ฎ๐ป๐ฐ๐ฒ ๐ผ๐ป ๐บ๐ฒ ๐ฎ๐ป๐ฑ ๐๐ฟ๐๐๐๐ฒ๐ฑ ๐บ๐ฒ ๐๐ถ๐๐ต ๐๐ต๐ถ๐ป๐ด๐ ๐'๐ฑ ๐ป๐ฒ๐๐ฒ๐ฟ ๐ฑ๐ผ๐ป๐ฒ ๐ฏ๐ฒ๐ณ๐ผ๐ฟ๐ฒ.
#Gratitude #CareerAdvice #Freshers #EntryLevelJobs #SoftwareEngineering #Hiring #CareerGrowth #TechCareers #Mentorship #JobSearch #Catch22 #CareerDevelopment #GivePeopleAChance
The engineers who put out the fires that they themselves create due to their poor design are the ones highly paid and promoted.
A fire adds drama, metrics and the hero story. When things go well they look like normal baseline performance so it is hard to measure what did not happen.
Ironically, the best engineers build such stable systems that their day-to-day work looks uneventful, which can hurt their career progression in flawed corporate cultures.
๐ข๐ป๐ฒ ๐ฅ๐ฒ๐ฝ๐ผ๐๐ถ๐๐ผ๐ฟ๐ ๐ฃ๐ฒ๐ฟ ๐ง๐ฎ๐ฏ๐น๐ฒ ๐ถ๐ ๐ก๐ข๐ง ๐๐ต๐ฒ ๐ฅ๐ฒ๐ฝ๐ผ๐๐ถ๐๐ผ๐ฟ๐ ๐ฃ๐ฎ๐๐๐ฒ๐ฟ๐ป.
The inconvenient truth is that if you have a repository that has a 1:1 mapping to a table and exposes getById / insert / update / delete, you didn't create a Repository. You built one of these in its place:
ย ย โข ๐ง๐ฎ๐ฏ๐น๐ฒ ๐๐ฎ๐๐ฎ ๐๐ฎ๐๐ฒ๐๐ฎ๐ โ a thin wrapper on SQL for each table
ย ย โข ๐๐๐ข โ a data-access abstraction
ย ย โข ๐๐ฐ๐๐ถ๐๐ฒ ๐ฅ๐ฒ๐ฐ๐ผ๐ฟ๐ฑ โ if entities carry their own Save()
๐ก๐ผ๐ป๐ฒ ๐ผ๐ณ ๐๐ต๐ฒ๐บ ๐ฎ๐ฟ๐ฒ ๐ฏ๐ฎ๐ฑ. ๐๐๐ ๐๐ต๐ฒ๐ ๐ฎ๐ฟ๐ฒ ๐ป๐ผ๐ ๐๐ต๐ฒ ๐ฅ๐ฒ๐ฝ๐ผ๐๐ถ๐๐ผ๐ฟ๐ ๐ฃ๐ฎ๐๐๐ฒ๐ฟ๐ป.
The Repository pattern is designed around the domain model, not the schema: A Repository is an in-memory collection of domain objects.
Which means that:
ย ย โข One repo for each aggregate root, not for each table..
ย ย โข It conceals persistence altogether. Tables or joins are never seen by the domain.
ย ย โข Returns fully reconstituted aggregates, not rows.
#SoftwareArchitecture #CleanCode #SoftwareEngineering #BackendDevelopment #ApplicationArchitecture #Software #Coding #TechnicalArchitect
@MansiCodez Business documentation is necessary. If a programmer has to reverse engineer the business cases/rules by looking at the code, the problems will arise.
๐ช๐ต๐ ๐ฎ๐ฟ๐ฒ ๐๐ฒ ๐๐ผ ๐๐๐ฟ๐ฝ๐ฟ๐ถ๐๐ฒ๐ฑ ๐ฎ๐ฏ๐ผ๐๐ ๐ถ๐?
The seeds for this catastrophe had been sown even before LLM existed. The LLMs have now accelerated this problem beyond our capabilities of managing it.
In the Pre-LLM era, developers shipped the code with no adherence to architecture and discipline in the codebase. The hurriedly created โMVPsโ were made as a base for real projects. Reviewers accepted the PRs with no baseline of what reduced the technical debt. There was no metric, no threshold, no standard for measuring reduced technical debt. Review became a formality, not a quality gate.
The project transitioned from team to team without the transfer of any architectural vision. Code was never anybodyโs concern. Each new team inherited a black box and made their own assumptions. The original architecture, if there ever was one, was lost in the shuffle.
It was about how faster we can ship. We have inherited the same mindset. The AI is being used to ship features faster, but not to make products and code robust. Code was never anybody's concern. The only metric that mattered was, how fast can we ship. Craftsmanship, and long-term maintainability were deprioritized at every level.
Once a team was giving a Knowledge Transfer to me and I asked a simple question, โWhere is the business logic?โ, and the Lead shamelessly said, โItโs all overโ. Seriously?? Isnโt this year 2026??
And there was this team that I was going to be a part of, and this person in the management declared with pride, โWe are using the XYZ Architectureโ, but when I inspected the codebase, it was rotten beyond repair. To this day they are under the illusion that they are using the XYZ Architecture, and still trying to figure out why the development has become slower and blaming people for not using enough AI.
Even the interviewers never asked candidates questions on how to write maintainable code, OR how to write code so that incremental change becomes easier without breaking the existing features, OR how to reduce technical debt. Instead, they were busy exercising their intellectual vanity, asking about Data Structures which they themselves never used.
The patterns and practices of software engineering fell out of fashion. It became cool to know data structures instead of writing maintainable code.
How many of the interviewers and developers even know what Bounded Contexts are??
The educational institutions also never bothered to teach how to write maintainable code. They focused on teaching technologies that were โCoolโ and had market demand.
AI didn't break software engineering. It exposed how little of it we were actually doing. The problem isn't the LLM. The problem is us, and it always was.
๐ช๐ต๐ ๐ฎ๐ฟ๐ฒ ๐๐ฒ ๐๐ผ ๐๐๐ฟ๐ฝ๐ฟ๐ถ๐๐ฒ๐ฑ ๐ฎ๐ฏ๐ผ๐๐ ๐ถ๐?
The seeds for this catastrophe had been sown even before LLM existed. The LLMs have now accelerated this problem beyond our capabilities of managing it.
In the Pre-LLM era, developers shipped the code with no adherence to architecture and discipline in the codebase. The hurriedly created โMVPsโ were made as a base for real projects. Reviewers accepted the PRs with no baseline of what reduced the technical debt. There was no metric, no threshold, no standard for measuring reduced technical debt. Review became a formality, not a quality gate.
The project transitioned from team to team without the transfer of any architectural vision. Code was never anybodyโs concern. Each new team inherited a black box and made their own assumptions. The original architecture, if there ever was one, was lost in the shuffle.
It was about how faster we can ship. We have inherited the same mindset. The AI is being used to ship features faster, but not to make products and code robust. Code was never anybody's concern. The only metric that mattered was, how fast can we ship. Craftsmanship, and long-term maintainability were deprioritized at every level.
Once a team was giving a Knowledge Transfer to me and I asked a simple question, โWhere is the business logic?โ, and the Lead shamelessly said, โItโs all overโ. Seriously?? Isnโt this year 2026??
And there was this team that I was going to be a part of, and this person in the management declared with pride, โWe are using the XYZ Architectureโ, but when I inspected the codebase, it was rotten beyond repair. To this day they are under the illusion that they are using the XYZ Architecture, and still trying to figure out why the development has become slower and blaming people for not using enough AI.
Even the interviewers never asked candidates questions on how to write maintainable code, OR how to write code so that incremental change becomes easier without breaking the existing features, OR how to reduce technical debt. Instead, they were busy exercising their intellectual vanity, asking about Data Structures which they themselves never used.
The patterns and practices of software engineering fell out of fashion. It became cool to know data structures instead of writing maintainable code.
How many of the interviewers and developers even know what Bounded Contexts are??
The educational institutions also never bothered to teach how to write maintainable code. They focused on teaching technologies that were โCoolโ and had market demand.
AI didn't break software engineering. It exposed how little of it we were actually doing. The problem isn't the LLM. The problem is us, and it always was.
#VibeCoding #TechDebt #CTO #EngineeringCulture #TechLead #Claude #CodeQuality #SoftwareArchitecture #SoftwareEngineering
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
@SwiggyCares I have already received the refund for this. Thank you. I request you to pay attention to the quality of the items before you sell them. Your customers health must be given importance.
@getawheyindia I purchased your Mango ice cream through @Swiggy and when I opened it looked like this. Quantity appared half, it smelled like a rotting Mango and tasted bad. I had just has a small bit and I now am worried about my health. Please maintain your Quality.
@HDFCBank_Cares, can you solve my 16-year-old problem? Please stop the calls offering personal loans. If I need loans, you will be the first one to receive my call.
@HDFC_Bank#loans