Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
I love coding and what motivates me is problem-solving and preferably if it has an element of creativity.
I am a self-taught developer and work full-time as a front-end developer.
Location
Denmark 🇩🇰
Education
Bachelor in Nutrition and health (I know not super relevant to my current line of work!)
But we are not always writing the data or code with null ourselves.
One example: Auto-generated types made with GraphQL Code Generator.
We still need to be able to handle null.
Null does indeed make sense if you do not know if data will return empty.
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
I love coding and what motivates me is problem-solving and preferably if it has an element of creativity.
I am a self-taught developer and work full-time as a front-end developer.
Location
Denmark 🇩🇰
Education
Bachelor in Nutrition and health (I know not super relevant to my current line of work!)
Null is the worst code smell
And optional chaining, IMHO hids this antipattern.
I've written a smell on optional chaining. I will publish it in the following weeks
hackernoon.com/null-the-billion-do...
And optional chaining is another code smell
Code Smell 149 - Optional Chaining
Maxi Contieri ・ Jul 16 ・ 2 min read
But we are not always writing the data or code with null ourselves.
One example: Auto-generated types made with GraphQL Code Generator.
We still need to be able to handle null.
Null does indeed make sense if you do not know if data will return empty.
Of course
In case null is beyond your own control you need to deal with it
That is why it is the billion dollar mistake
We must be mature enough to avoid creating NEW nulls
Yeah, that makes sense 😄