cxy

Senior quality Engineer | talks about product quality and Cypress | Make something out of nothing

[cxy @imycx]

I was born ten thousand, nine hundred and sixty days ago, and an average human lifespan is twenty nine thousand, two hundred days.

[cxy @imycx]

@chinafutureclub It really depends on where you go, there’s a ton of breakfast places open around 6am, it’s just coffee places open later in the morning

[cxy @imycx]

@XianyuLi @grok 总结这篇文章，给出根据这篇文章做出实际行动的建议

[alcaraz archive @alcarchive]

The amazing photographer Rachel Bach on IG: “I don't like to play favourites, but I think you'll understand when I say there's just something special about photographing Carlos. You never quite know what's coming next, but whether it's a dive, a slide or a roar, it's pretty magical to capture. Career slam."

[cxy @imycx]

@Jacobsklug @lovable build, thanks for sharing

[Shane Levine @theShaneLevine]

How an iPhone wallpaper paid my rent for a year

here's the story 👇

[cxy @imycx]

“The best life is the one in which the creative impulses play the largest part and the possessive impulses the smallest.”
— ​Bertrand Russell​

via the 5-Bullet Friday newsletter (https://t.co/haChxnKu0w) from @tferriss

[Amanda Natividad @amandanat]

This Craigslist ad for a 1999 Toyota Corolla is a masterclass in copywriting.

[Artem Zakharchenko @kettanaito]

Here's the truth about TDD (Test Driven Development).

It's a broken practice. It's always been broken. It's broken by the definition of it. Its biggest merit is the encouragement of testing but that's about where it ends.

TDD implies writing tests before writing the code. So, what's broken about this, Artem? You write tests to describe the intention behind the system—how you expect it to behave. TDD heavily implies that you should know how the system behaves before even implementing it. You should know what you're doing.

Most of the time you don't. All the developers I know don't know that ahead of time. I don't know that ahead of time. In fact, I can spend days experimenting, writing an MVP, until I even begin to grasp what parts of my system should be and what I expect from them.

I don't see TDD as a viable approach in fast-evolving systems, like the web. It may make significantly more sense when writing systematic software where very little changes from project to project. That's the complete opposite of what you write on the web.

The negative aspect of TDD is that I've seen teams discouraged if they fail to follow it. And so they give up on the whole idea of testing since TDD is so universally associated with it. Instead of encouraging people to test and showing them that testing software can be fun, the practice locks them in pedantic constraints that no engineer can follow.

I don't follow TDD. It doesn't mean I don't write tests. I write a lot of tests. What I do is Prototype-Iterate-Test development.

Prototype. I give my ideas some room and let them breathe without caring too much about testing at first. I experiment, move things, break things, put myself in my user's shoes and design the API, behaviors, and expectations. As I said, this can take some time.

Iterate. I take that time to make sure my system makes sense and satisfies the requirements toward it (which, by themselves, may evolve and change why I do this).

Test. Finally, I write the tests. It's become an inseparable part of my workflow. I cannot imagine not writing tests.

There are exceptions, of course. If I'm writing a simple I/O function, it doesn't need a day of work to understand what it does because that's all it will ever do. I may write some unit tests for it from the start. But the majority of my (and I'm sure yours too) work are not simple functions. It's complex logic that takes time to get right. If I follow TDD faithfully, I will be wasting my time writing tests that I will, eventually, throw away. Those are not useful and they'd help me not to gain confidence in what I'm building.

Don't be discouraged. Adopt the practices that work for you (even if it's TDD, as long as you are not lying to yourself!). The important thing is that testing matters. It always did. Developers have been testing software since the 80s, I believe. You should too! I will do my best to show you that testing can be accessible and fun.

[cxy @imycx]

🤯

[Corey Lynch @coreylynch]

We are now having full conversations with Figure 01, thanks to our partnership with OpenAI.

Our robot can:
- describe its visual experience
- plan future actions
- reflect on its memory
- explain its reasoning verbally
Technical deep-dive 🧵:

[cxy @imycx]

@kettanaito 1. how much effort should be in development vs. writing automated testing ? any good strategy on balancing them?
2. what's the best way to test async api?
3. do you think in the future QA role can be obsolete from having developers writing automated tests?

[cxy @imycx]

@ShaanVP This episode was absolutely bonkers!

[cxy @imycx]

@pwang_szn what's the best solution to this? PHP?

[cxy @imycx]

@rrmdp @levelsio Congrats @rrmdp ! Love the simple ideas

[cxy @imycx]

@Swizec @chrismunns these lights make me wake up faster during dark days

[cxy @imycx]

@SahilBloom beast

[cxy @imycx]

@suryasanchez1 @levelsio probably on a snowboard rather than ski 😆

[cxy @imycx]

@dhh question: can I pay to sign up for Tada List now? :)

[cxy @imycx]

@bearliu 干货 转发以后慢慢读

[Bear Liu @bearliu]

最近我认真学习了由AI领域的知名专家吴恩达博士（Andrew Ng）制作的课程《Generative AI for Everyone》。学完这门课程后，我总结了九个对我而言极具价值的知识点，本贴旨在分享这些收获，并为自己留下一份学习存档。

说明：强烈推荐有兴趣的朋友投入一点时间，直接去深入学习吴博士的这门课程。课程内容丰富，全免费，在deeplearning的网站就有，有中文字幕，非常容易理解。我的分享只是作为导读，真正的学习还是要亲自去体验。