I love a good "Things programmers believe about <X>" post. Opens your eyes a bit; expecting the unexpected is a good habit for an engineer to get into.

https://flightaware.engineering/falsehoods-programmers-believe-about-aviation/

#ThingsProgrammersBelieve #falsehoods #engineering #software

Falsehoods Programmers Believe About Aviation

There are a lot of assumptions one could make when designing data types and schemas for aviation data that turn out to be inaccurate. In the spirit of Patrick McKenzie’s classic piece on names, here are some false assumptions one might make about aviation.

Angle of Attack

Another Thing #Programmers Believe About Email... [*]

Email is instantaneous, or close enough. Verification links and codes sent via #email with 5-minute timeouts are perfectly fine, because no one's email is ever behind a higher-latency link than that, or has email that traverses multiple #hops, or that email #servers are ever #overloaded or #down for #maintenance.

[*] Or possibly Thing Product Managers Believe About Email

#ThingsProgrammersBelieve #ThingsProgrammersBelieveAboutEmail

On #software #development and #programmers ...

There are lots of writeups of the form "Things Programmers Believe About X" ... with X being names, addresses, phone numbers, time zones, postal codes, and any number of other pieces of information that are sloppily defined, or which vary greatly in format across different regions, in the real world, but which are commonly built into software systems.

They're all great. You should read them.

This is different.

1/x

#ThingsProgrammersBelieve

@kagan  

Additional #annoyances, some personal.

#People can have more than 1 middle #name.

People can have 0 middle names.

People can use a first #initial and a middle name, rather than the opposite.

Names can be #longer than 12 characters.

There's a great series of posts around the web "Things Programmers Believe About <X>" worth searching out. Names, phone numbers, addresses, ...

#ThingsProgrammersBelieve