By age 2, my kid didn't speak, cried a lot, couldn't fall asleep without being held for an hour, eating was problem, in fact everything was a problem. Doctors said he'd never speak and would need special care forever. 1/
It was a "child without a manual". We put in the work to write one. At home, in kindergarten, with therapists. We tried lots of experiments. Eg I invented a ball throwing game to teach him the words yes and no that we played for weeks until it clicked. 2/
Imagine being born with a perfectly capable brain, but the way you perceive the outside world is entirely different. Not wrong, just different, and the world doesn't accommodate for how you perceive it. 3/
He's 11 now, goes to regular school, and is gradually learning to eat more things (trying pizza last year was a huge victory!) He has two best friends who are also wonderful little humans. He likes to draw comics, programs little games, makes stop motion movies. 4/
He's funny, he likes to talk about history, and he is what I can only describe as a Minecraftologist. 5/
Some things are still hard, and will always be, partly because the world tries to fix people with autism, instead of accepting not everybody is alike. For many less privileged kids and adults it's a struggle. 6/
"Autism is not a disability, it's a different ability."
❤️ to everybody who struggles, and to everybody who tries to make it easier #WorldAutismAwarenessDay 7/7
PS You can help raise awareness in 2 easy steps: click here -> #WorldAutismAwarenessDay, then retweet anything you like
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I consulted for a client that acted as a broker for paying copyright holders for the use of their content. To do this, they figured out who the copyright holders of a work were. 3/
Bloggers: "I'll demonstrate DDD by building a Todo app"
Actual DDD: "We looked at how people are using Todo lists, and we figured that our model was wrong. Besides TODO and DONE, we needed to afford for POSTPONE, WON'T DO ANYWAY, and TOO LATE. A quick experiment showed that..."
For the record, please don't read that tweet as gatekeeping. By all means, write todo apps as a learning tool. Learn how to use patterns. But then go further. Think about your model. Can you find things that are hidden in if statements? Those might be indicators that...
Reposting this thread about the coffee room conversations where the software design conversations happen. (The thread's order was a little messed up, and I want to be easy to find.)
There is a fallacy about how domain modelling works, and we need to talk about it. With software design, you're not just solving problems, you can reframe the problem itself. 🧵 /1
The fallacy about domain modelling is that we can design software by discovering all the relevant concepts in the domain, turn them into concepts in our design, add some behaviours, and voilà, we’ve solved our problem. /3
I probably used the term monolith a bit liberally there. But imagine you have a large chunk of your system that is very complex, because it has to deal with something with a lot of variability, in this case, different ways of doing things in different countries.
Naive strategic design here is to separate by domain (billing, invoicing, debt collection). But Bounded Contexts don't need to align with subdomains. That separation is still complex because each context needs to know country-specific things.
This nonsense that tactical #DDDesign isn't important has to stop. It's not even an actual opinion anyone has given proper thought, it's just a fashionable meme people are parroting. None of your strategic design matters if nobody in your org can properly implement it.
If you think tactics don't matter, you might as well wear a t-shirt saying "Ivory tower architect 4 life".
(Yes I deliberately deployed one overused meme to battle the use of another, I'm a sly fox.)