Top Trending LinkedIn Posts about tdd

TDD (Test Driven Development) is not a *practice* but rather I'd say a "process"

- to put yourselves in a customer's shoe and

TDD is the best way to build software.

And for those who confuse TDD with automated testing, I'm talking about writing the tests before

TDD is the best way to build software.

And for those who confuse TDD with automated testing, I'm talking about writing the tests before

TDDR; (Too deep, don’t read).

Notes from the frontline of burnout.

-

Do those who thrive spend time staring at screens?

Do those who thrive

"TDD in a SwiftUI World" live-coding will be back this Sunday! 9:30am Pacific (16:30 UTC) for roughly 1 hour. This time, let's improve

TDD stands for...


Wrong answers only 🤔

TDD, BDD, DDD, SOLID, DRY, KISS, and So on!

This list will never end and you can easily overcomplicate your projects.

These

TDD Stands for...?


Wrong answers only ;)

TDD is an absolute requirement for all software development!!

Who wouldn't Test During Deployment?

TDD is for old people.

When I was young, I had the entire code base in my brain.

Now I use TDD.

TDD fanatics crack me up 😂

They're just like TypeScript fanatics, or any other "right" way of doing stuff fanatic

Say you don't like something

TDD: Testes ou Especificações Executáveis?

No desenvolvimento de software, o Test-Driven Development (TDD) é uma abordagem que preconiza escrever testes antes mesmo da implementação

I have no cheeky or controversial TDD posts planned for today.

But Monday on the other hand...

Daniel Moka 👀

Ad-Free Friday and this week... it's all about TDD 👇

🔍 The Pitfall of Writing Tests After Development

Writing tests after code implementation can lead to embedding bugs within tests themselves. This practice often

TDD slows you down?! It's because of you, not TDD.

TDD makes you faster if you do it well.

But to experience the sweetness, you

TDD par ci, TDD par là... Voilà maintenant t'as plus aucune excuse pour parler de TDD sans savoir ce que c'est réellement !

Connaissant

Does it feel pointless doing TDD when you have a QA department?

Are your user acceptance criteria completely out of whack with your engineering

I sometimes hear people refuting TDD on account of DHH being against it. They forget that Rails creator is focused on implementation details

Do you have difficulty in talking about the benefits of test-driven development with others? Or simply how it works?

That's why I created "JitterTed's

If you had a qualified instructor show you how to do TDD properly but you still cannot find the way to apply it

I started my career dreading test-writing.

Testing felt like "eugh!"
TDD felt like "YUCK!"

Ironically, the dread was architectural:
Legacy code.

There was nothing wrong with my ability

TDD, PRs, Remote Working, AI, Microservices: all tech LinkedIn can talk about.

Over and over and over.

Boring.

The last few months of my LinkedIn feed were all ‘no to TDD’ and ‘no to overengineering’.

But today, everybody is a software quality

TDD vs. BDD: Which Approach is Right for Your Project?
In the world of Agile development, Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are

TDD - Test Driven Development is a Requirements Discovery Practice

Too many people think TDD - Test Driven Development - is there to assure

TDD mérite il qu’autant de pixel lui soit dédié sur les réseaux ?

Moi je pense pas, mais ça fait réagir du monde

TDD in legacy code seems impossible. The theory is simple, you read books, you watched courses, you tried applying it to the legacy

TDD is programming hygiene. It keeps the code orderly while supporting incremental and iterative development with continuous integration.

All of these behaviors would be

TDD is Prompt Engineering.

We're writing a description of how we expect the system to behave for us.

- Red Light => Not there yet.