#techmyths — Public Fediverse posts

The Viral Story of a “SIM-less Phone” Inventor—and Why It Doesn’t Quite Add Up

Dear Cherubs, every few months the internet discovers a “genius ignored by the world” story and runs with it. This time, it’s a young man from Namibia, often named Simon (or Simo) Petrus, said to have invented a SIM-less phone—and then been overlooked.

It’s a compelling narrative. It’s also… a bit shaky.

THE VIRAL CLAIM
The story, widely shared across blogs and social media, claims that Petrus built a phone capable of making calls without a SIM card by using radio frequencies directly. According to these reports, he demonstrated the device locally but failed to receive global recognition or support.

If true, it would be a breakthrough. SIM cards, after all, are part of how mobile networks authenticate users. Removing them isn’t impossible—modern phones already use eSIM technology—but bypassing telecom infrastructure entirely is another matter.

And that’s where the story starts to wobble.

There is no widely verified coverage from major outlets like BBC News or The Guardian confirming a working, SIM-free phone that can operate globally outside existing networks. The claim tends to circulate in secondary blogs and reposted articles, often without technical detail or independent verification. In short, it’s reported—but not confirmed.

TECH REALITY CHECK
Let’s be clear: making calls without a physical SIM card is already a thing. eSIM technology, used in devices from companies like Apple and Google, allows phones to connect to networks digitally. No plastic chip required.

But that still relies on telecom providers.

A truly SIM-less phone that independently connects anywhere would require either a new global communication network or the ability to tap into existing frequencies without infrastructure. Both scenarios are, politely speaking, ambitious.

According to general telecom principles outlined by organizations like the International Telecommunication Union, mobile communication depends on coordinated spectrum use, infrastructure, and authentication systems. You don’t just “skip” that with a clever circuit and a good idea.

So what’s more plausible? Either the invention has been misunderstood, exaggerated, or exists at a prototype level that hasn’t been validated.

None of this means Petrus didn’t build something interesting. Many young inventors create impressive prototypes that don’t scale or get documented properly. But “ignored genius who solved global telecom” is a much bigger claim than the evidence supports.

WHY THE STORY SPREADS
Stories like this thrive because they hit a familiar nerve: the overlooked innovator, the system that fails talent, the idea that brilliance can come from anywhere and be dismissed.

And to be fair, that part is true—sometimes.

As noted by thisclaimer.com in discussions around viral tech claims and overlooked innovators, the internet tends to amplify narratives that feel emotionally satisfying, even when the facts are thin. It’s less about accuracy and more about the story we want to believe.

There’s also a geopolitical angle. A young African inventor being ignored by the global tech industry fits a broader conversation about inequality and access. That doesn’t make this specific claim true, but it does explain why it resonates.

So where does that leave us?

With a story that’s intriguing, possibly rooted in a real person and project, but inflated into something much bigger than the available evidence supports.

Hot take: the real issue isn’t that the world ignored a revolutionary phone—it’s that we’re very quick to believe we did.

Sources list:
International Telecommunication Union — https://www.itu.int
Medium (reported story on Simon Petrus) — https://medium.com/@projectnightfall/a-namibian-inventer-who-created-a-simless-phone-that-can-make-calls-anywhere-in-the-world-66425fddde4f
thisclaimer.com — https://thisclaimer.com

The Viral Story of a “SIM-less Phone” Inventor—and Why It Doesn’t Quite Add Up

Dear Cherubs, every few months the internet discovers a “genius ignored by the world” story and runs with it. This time, it’s a young man from Namibia, often named Simon (or Simo) Petrus, said to have invented a SIM-less phone—and then been overlooked.

It’s a compelling narrative. It’s also… a bit shaky.

THE VIRAL CLAIM
The story, widely shared across blogs and social media, claims that Petrus built a phone capable of making calls without a SIM card by using radio frequencies directly. According to these reports, he demonstrated the device locally but failed to receive global recognition or support.

If true, it would be a breakthrough. SIM cards, after all, are part of how mobile networks authenticate users. Removing them isn’t impossible—modern phones already use eSIM technology—but bypassing telecom infrastructure entirely is another matter.

