2 ms·
> I have grown to dislike "jugaad" solutions to problems Maybe it takes an outsider's view to appreciate jugaad. I certainly didn't on my first encounter. > n
by ggeorgovassilis 4y ago
> I have grown to dislike "jugaad" solutions to problems
Maybe it takes an outsider's view to appreciate jugaad. I certainly didn't on my first encounter.
> no adherence or even ambition to achieving excellence and craftsmanship
I agree - jugaad isn't the place for planned evolution, so skills that transcend the immediate needs for delivery never form.
> Aspiring to arrive to the jugaad solution to problems when better ways of doing it are within reach though, that's where I draw the line.
I think that most developers in India aren't even aware of the jugaad methodology, it's just the way things are done. When I was first exposed to jugaad I mistook it for sloppiness, but it turned out that both deliverables and the organisational setup itself is extremely anti-fragile: it's always easy to add or remove a part, although refactoring is hard.
- pm90 4y agoHeh, this is an interesting perspective and Im realizing some assumptions Ive come to rely on. When designing a system or writing code, my instinct is to write it in a way that makes it clear, easy to work with and change down the road, because Ive seen code that is not structured this way and working with it is hell. I consider myself somewhat lucky to have worked in teams that allow for this. If however I wasn’t fortunate enough, or just not paid enough even, or the work culture didn’t exist or was purely transactional, I would likely change my approach to fit that situation.