No Need To Shout

That visceral internal reaction when your non-technical friend pitches their "revolutionary" app idea that's basically just Uber-but-for-dogwalkers and casually mentions "it should only take a weekend to build, right?" The face perfectly captures that split-second calculation of whether to explain that their "simple app" requires a database architecture, frontend framework, backend API, authentication system, payment processing, and six months of your life... or just smile politely while mentally running process.exit(1) .

Content Carla CodesCarla I saw a great movie about databases today - I can't wait for the SQL. 11:11 PM 17 Nov 20 Twitter Web App 276 Retweets 77 Quote Tweets 2,546 Likes 17

Content OUR SOL

Content STOP DOING AGILE SOFTWARE WAS NOT SUPPOSED TO BE SISYPHEAN YEARS OF PROGRAMS yet NO REAL-WORLD USE FOUND for a DAILY STANDUP Wanted to add features anyway for a laugh? We had a tool for that: It was called "WATERFALL" "Yes please give me UNFINISHED software. Please let me work INFINITY hours"- Statements dreamed up by the utterly Deranged LOOK at what Programmers have been demanding your Respect for all this time, with all the keyboards mice we built for them (This is REAL Programming, done by REAL Programmers): SCRUM PROCESS ????? ??????? ????????????????? "Hello I would like features please" They have played us for absolute fools

The tech world's most pointless debate that somehow causes more arguments than tabs vs spaces. Is it "day-ta" or "dah-ta"? The answer depends entirely on whether you went to school in the US or literally anywhere else on the planet. Liam's response is gold because your brain automatically reads both pronunciations differently in the same sentence. It's like that GIF/JIF war, except nobody's built an entire career around being pretentious about data pronunciation... yet. Fun fact: The Latin origin "datum" suggests "dah-ta" is technically more correct, but good luck explaining etymology to your PM during standup when they ask about the "day-ta pipeline."

Content Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, andor sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.