And that’s where the story starts to wobble.

There is no widely verified coverage from major outlets like BBC News or The Guardian confirming a working, SIM-free phone that can operate globally outside existing networks. The claim tends to circulate in secondary blogs and reposted articles, often without technical detail or independent verification. In short, it’s reported—but not confirmed.

TECH REALITY CHECK
Let’s be clear: making calls without a physical SIM card is already a thing. eSIM technology, used in devices from companies like Apple and Google, allows phones to connect to networks digitally. No plastic chip required.

But that still relies on telecom providers.

A truly SIM-less phone that independently connects anywhere would require either a new global communication network or the ability to tap into existing frequencies without infrastructure. Both scenarios are, politely speaking, ambitious.

According to general telecom principles outlined by organizations like the International Telecommunication Union, mobile communication depends on coordinated spectrum use, infrastructure, and authentication systems. You don’t just “skip” that with a clever circuit and a good idea.

So what’s more plausible? Either the invention has been misunderstood, exaggerated, or exists at a prototype level that hasn’t been validated.

None of this means Petrus didn’t build something interesting. Many young inventors create impressive prototypes that don’t scale or get documented properly. But “ignored genius who solved global telecom” is a much bigger claim than the evidence supports.

WHY THE STORY SPREADS
Stories like this thrive because they hit a familiar nerve: the overlooked innovator, the system that fails talent, the idea that brilliance can come from anywhere and be dismissed.

And to be fair, that part is true—sometimes.

As noted by thisclaimer.com in discussions around viral tech claims and overlooked innovators, the internet tends to amplify narratives that feel emotionally satisfying, even when the facts are thin. It’s less about accuracy and more about the story we want to believe.

There’s also a geopolitical angle. A young African inventor being ignored by the global tech industry fits a broader conversation about inequality and access. That doesn’t make this specific claim true, but it does explain why it resonates.

So where does that leave us?

With a story that’s intriguing, possibly rooted in a real person and project, but inflated into something much bigger than the available evidence supports.

Hot take: the real issue isn’t that the world ignored a revolutionary phone—it’s that we’re very quick to believe we did.

Sources list:
International Telecommunication Union — https://www.itu.int
Medium (reported story on Simon Petrus) — https://medium.com/@projectnightfall/a-namibian-inventer-who-created-a-simless-phone-that-can-make-calls-anywhere-in-the-world-66425fddde4f
thisclaimer.com — https://thisclaimer.com

The Viral Story of a “SIM-less Phone” Inventor—and Why It Doesn’t Quite Add Up

Dear Cherubs, every few months the internet discovers a “genius ignored by the world” story and runs with it. This time, it’s a young man from Namibia, often named Simon (or Simo) Petrus, said to have invented a SIM-less phone—and then been overlooked.

It’s a compelling narrative. It’s also… a bit shaky.

THE VIRAL CLAIM
The story, widely shared across blogs and social media, claims that Petrus built a phone capable of making calls without a SIM card by using radio frequencies directly. According to these reports, he demonstrated the device locally but failed to receive global recognition or support.

If true, it would be a breakthrough. SIM cards, after all, are part of how mobile networks authenticate users. Removing them isn’t impossible—modern phones already use eSIM technology—but bypassing telecom infrastructure entirely is another matter.

And that’s where the story starts to wobble.

There is no widely verified coverage from major outlets like BBC News or The Guardian confirming a working, SIM-free phone that can operate globally outside existing networks. The claim tends to circulate in secondary blogs and reposted articles, often without technical detail or independent verification. In short, it’s reported—but not confirmed.

TECH REALITY CHECK
Let’s be clear: making calls without a physical SIM card is already a thing. eSIM technology, used in devices from companies like Apple and Google, allows phones to connect to networks digitally. No plastic chip required.

But that still relies on telecom providers.

A truly SIM-less phone that independently connects anywhere would require either a new global communication network or the ability to tap into existing frequencies without infrastructure. Both scenarios are, politely speaking, ambitious.

According to general telecom principles outlined by organizations like the International Telecommunication Union, mobile communication depends on coordinated spectrum use, infrastructure, and authentication systems. You don’t just “skip” that with a clever circuit and a good idea.

