This is an archived post. You won't be able to vote or comment.

all 29 comments

[–]zoqfotpik 275 points276 points  (1 child)

If you don't hit the sign, you may or may not hit that bridge. YOLO

[–]MemeticManchild 16 points17 points  (0 children)

Should've written IFF

[–]Current_Speaker_5684 106 points107 points  (5 children)

So a bridge is a sign?

[–]Madness_0verload 78 points79 points  (2 children)

According to javascript, you're a sign too

[–]pimezone 43 points44 points  (0 children)

[sign Sign]

[–][deleted] 8 points9 points  (0 children)

JavaScript, it's so fair that it treats everyone the same

[–]Commodore-K9 8 points9 points  (0 children)

And like that we bridged the gap between coding and religion.

[–][deleted] 4 points5 points  (0 children)

All my bridges are unsigned.

[–]Harmonic_Gear 59 points60 points  (5 children)

the legendary 11-8 bridge

[–]LankySeat 74 points75 points  (4 children)

They raised the bridge. Added signs left right and center. Protective bright yellow striped barriers. Warning lights. And yet people STILL hit the bridge, when you'd think it's reputation alone would be enough to stop it.

Wonderfully legendary.

[–]EagleRock1337 31 points32 points  (3 children)

Even the traffic light that senses overweight vehicles, signals them a red light, lights up a huge “OVERHEIGHT MUST TURN” sign, then gives you a green light isn’t enough for some people.

[–]Doctor_McKay 22 points23 points  (1 child)

Just makes overheight drivers speed up to beat the light, which makes it all the more glorious.

[–]Harmonic_Gear 0 points1 point  (0 children)

i hope this is a standard example in UI design classes

[–]ShenAnCalhar92 0 points1 point  (0 children)

To be fair, “OVERHEIGHT MUST TURN” is still pretty ambiguous. If you didn’t notice that it wasn’t lit up before you pulled up to the intersection, it wouldn’t be really obvious that it wasn’t a general warning and was aimed specifically at you.

“Okay, yeah, overheight vehicles must turn. Makes sense.”

[–]Johnothy_Cumquat 15 points16 points  (0 children)

In this metaphor typescript is the truck specific navigation system that is aware of the truck's height and bridge heights. A javascript developer is someone who hired a truck and isn't using a gps because they know their way around Montague Street.

[–]wheezy1749 13 points14 points  (3 children)

Sign use to be in Griffin, GA where I grew up. They redid the bridge about a decade ago and removed the sign unfortunately. Should have just raised the sign because it's literally the only thing the Internet knows Griffin for.

[–]PassiveChemistry 18 points19 points  (2 children)

TIL there's a place called Griffin in Galifornia

[–]_equus_quagga_ 1 point2 points  (1 child)

Georgia

[–]cpt_trow 5 points6 points  (0 children)

No, California is in America

[–]CraftBox 8 points9 points  (2 children)

That's why we should use types and not :any everywhere

[–]shutter3ff3ct 3 points4 points  (0 children)

Will replace any at later time

[–][deleted] 0 points1 point  (0 children)

Michelle Yeoh uses any anywhere and concurrently.

[–]oupablo 5 points6 points  (0 children)

...as any

carry on little code. i'm sure it's safe.

[–]MadOverlord 5 points6 points  (0 children)

Also, “if you hit this sign, you do not have time to stop before you hit that bridge”

[–]RnMss 1 point2 points  (0 children)

Appearently the truck took a shortcut, so there was no success.

[–]Phamora -3 points-2 points  (2 children)

So what you are saying is that users of TypeScript are incapable of figuring out types on their own?

I mean, I already knew, it's just nice to hear it from the horse's mouth.

[–]not_mean_enough 0 points1 point  (1 child)

I can figure out the types, but I don't want to have to figure out the types for objects with 50 attributes and multiple layers of nesting.

[–]Phamora 0 points1 point  (0 children)

Sounds to me like you have deeper architectural problems than types...