Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Grug Brained Developer

grugbrain.dev

Post reply on HN
Print view View original

341–350 of 394 posts

Re: The Grug Brained Developer

#341

Post by nisegami »

jstanley wrote: post #18

> grug no able see complexity demon, but grug sense its presence in code base This is the key problem with complexity. Complexity is fine if you understand it! It's when you're aware that something is complex, but you start to get these mental force-fields pushing you aware from the scary parts, that it becomes a problem. > demon complexity spirit mocking him make change here break unrelated thing there what!?! That'…

>but then 3 years later you realise something you somewhat care about has been silently broken for a very long time

The trick is to never stay somewhere long enough to feel the consequences of your bad decisions

Re: The Grug Brained Developer

#342

Post by pvillano »

xbar wrote: post #233
throwaway892238 wrote: post #172

Earlier quoted context omitted.

> I don't want to see yet another developer say "complexity bad". > I want to see a company deliver high-quality products with very few bugs at a fast cadence, and continue to make major changes long into the future without slowing down. you want eat cake and have cake.

...and now you have 2 cakes.

idea start with one cake. eat only cake mean no cake left :(

Re: The Grug Brained Developer

#343

Post by pvillano »

bpicolo wrote: post #152
strix_varius wrote: post #146

Earlier quoted context omitted.

For me, that's 50% of it. The other 50% would be: > type systems other most value when grug make wrong, but no user see because big red arrow point to first.

The other big one is I think Rust style enums (especially to enable null-safe types) are amazing. Lots of real world problems are solved well by really darn good enums.

grug hate magic number, magic string

Re: The Grug Brained Developer

#344

Post by sethd »

wildrhythms wrote: post #221
geekbird wrote: post #176

Earlier quoted context omitted.

This. Premature and excessive fragmenting into unmaintainable and operationally microse5rvices is the bane of my existence. It's often done by zealots, who see microservice architecture as a matter of religious faith, not operability convenience. Sure, some monoliths are harder to debug if there are multiple distinct packages that need to operate together if they are all in the same container. But fragmenting a simpl…

i can't tell you how many teams I've seen spend months and months engineering some vast microservice system only to end up serving maybe 500 DAU. It could have been a single executable on a $5 VPS

Wouldn't replacing that with a single point of failure be going a bit too far in the other direction? Perhaps three $5 instances?

Re: The Grug Brained Developer

#345

Post by cwoolfe »

dack wrote: post #102

As funny as this post is to read, I don't want to see yet another developer say "complexity bad". I want to see a company deliver high-quality products with very few bugs at a fast cadence, and continue to make major changes long into the future without slowing down. _THEN_ I want developers from that company to share their opinions about how they do it. Do such companies/products even exist? Software is so bad these…

Doesn't Apple "deliver high-quality products with very few bugs at a fast cadence, and continue to make major changes long into the future without slowing down" ? I'm not sure how they do it; but I like their products. It seems like they do it by saying no to a lot of complexity; while embracing necessary complexity.

Re: The Grug Brained Developer

#346

Post by pvillano »

TremendousJudge wrote: post #331
Tade0 wrote: post #306

> grug brain developer try collect learns into small, easily digestible and funny page, not only for you, the young grug, but also for him because as grug brain developer get older he forget important things, like what had for breakfast or if put pants on grug relate. other day grug forget Angular have pipes even though grug use async pipe in same PR. This is particularly concerning for me because not being too stron…

grug brain like pokemon brain: have to forget thing to learn new thing. sometimes old thing useless, sometime old thing very important like bank password

grug brain tip: password manager. grug only remember one password. even on other computer, grug look up password on phone

grug brain tip 2: use grug-brain-compatible password generation algorithm. Grug only need remember algorithm

Example: f("hacker news") = "GRUGgrug invent first part with number and symbol one time. rest change depending on site

Re: The Grug Brained Developer

#347

Post by pvillano »

trwhite wrote: post #99

I have been thinking about the complexity bias that affects our perception of quality. I think as programmers it is our natural assumption that if something is complex, lots of thought must have gone into it beyond our understanding. This is especially true when starting a new job. But this is slightly ironic because often more code makes something slow, which isn't a good thing at all.

code can be thought of explaining to a computer what do you want it to do.

In general, explaining without managing complexity is easy and makes you look smart. However, explaining so anyone can understand is very hard. Grug author good at this

Re: The Grug Brained Developer

#349

Post by bb88 »

timr wrote: post #253
bb88 wrote: post #240

Earlier quoted context omitted.

> Anyway, it might be good to talk to your PMs and not assume they're evil villains. I've always thought PM's to be more or less aliens with a ray gun tapping at their watch. Communicating with them goes nowhere since they don't empathize with your point of view. The only thing they're concerned with is when something's going to get done. The only form of motivation is threat of existence in the company. > While I've…

I've been the guy who gets called at 4am when postgres takes a dump. I've also been the guy doing the calling (well, not really as a PM, since again, we don't generally have the ability to tell anyone what to do at 4AM , but I digress.) > Communicating with them goes nowhere since they don't empathize with your point of view. Can't speak for everyone, but again, I've been on both sides of the table, and I've never se…

> if your PM is motivating you via threats, something is very wrong.

Seriously? This is how 80% of companies work. In many of those companies, stack ranking is a very effective tool for running people out the door. It's often _baked_ into corporate culture.

Re: The Grug Brained Developer

#350

Post by strix_varius »

ngc248 wrote: post #304
strix_varius wrote: post #140

Earlier quoted context omitted.

I don't know if this is universal, but in my circles "microfrontends" are now all the rage. How do you bring up concerns with that in good faith? It's so obviously terrible that I've no idea where to begin.

MicroFrontEnds (MFE) solve an actual problem, but it becomes a problem if developers do it for the sake of RDD (Resume Driven Development) or just because. My Company has a Cloud platform which is kinda like a marketplace and users can install and uninstall apps/services. In our case MFEs are a perfect fit.

I have yet to see such a scenario where either web components or iframes would not have been a better fit.
Post reply on HN