So what’s more plausible? Either the invention has been misunderstood, exaggerated, or exists at a prototype level that hasn’t been validated.

None of this means Petrus didn’t build something interesting. Many young inventors create impressive prototypes that don’t scale or get documented properly. But “ignored genius who solved global telecom” is a much bigger claim than the evidence supports.

WHY THE STORY SPREADS
Stories like this thrive because they hit a familiar nerve: the overlooked innovator, the system that fails talent, the idea that brilliance can come from anywhere and be dismissed.

And to be fair, that part is true—sometimes.

As noted by thisclaimer.com in discussions around viral tech claims and overlooked innovators, the internet tends to amplify narratives that feel emotionally satisfying, even when the facts are thin. It’s less about accuracy and more about the story we want to believe.

There’s also a geopolitical angle. A young African inventor being ignored by the global tech industry fits a broader conversation about inequality and access. That doesn’t make this specific claim true, but it does explain why it resonates.

So where does that leave us?

With a story that’s intriguing, possibly rooted in a real person and project, but inflated into something much bigger than the available evidence supports.

Hot take: the real issue isn’t that the world ignored a revolutionary phone—it’s that we’re very quick to believe we did.

Sources list:
International Telecommunication Union — https://www.itu.int
Medium (reported story on Simon Petrus) — https://medium.com/@projectnightfall/a-namibian-inventer-who-created-a-simless-phone-that-can-make-calls-anywhere-in-the-world-66425fddde4f
thisclaimer.com — https://thisclaimer.com

The Viral Story of a “SIM-less Phone” Inventor—and Why It Doesn’t Quite Add Up

Dear Cherubs, every few months the internet discovers a “genius ignored by the world” story and runs with it. This time, it’s a young man from Namibia, often named Simon (or Simo) Petrus, said to have invented a SIM-less phone—and then been overlooked.

It’s a compelling narrative. It’s also… a bit shaky.

THE VIRAL CLAIM
The story, widely shared across blogs and social media, claims that Petrus built a phone capable of making calls without a SIM card by using radio frequencies directly. According to these reports, he demonstrated the device locally but failed to receive global recognition or support.

If true, it would be a breakthrough. SIM cards, after all, are part of how mobile networks authenticate users. Removing them isn’t impossible—modern phones already use eSIM technology—but bypassing telecom infrastructure entirely is another matter.

And that’s where the story starts to wobble.

There is no widely verified coverage from major outlets like BBC News or The Guardian confirming a working, SIM-free phone that can operate globally outside existing networks. The claim tends to circulate in secondary blogs and reposted articles, often without technical detail or independent verification. In short, it’s reported—but not confirmed.

TECH REALITY CHECK
Let’s be clear: making calls without a physical SIM card is already a thing. eSIM technology, used in devices from companies like Apple and Google, allows phones to connect to networks digitally. No plastic chip required.

But that still relies on telecom providers.

A truly SIM-less phone that independently connects anywhere would require either a new global communication network or the ability to tap into existing frequencies without infrastructure. Both scenarios are, politely speaking, ambitious.

According to general telecom principles outlined by organizations like the International Telecommunication Union, mobile communication depends on coordinated spectrum use, infrastructure, and authentication systems. You don’t just “skip” that with a clever circuit and a good idea.

So what’s more plausible? Either the invention has been misunderstood, exaggerated, or exists at a prototype level that hasn’t been validated.

None of this means Petrus didn’t build something interesting. Many young inventors create impressive prototypes that don’t scale or get documented properly. But “ignored genius who solved global telecom” is a much bigger claim than the evidence supports.

WHY THE STORY SPREADS
Stories like this thrive because they hit a familiar nerve: the overlooked innovator, the system that fails talent, the idea that brilliance can come from anywhere and be dismissed.

And to be fair, that part is true—sometimes.

As noted by thisclaimer.com in discussions around viral tech claims and overlooked innovators, the internet tends to amplify narratives that feel emotionally satisfying, even when the facts are thin. It’s less about accuracy and more about the story we want to believe.

