Fork me on GitHub

Morning ☀️

❤️ 1
David Pham09:11:33

Good morning :)


Good point about the name!


Side note: I upgraded my OS and have taken to using bat all the time. Thanks for the tip!


Morning 👋


Traveling to Berlin 🎉

🏭 3
🧸 1

good morning


Man, sometimes I hate presenting stuff I’ve made to end users… the amount of nitpicking that goes on around small details is unbearable and hardly anyone focuses on the massive task that was accomplished.


Sounds frustrating! Not sure if this applies to your situation but I found that involving stakeholders early and often helped. Nitpicking on minor visual aspects can sometimes be an expression of wanting to be more involved in some way.


Good point. I think I have, but they’ve been rather busy and not really willing to get more involved when it was more conceptual/data wranling. Presenting a graphical application of the underlying data has opened the flood gates.


One of them just came over and apologised for being overly negative. I guess they could see it made me rather uncomfortable. Made me feel a bit better.

❤️ 2
👍 1

Oh that's nice!


Not at all saying your stakeholders are children... but I remember when I involved children in their meal preparation they were much more likely to enjoy their meal.

😁 4
❤️ 1
👏 1

Them apologizing is nice!


Once had a very nitpicky boss, so the dev team started implementing obvious flaws in the frontend, so they could nitpick on the “prepared” issues which were easily removable, and not started looking for issues that were not there.

👍 3

hah, of course there is a term for that


By sheer coincidence, the 64-across clue in today's New York Times crossword is Nitpickers.


The universe must be aligned against me


it's the user equivalent of bike shedding, in fact it's just bike shedding - we adopted that from the real world 🙂


everyone likes to deal with stuff they can grok rather than the stuff that is outside of their wheelhouse


I was going to bikeshed your use of bikeshedding but stopped myself when I realized I was being a pedant (answer to today’s crossword nitpicker clue!). I never looked up bikeshedding before, interesting!: > +‎ The term was coined as a metaphor to illuminate Parkinson observed that a committee whose job is to approve plans for a may spend the majority of its time on relatively unimportant but easy-to-grasp issues, such as what materials to use for the staff bikeshed, while neglecting the design of the power plant itself, which is far more important but also far more difficult to criticize constructively. It was popularized in the community by and has spread from there to the software industry at large.


@U04V5V0V4 Yeah… it’s not my first experience with this kind of stuff. I remember at my old job I managed to finish a task in a single sprint that no one had basically dared to approach in 2 years (they were scared of the complexity and always picked more low-hanging fruit). I worked several late days and got it done in time - was really proud of myself. Then I presented the new features to some end users and the manager who was present had to interrupt me at some point and say “so see, even though it looks very basic, it actually took two whole weeks to do!“. I was fuming inside. If feel like software development - at least in this country - has this peculiar quality of being both low status while also being seen as highly complex and well-paid.

💯 1

It’s an issue I often had in internal development teams that are financed with budgeting. “They cost money, but don’t make any”.


@U4P4NREBY yeah that mix of status / rewards is a great observation: we really are white collar plumbers.


Not sure why, but I've always felt more like a drywaller myself.


Because you are always getting plastered?

Jakub Holý (HolyJak)20:11:58

I'm practicing the fine art of code archeology, namely on, drilling down back to 2015...

🪥 2
Jakub Holý (HolyJak)22:11:37

The same piece of code is used in #fulcro and nobody knows why it is the way it is.


fantastic 😄