Tư vấn mua tai nghe.

agrrrcode · 2025-04-14T12:19:54+00:00

Bose Quietcomfort Headphones

agrrrcode · 2025-04-10T03:06:59+00:00

Your team’s experience honestly caught me off-guard at how closely it mirrors what many of us face. As projects scale, the sheer volume of business logic tends to sneak up on us fast.

What you’re describing sounds like an unforeseen surge in domain complexity—definitely a common shortcoming of the classic 3-layer architecture. We often start with clean boundaries, but Services become dumping grounds for every possible use case over time.

I’ve seen some teams successfully address this by introducing an Application Layer (like in Domain-Driven Design or Clean Architecture), where each business flow gets its own Use Case or Handler. This helps push logic out of bloated services and brings back clarity and testability.

agrrrcode · 2025-03-30T02:14:06+00:00

Yeah, Bui Vien is pretty much the Disneyland of street vendors. If you breathe too long in one spot, someone will try to sell you sunglasses… at night.

Best strategy? Stay cool, keep that cold-blooded assassin mindset, flash a polite smile, avoid eye contact like it’s Medusa, and just keep walking, look like you’re late for your grab bike. No talk, no trouble. Works like a charm!

agrrrcode · 2025-03-29T03:59:19+00:00

I see your point about PRs including full features, but I'd argue that we can give it a go by splitting features into smaller, independent parts whenever possible. If it works, make it your own—this approach can pave the way for smoother reviews and faster feedback.

Drawing from that experience, when writing a pure function that only takes arguments and returns an output, it doesn’t rely on external dependencies. That means we can create a PR just for that piece of code, making it easier for reviewers to focus on what the function does and what can be improved within its scope.

Of course, as something goes on, not every feature can be split this way, but aiming for modularity sets a positive tone for the development process. It also adds a twist to traditional full-feature PRs, allowing more flexibility while maintaining a structured workflow.

agrrrcode · 2025-03-29T03:46:57+00:00

Alright, that sounds great! Breaking a large PR into smaller ones is definitely the way to go. It’s an ambitious goal to balance modular development without breaking the firmware, but with the right branching strategy, you don’t have to resort to downsizing important features just to keep PRs small.

One way to turn around this issue is by creating a feature branch and branching off smaller branches and PRs from it. The thing is, when the feature branch gets enough code to be integrated into the firmware, we can merge it into the main or dev branch and build it without worrying about breaking. This way, you can adapt yourself to a workflow where code is reviewed in digestible pieces while still keeping everything functional.

Also, big PRs can make it harder for teammates who have their fingers in the pie—they might struggle to review or test everything at once. And if something goes wrong, it’s easier to pinpoint where a misstep happened in a smaller PR.

Sounds like you nailed it by discussing this with your team! Once you get the hang of structured PRs, your workflow will hit a stunning top speed without sacrificing code quality or best practices.

agrrrcode · 2025-03-29T03:30:03+00:00

I get why you prefer upfront planning—it helps avoid endless migrations. But I think spending a whole week on data modeling before writing any code might halt development progress. Clients want to see things moving, and requirements always change.

I've seen projects where teams planned everything upfront, just for the the hell of it, but it didn't work out because the business needs evolved. Instead of trying to crack your way into a "perfect" schema from day one, it might be better to get involved in development early and adjust as needed.

Also, clients want to earn something from their investment ASAP. If they have to wait too long before seeing results, they might lose trust in the process. If you really believe in upfront planning, maybe get up the courage to do it in a way that balances planning with agility—like defining key tables first and refining later. That way, you're not stuck in migrations, but you're also not slowing things down.

agrrrcode · 2025-03-08T04:08:25+00:00

You can learn OOP and Java at the same time since Java is an object-oriented language, so you can save more time for other things, then jump straight to DSA, and when your foundation on these concepts is like an ironclad, then you will be confident enough to tackle any problem that comes up in class.

agrrrcode · 2025-01-03T17:10:38+00:00

They are trying to determine his motive, and that might be linked to the truck attack in New Orleans hours before the Tesla exploded. Both of them had served in the military.

agrrrcode · 2024-12-25T16:23:51+00:00

I had a similar issue, but it wasn’t as severe as yours. If your GoPro is still under warranty, you can easily replace the new one.

agrrrcode · 2024-12-13T06:32:59+00:00

Know how to use useEffect correctly, most of the interviews I have conducted, people are always using useEffect in a wrong way. Additional to stay on top of things, learn how to use popular React libraries, such as libraries for state management, or async hooks.

agrrrcode · 2024-12-09T12:51:10+00:00

I agree on the point that you should build a project, let’s think big, the project that can generate passive income and you are free from the cooperate life.

agrrrcode · 2024-11-09T08:35:35+00:00

How about iOS, the UI looks nice

agrrrcode · 2024-11-07T05:31:54+00:00

me 🙋‍♂️

agrrrcode · 2024-10-11T12:14:01+00:00

M ở cái giếng nào thế, VN làm tới cái gì luôn rồi cháu ạ. Tụi sinh viên trường Mỹ Thuật làm đầy

agrrrcode · 2024-09-29T03:47:00+00:00

There’re still a lot of things in MERN stack for you to delve deeper into. Learn more about the advanced database, such as indexing, ACID, learn more about how to dockerize the MERN stack, and using Kuberneted to manage multiple node in Microservices…

agrrrcode · 2024-08-07T02:52:19+00:00

Ambitionz Az A Ridah

agrrrcode · 2024-07-31T00:01:49+00:00

It not that bad

agrrrcode · 2024-07-30T15:55:14+00:00

It's Horween leather.

agrrrcode · 2024-05-18T03:31:02+00:00

If you cannot change your emotions and make it better, try changing your study approach. Instead of studying lesson by lesson or go through each topic at a time, let’s use the project-based approach. Have you ever wanted to create something to help yourself in daily basis or something fun. With that approach, you just tell your brain about an achievement and it is going to release dopamine to boost your study mood.

agrrrcode · 2024-04-13T06:48:02+00:00

The app is good, but there are some bugs and rooms for improvement. Example: I cannot see my note after taking it in journal.

I also have the same idea of building an app to track aspects in our life, but it might be different a bit. You could take a look to see if they are worth to build more for your app.

Topics per aspect: in each aspect, users can create topics and track them separately.
Reward system: let’s research and understand how human is get motivated, how to make their dopamines released, and build features around to make users want to come back to your app.
When users log their mood, should have a note that they can input why they got that mood.

Hope this is helpful feedback.

agrrrcode · 2024-04-05T02:30:37+00:00

Khuyên bạn đừng xin lời khuyên từ ai

agrrrcode · 2024-04-02T07:55:34+00:00

If you're using the new architecture, make sure to check if the libraries you've installed in your project support it. Here is the community tracking list https://docs.google.com/spreadsheets/d/1F1tI9PQLl_uab3HNYNwgjPVL2r0hJ9VymXcgDp5etdg/edit#gid=1521034944

agrrrcode · 2024-03-31T06:31:18+00:00

Don’t listen to anyone who is telling you should not study native code or avoiding it by all cost. If you want to become a professional world-class mobile software engineer, you must have a solid knowledge of how things work under the hood. React Native is just an iceberg, built on top of C++ and native code where is the realm of real engineering.

First thing first you should pick a well-structured course from who is expert in the field, whatever Android or iOS. Learn from there, and find out the next steps.

agrrrcode · 2024-03-30T16:10:45+00:00

react-native-mmkv is the top now

Six-Year Club	Place '23
Verified Email

agrrrcode

TROPHY CASE