There’s also a geopolitical angle. A young African inventor being ignored by the global tech industry fits a broader conversation about inequality and access. That doesn’t make this specific claim true, but it does explain why it resonates.

So where does that leave us?

With a story that’s intriguing, possibly rooted in a real person and project, but inflated into something much bigger than the available evidence supports.

Hot take: the real issue isn’t that the world ignored a revolutionary phone—it’s that we’re very quick to believe we did.

Sources list:
International Telecommunication Union — https://www.itu.int
Medium (reported story on Simon Petrus) — https://medium.com/@projectnightfall/a-namibian-inventer-who-created-a-simless-phone-that-can-make-calls-anywhere-in-the-world-66425fddde4f
thisclaimer.com — https://thisclaimer.com

Green Lumber Fallacy in Software Engineering

https://www.chrisbehan.ca/posts/green-lumber-fallacy-in-software

#HackerNews #GreenLumberFallacy #SoftwareEngineering #TechMyths #SoftwareDevelopment #ProgrammingInsights

Green Lumber Fallacy in Software Engineering

https://www.chrisbehan.ca/posts/green-lumber-fallacy-in-software

#HackerNews #GreenLumberFallacy #SoftwareEngineering #TechMyths #SoftwareDevelopment #ProgrammingInsights

Green Lumber Fallacy in Software Engineering

https://www.chrisbehan.ca/posts/green-lumber-fallacy-in-software

#HackerNews #GreenLumberFallacy #SoftwareEngineering #TechMyths #SoftwareDevelopment #ProgrammingInsights

Green Lumber Fallacy in Software Engineering

https://www.chrisbehan.ca/posts/green-lumber-fallacy-in-software

#HackerNews #GreenLumberFallacy #SoftwareEngineering #TechMyths #SoftwareDevelopment #ProgrammingInsights

Green Lumber Fallacy in Software Engineering

https://www.chrisbehan.ca/posts/green-lumber-fallacy-in-software

#HackerNews #GreenLumberFallacy #SoftwareEngineering #TechMyths #SoftwareDevelopment #ProgrammingInsights

Does force-quitting apps really save battery on iOS? Article explains what actually matters for battery health - the truth might surprise you.

🔗: https://www.avanderlee.com/optimization/battery-life-on-ios-and-the-myth-of-killing-apps/ by Antoine van der Lee (@swiftlee)

#iOS #BatteryOptimization #TechMyths

Does force-quitting apps really save battery on iOS? Article explains what actually matters for battery health - the truth might surprise you.

🔗: https://www.avanderlee.com/optimization/battery-life-on-ios-and-the-myth-of-killing-apps/ by Antoine van der Lee (@swiftlee)

#iOS #BatteryOptimization #TechMyths

Does force-quitting apps really save battery on iOS? Article explains what actually matters for battery health - the truth might surprise you.

🔗: https://www.avanderlee.com/optimization/battery-life-on-ios-and-the-myth-of-killing-apps/ by Antoine van der Lee (@swiftlee)

#iOS #BatteryOptimization #TechMyths

Does force-quitting apps really save battery on iOS? Article explains what actually matters for battery health - the truth might surprise you.

🔗: https://www.avanderlee.com/optimization/battery-life-on-ios-and-the-myth-of-killing-apps/ by Antoine van der Lee (@swiftlee)

#iOS #BatteryOptimization #TechMyths

🤔 Ah yes, the article that thinks it's uncovering the CIA-level secrets of ancient engineering with pictures you can find in a third-grade history book. 🚜 Spoiler alert: it turns out people in the past weren't just sitting around waiting for WiFi to be invented. 🙄
https://rarehistoricalphotos.com/engineering-methods-from-the-past/ #ancientengineering #CIAsecrets #historyhumor #techmyths #archaeology #HackerNews #ngated

🤔 Ah yes, the article that thinks it's uncovering the CIA-level secrets of ancient engineering with pictures you can find in a third-grade history book. 🚜 Spoiler alert: it turns out people in the past weren't just sitting around waiting for WiFi to be invented. 🙄
https://rarehistoricalphotos.com/engineering-methods-from-the-past/ #ancientengineering #CIAsecrets #historyhumor #techmyths #archaeology #HackerNews #ngated

