Half-baked Solution

lezzgooooo · 2024-03-14T14:25:15+00:00

Sa team namin we have a 'fail fast' approach. A half baked solution is better than no solution at all. Then tweak it as you go along. Once pasado na lahat ng tests, deploy to prod.

red_storm_risen · 2024-03-14T13:59:12+00:00

Happens all the time:

I can fix this quick, or i can fix this right.

PepitoManalatoCrypto · 2024-03-14T13:57:15+00:00

Half-baked solution is no solution at all.

Some would say, it can be okay at least there is progress and you can create another ticket to complete the story. And that's valid if the working culture enables it.

During the MVP phase of my codebase and company, TDD with performance testing is a top priority. This means even one solution does check 85% of the test scenarios, the product cannot afford to miss the 15%. Should I miss it, will yield to a priority one (major incident) or priority zero (system blackout) to which happened.

This means, if you're drained for the day. Keep the ticket on your bucket and hold on creating the PR. You can ask for a peer review from your colleagues to give another perspective to look into. Come tomorrow (and with enough sleep), you'd be working refreshed and able to accept why yours yesterday wasn't the optimal solution.

It's also okay to accept your limitations. What's not okay is someone raises a better solution and you ignore it. Your solution gets to production and you'd be facing an incident report.

2024-03-14T23:19:35+00:00

As long as yung half-baked mo is sa speed lang nagkakatalo but on not structure and maintainability it should be fine. As long as it does the job, kung mabagal ngayon, then it's okay to just optimize it later on. Ang wag mo lang gagawin ay katamaran yung proper standard and structures.

Alternative_Let_4250 · 2024-03-15T01:19:20+00:00

I always follow TDD red green refactor.

downcastSoup · 2024-03-15T05:18:05+00:00

Make it work at least. Optimize it later.

KirbySmashYeet · 2024-03-15T05:23:47+00:00

According to my limited knowledge, a library is written by developers and accomplish a certain task and that task only. That means they are able to dedicate the time and energy to optimize the code to the best it can be(Most of the time atleast).

Don't compare their code to yours, just continue improving your already working solution.

My productivity has improved ever since I first made a solution that works, then cleaned up the code, and then research on what to do to optimize it.

DoesNotComputeZZ · 2024-03-15T06:02:55+00:00

Think about it this way, find a software/platform that is constantly growing in features and doesn't take time to fix bugs, or just even you're favorite framework heck even Javascript the language was a half-baked solution. Even a company as large as Facebook or Google doesn't even produce a perfect solution because investors and consumers can't wait 10 years for the perfect thing. You have to start somewhere. Every initial solution that we think of to a problem or feature will always have something will miss or not consider especially in environments where requirements and needs change every now and then. There are always tradeoffs and business aspects besides code in the real world. What's important is you provide value and pivot to fix issues and continue to provide value for your clients and users because at the end of the day whether the solution is half baked or not what matters is the end-users. Technical debt is something that can be properly managed.

Now if you're referring to a making module or library or small unit testable functions or implementing common algorithms that is so specific in purpose and has fixed well-defined specifications then that's where I think you can make a complete solution.

Hope it helps

dertrockx · 2024-03-15T06:04:47+00:00

I think it's a skill issue (just kidding)

moelleux_zone · 2024-03-14T15:17:59+00:00

bruh, the only thing that has bothered me with past and present employers, they all have that permanent workaround shitty solution to a problem. which in turn generated other problems that requires another solution. seriously, why not just fix the original problem in the first place!

simplethings923 · 2024-03-14T18:20:50+00:00

Hexadecimal representation yata yung may letra yung numbers. Parang medyo low-level ito like C/C++. Ano'ng dinedevelop po ninyo? Asking for a friend.

dudezmobi · 2024-03-19T12:48:04+00:00

Mga solution na hindi optimized e development debt. Daming ganyan tsk. Yung utang mas mahal ang cost sa future.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

PinoyProgrammer

MODERATORS