miChou
5.9K posts

miChou retweetledi

A thread on Product Thinking:
twitter.com/shreyas/status…
Shreyas Doshi@shreyas
As they grow in size, teams within megacorps and startups tend to implicitly bias more towards Project Thinking and not enough Product Thinking. Product Thinking is a mindset and a process that, once you see, you cannot unsee it. Product Thinking, Project Thinking, a thread:
English

@raganoakley @Adobe Log in with your username on adobe.com and accept the Terms of use there. You will be able to continue in the app afterwards.
English

@DynamicWebPaige What's wrong with using Word to edit your CV... like normal people? :))
English
miChou retweetledi

@IanColdwater That's an easy one: site has a character limit on passwords, sign in and sign up do not truncate before sending to backend, but reset does.
You'd be amazed how often that happens and how many times reset is a second class citizen compared to sign in/sign up...
English
miChou retweetledi

I liked this backend developer roadmap by @kamranahmedse roadmap.sh/backend -- it's impossible to build a list like this that everyone agrees on but it's a good starting point

English
miChou retweetledi

@0xcafebabe @noahsussman As always, context matters, and the same tools can be used for good or evil. FWIW, the team I'm in moved from ~100/8000 flaky tests to ~10/9000 flaky tests in the past year. Would have I been better off leaving the team/company when we were at 100/8000? I highly doubt it.
English

@0xcafebabe @noahsussman Also, it's more about retry-to-total-tests ratio. Is it 10 tests out of 10.000? Then it might be OK to always retry them. Is it 100 tests out of 5000? Maybe you're better off spending _some time_ investigating and fixing the root causes. Is it 200 out of 400? Stop now & fix 💩
English

Hey, testing practitioner twitter: What are your thoughts on automatically retrying E2E tests? Do you do it? Only for tests depending on external systems? Do you find it hard to get rid of flakey tests? (cue @noahsussman)
English
miChou retweetledi

@lucianadrian @santhoshst I would rather ascribe it to the (perceived) lack of feedback that saving usually has. When you're unsure if you really pressed those keys and there's no way way too tell it, you do it a couple of times “just to be sure”.
I doubt vim users :w! multiple times in a row 🤓
English

@santhoshst How did you realise this? Broken key or some other sign? Also, why so little trust in the autosave feature? Wait ... you're a #testing person and seen that fail
English

Thoughtful and nicely explicited thread. Applies to many things in software development, including #testing and #infrastructure (incl. testing infrastructure)
Charity Majors@mipsytipsy
This is in response to my statement that senior engineer's job is to point out and amplify hidden costs. Not one time, but patiently, consistently, repeatedly.
English

@substars @mipsytipsy Yes, but oh my is the strain of disbelief hard on you as a person. Despite experience and the fact that they should know better when working on technology, “but that can’t happen”... is far too often spoken.
English

senior engineers need to see/amplify hidden costs in systems - such a simple/powerful idea from @mipsytipsy at #CodeFreeze2020
Minneapolis, MN 🇺🇸 English
miChou retweetledi
miChou retweetledi

I told this story unplanned and impulsively at code freeze, I may as well tell it here too.
It was deep in the dog days of last summer, our funding situation at its grimmest. I lay awake every night gnawing and fretting over whether we really had product market fit or not.
Andy Fleener@andyfleener
“It’s like a management virus it just takes over your brain” -@mipsytipsy on bad management motivation tricks #CodeFreeze2020
English