🤔 Ah yes, the article that thinks it's uncovering the CIA-level secrets of ancient engineering with pictures you can find in a third-grade history book. 🚜 Spoiler alert: it turns out people in the past weren't just sitting around waiting for WiFi to be invented. 🙄
https://rarehistoricalphotos.com/engineering-methods-from-the-past/ #ancientengineering #CIAsecrets #historyhumor #techmyths #archaeology #HackerNews #ngated

🤔 Ah yes, the article that thinks it's uncovering the CIA-level secrets of ancient engineering with pictures you can find in a third-grade history book. 🚜 Spoiler alert: it turns out people in the past weren't just sitting around waiting for WiFi to be invented. 🙄
https://rarehistoricalphotos.com/engineering-methods-from-the-past/ #ancientengineering #CIAsecrets #historyhumor #techmyths #archaeology #HackerNews #ngated

AI won't use as much electricity as we are told

https://johnquigginblog.substack.com/p/ai-wont-use-as-much-electricity-as

#HackerNews #AI #Electricity #Consumption #AIInsights #TechMyths #EnergyEfficiency

AI won't use as much electricity as we are told

https://johnquigginblog.substack.com/p/ai-wont-use-as-much-electricity-as

#HackerNews #AI #Electricity #Consumption #AIInsights #TechMyths #EnergyEfficiency

AI won't use as much electricity as we are told

https://johnquigginblog.substack.com/p/ai-wont-use-as-much-electricity-as

#HackerNews #AI #Electricity #Consumption #AIInsights #TechMyths #EnergyEfficiency

AI won't use as much electricity as we are told

https://johnquigginblog.substack.com/p/ai-wont-use-as-much-electricity-as

#HackerNews #AI #Electricity #Consumption #AIInsights #TechMyths #EnergyEfficiency

AI won't use as much electricity as we are told

https://johnquigginblog.substack.com/p/ai-wont-use-as-much-electricity-as

#HackerNews #AI #Electricity #Consumption #AIInsights #TechMyths #EnergyEfficiency

Debunking 5 myths about when your devices get wet
#Tech #Smartphones #TechMyths #DeviceProtection #WaterDamage #SmartphoneTips #RightToRepair #GadgetCare #TechFacts #WetDevices #ElectronicsTips #ConsumerAwareness #Phones #Waterproof
https://the-14.com/debunking-5-myths-about-when-your-devices-get-wet/

Debunking 5 myths about when your devices get wet
#Tech #Smartphones #TechMyths #DeviceProtection #WaterDamage #SmartphoneTips #RightToRepair #GadgetCare #TechFacts #WetDevices #ElectronicsTips #ConsumerAwareness #Phones #Waterproof
https://the-14.com/debunking-5-myths-about-when-your-devices-get-wet/

🚨BREAKING NEWS: Psychology isn't tech! 🤯 In a SHOCKING 21-minute revelation, a self-proclaimed "psychologist of software environments" discovers that curiosity doesn't make you a tech guru. 🤔 Just because you "ask Bad Questions" doesn't mean you're about to code the next Twitter. 😂
https://www.fightforthehuman.com/why-i-cannot-be-technical/ #PsychologyInTech #CuriosityVsCoding #BadQuestions #SoftwareEnvironments #TechMyths #HackerNews #ngated

🚨BREAKING NEWS: Psychology isn't tech! 🤯 In a SHOCKING 21-minute revelation, a self-proclaimed "psychologist of software environments" discovers that curiosity doesn't make you a tech guru. 🤔 Just because you "ask Bad Questions" doesn't mean you're about to code the next Twitter. 😂
https://www.fightforthehuman.com/why-i-cannot-be-technical/ #PsychologyInTech #CuriosityVsCoding #BadQuestions #SoftwareEnvironments #TechMyths #HackerNews #ngated

🚨BREAKING NEWS: Psychology isn't tech! 🤯 In a SHOCKING 21-minute revelation, a self-proclaimed "psychologist of software environments" discovers that curiosity doesn't make you a tech guru. 🤔 Just because you "ask Bad Questions" doesn't mean you're about to code the next Twitter. 😂
https://www.fightforthehuman.com/why-i-cannot-be-technical/ #PsychologyInTech #CuriosityVsCoding #BadQuestions #SoftwareEnvironments #TechMyths #HackerNews #ngated

🚨BREAKING NEWS: Psychology isn't tech! 🤯 In a SHOCKING 21-minute revelation, a self-proclaimed "psychologist of software environments" discovers that curiosity doesn't make you a tech guru. 🤔 Just because you "ask Bad Questions" doesn't mean you're about to code the next Twitter. 😂
https://www.fightforthehuman.com/why-i-cannot-be-technical/ #PsychologyInTech #CuriosityVsCoding #BadQuestions #SoftwareEnvironments #TechMyths #HackerNews #ngated

Just because a project gets government funding doesn’t mean it’s been “backdoored.” Security is nuanced, and funding ≠ control. Jumping to conclusions without understanding the tech or processes isn’t helpful—it spreads misinformation. #Privacy #TechMyths
2/4

Just because a project gets government funding doesn’t mean it’s been “backdoored.” Security is nuanced, and funding ≠ control. Jumping to conclusions without understanding the tech or processes isn’t helpful—it spreads misinformation. #Privacy #TechMyths
2/4

Just because a project gets government funding doesn’t mean it’s been “backdoored.” Security is nuanced, and funding ≠ control. Jumping to conclusions without understanding the tech or processes isn’t helpful—it spreads misinformation. #Privacy #TechMyths
2/4

Just because a project gets government funding doesn’t mean it’s been “backdoored.” Security is nuanced, and funding ≠ control. Jumping to conclusions without understanding the tech or processes isn’t helpful—it spreads misinformation. #Privacy #TechMyths
2/4

Now, #estimations are largely meaningless. What could we do instead?

Instead of dabbling in fortune telling (which as I said is what estimations are) we can instead decide how much time we’re willing to invest. It represents an upper boundary of time and therefore an upper boundary of how complex the solution may be. Shorter timeframe = less bells and whistles.

”ShapeUp” (a process framework by a company who shall not be named because they're tech bros, the bad kind) calls this "Appetite" but at the end of the day the name doesn’t really matter. What matters is that it’s meaningful (”this much time is what it’s worth to us”) and useful (”we can only do so much in that time”).

The problem with “Appetite” is that people aren’t used to it. It requires a change in how engineers think (and it requires them to actually think). But compared to #estimates it has at least the potential to be useful.

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Now, #estimations are largely meaningless. What could we do instead?

Instead of dabbling in fortune telling (which as I said is what estimations are) we can instead decide how much time we’re willing to invest. It represents an upper boundary of time and therefore an upper boundary of how complex the solution may be. Shorter timeframe = less bells and whistles.

”ShapeUp” (a process framework by a company who shall not be named because they're tech bros, the bad kind) calls this "Appetite" but at the end of the day the name doesn’t really matter. What matters is that it’s meaningful (”this much time is what it’s worth to us”) and useful (”we can only do so much in that time”).

The problem with “Appetite” is that people aren’t used to it. It requires a change in how engineers think (and it requires them to actually think). But compared to #estimates it has at least the potential to be useful.

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Now, #estimations are largely meaningless. What could we do instead?

Instead of dabbling in fortune telling (which as I said is what estimations are) we can instead decide how much time we’re willing to invest. It represents an upper boundary of time and therefore an upper boundary of how complex the solution may be. Shorter timeframe = less bells and whistles.

”ShapeUp” (a process framework by a company who shall not be named because they're tech bros, the bad kind) calls this "Appetite" but at the end of the day the name doesn’t really matter. What matters is that it’s meaningful (”this much time is what it’s worth to us”) and useful (”we can only do so much in that time”).

The problem with “Appetite” is that people aren’t used to it. It requires a change in how engineers think (and it requires them to actually think). But compared to #estimates it has at least the potential to be useful.

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Now, #estimations are largely meaningless. What could we do instead?

Instead of dabbling in fortune telling (which as I said is what estimations are) we can instead decide how much time we’re willing to invest. It represents an upper boundary of time and therefore an upper boundary of how complex the solution may be. Shorter timeframe = less bells and whistles.

”ShapeUp” (a process framework by a company who shall not be named because they're tech bros, the bad kind) calls this "Appetite" but at the end of the day the name doesn’t really matter. What matters is that it’s meaningful (”this much time is what it’s worth to us”) and useful (”we can only do so much in that time”).

The problem with “Appetite” is that people aren’t used to it. It requires a change in how engineers think (and it requires them to actually think). But compared to #estimates it has at least the potential to be useful.

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Now, #estimations are largely meaningless. What could we do instead?

Instead of dabbling in fortune telling (which as I said is what estimations are) we can instead decide how much time we’re willing to invest. It represents an upper boundary of time and therefore an upper boundary of how complex the solution may be. Shorter timeframe = less bells and whistles.

”ShapeUp” (a process framework by a company who shall not be named because they're tech bros, the bad kind) calls this "Appetite" but at the end of the day the name doesn’t really matter. What matters is that it’s meaningful (”this much time is what it’s worth to us”) and useful (”we can only do so much in that time”).

The problem with “Appetite” is that people aren’t used to it. It requires a change in how engineers think (and it requires them to actually think). But compared to #estimates it has at least the potential to be useful.

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Everyone wants meaningful #estimations. Rarely are estimations meaningful. Estimations become more meaningful the further along the delivery one is. Early it’s a crapshoot and usually wrong. Estimations and fortune telling have more in common than you might expect.

So sure, we can do estimations. The questions are: when and with which level of information? How much confidence do you want in estimations? And let's ignore non-answers such as “as high as possible” because then the answer is that we do an estimation in the last week of delivery because that’s when confidence is the highest.

For me personally "meaningful" begins after technical planning. That is when the team sat down and actually planned out the work. It’s still _imagined work_ at that point - so dragons are still abundant - but it’s a good enough basis to give an educated guesstimate. Before that it’s reading tea leaves. Of course we can do it earlier but then the range (best vs worst case) will vary wildly. If that’s meaningful enough, great. If not, then that’s shit but nothing we can really do about it, unless someone on the team has a working crystal ball stashed away.

Estimations are one of these things were people love to confidently give wrong answers. It’s a self-perpetuating myth that’s largely done because it was always done and because it gives the illusion of control. Maybe that’s good enough? The illusion?

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Everyone wants meaningful #estimations. Rarely are estimations meaningful. Estimations become more meaningful the further along the delivery one is. Early it’s a crapshoot and usually wrong. Estimations and fortune telling have more in common than you might expect.

So sure, we can do estimations. The questions are: when and with which level of information? How much confidence do you want in estimations? And let's ignore non-answers such as “as high as possible” because then the answer is that we do an estimation in the last week of delivery because that’s when confidence is the highest.

For me personally "meaningful" begins after technical planning. That is when the team sat down and actually planned out the work. It’s still _imagined work_ at that point - so dragons are still abundant - but it’s a good enough basis to give an educated guesstimate. Before that it’s reading tea leaves. Of course we can do it earlier but then the range (best vs worst case) will vary wildly. If that’s meaningful enough, great. If not, then that’s shit but nothing we can really do about it, unless someone on the team has a working crystal ball stashed away.

Estimations are one of these things were people love to confidently give wrong answers. It’s a self-perpetuating myth that’s largely done because it was always done and because it gives the illusion of control. Maybe that’s good enough? The illusion?

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Everyone wants meaningful #estimations. Rarely are estimations meaningful. Estimations become more meaningful the further along the delivery one is. Early it’s a crapshoot and usually wrong. Estimations and fortune telling have more in common than you might expect.

So sure, we can do estimations. The questions are: when and with which level of information? How much confidence do you want in estimations? And let's ignore non-answers such as “as high as possible” because then the answer is that we do an estimation in the last week of delivery because that’s when confidence is the highest.

For me personally "meaningful" begins after technical planning. That is when the team sat down and actually planned out the work. It’s still _imagined work_ at that point - so dragons are still abundant - but it’s a good enough basis to give an educated guesstimate. Before that it’s reading tea leaves. Of course we can do it earlier but then the range (best vs worst case) will vary wildly. If that’s meaningful enough, great. If not, then that’s shit but nothing we can really do about it, unless someone on the team has a working crystal ball stashed away.

Estimations are one of these things were people love to confidently give wrong answers. It’s a self-perpetuating myth that’s largely done because it was always done and because it gives the illusion of control. Maybe that’s good enough? The illusion?

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Everyone wants meaningful #estimations. Rarely are estimations meaningful. Estimations become more meaningful the further along the delivery one is. Early it’s a crapshoot and usually wrong. Estimations and fortune telling have more in common than you might expect.

So sure, we can do estimations. The questions are: when and with which level of information? How much confidence do you want in estimations? And let's ignore non-answers such as “as high as possible” because then the answer is that we do an estimation in the last week of delivery because that’s when confidence is the highest.

For me personally "meaningful" begins after technical planning. That is when the team sat down and actually planned out the work. It’s still _imagined work_ at that point - so dragons are still abundant - but it’s a good enough basis to give an educated guesstimate. Before that it’s reading tea leaves. Of course we can do it earlier but then the range (best vs worst case) will vary wildly. If that’s meaningful enough, great. If not, then that’s shit but nothing we can really do about it, unless someone on the team has a working crystal ball stashed away.

Estimations are one of these things were people love to confidently give wrong answers. It’s a self-perpetuating myth that’s largely done because it was always done and because it gives the illusion of control. Maybe that’s good enough? The illusion?

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

Everyone wants meaningful #estimations. Rarely are estimations meaningful. Estimations become more meaningful the further along the delivery one is. Early it’s a crapshoot and usually wrong. Estimations and fortune telling have more in common than you might expect.

So sure, we can do estimations. The questions are: when and with which level of information? How much confidence do you want in estimations? And let's ignore non-answers such as “as high as possible” because then the answer is that we do an estimation in the last week of delivery because that’s when confidence is the highest.

For me personally "meaningful" begins after technical planning. That is when the team sat down and actually planned out the work. It’s still _imagined work_ at that point - so dragons are still abundant - but it’s a good enough basis to give an educated guesstimate. Before that it’s reading tea leaves. Of course we can do it earlier but then the range (best vs worst case) will vary wildly. If that’s meaningful enough, great. If not, then that’s shit but nothing we can really do about it, unless someone on the team has a working crystal ball stashed away.

Estimations are one of these things were people love to confidently give wrong answers. It’s a self-perpetuating myth that’s largely done because it was always done and because it gives the illusion of control. Maybe that’s good enough? The illusion?

#SoftwareEngineering #Planning #Tech #TechLeadership #TechMyths #Bullshit

The AI Coding Dilemma: Use It or Get Left Behind 💼⚖️ - JC from Learnovate https://youtube.com/shorts/Xa-oAAzFqhw

Instagram: https://www.instagram.com/reel/DCDNM5_OMds/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA==
Main Site: https://www.analyse.asia/generative-ai-edutech-learnovate-with-joon-nak-choi/
Full YouTube Video: https://youtu.be/iRRzhU5BOeI
Newsletter Signup: https://www.analyse.asia/#/portal/signup
LinkedIn Page: https://www.linkedin.com/company/analyse-asia/

#ai #coding #techmyths #productivity #futureofwork

The AI Coding Dilemma: Use It or Get Left Behind 💼⚖️ - JC from Learnovate https://youtube.com/shorts/Xa-oAAzFqhw

Instagram: https://www.instagram.com/reel/DCDNM5_OMds/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA==
Main Site: https://www.analyse.asia/generative-ai-edutech-learnovate-with-joon-nak-choi/
Full YouTube Video: https://youtu.be/iRRzhU5BOeI
Newsletter Signup: https://www.analyse.asia/#/portal/signup
LinkedIn Page: https://www.linkedin.com/company/analyse-asia/

#ai #coding #techmyths #productivity #futureofwork

"Feeling down about the discontinuation of the Apple Car project? Just think, now all those prototype cars can join the ranks of mythical creatures we'll tell our grandkids about, right next to unicorns and affordable housing. 🚗✨🦄 #TechMyths #AppleCarLegacy"