Email or username:

Password:

Forgot your password?
Jerry Bell :verified_paw: :donor: :verified_dragon: :rebelverified:​'s posts Post Back to profile
Jerry Bell :verified_paw: :donor: :verified_dragon: :rebelverified:​
26 comments
Jerry Bell :verified_paw: :donor: :verified_dragon: :rebelverified:​

I don’t know how you can be an 11x programmer and think you have time for testing anyway

10 January at 15:06 | Open on infosec.exchange
Biggles

@jerry I'm a 40-something X programmer, these 11xers got nothing

10 January at 15:08 | Open on aus.social
Kevin Mirsky :donor:

@jerry spending an x on testing is an x not used towards more code. Inefficient!

10 January at 15:09 | Open on infosec.exchange
Simon Zerafa

@jerry

We're too busy pushing to prod. No time for testing 🙂🤷‍♂️

10 January at 15:32 | Open on infosec.exchange
Ichinin :verified: :verified_paw: ✅🎯🙄

@jerry "10x" just means that you have a solid background in several areas and can do the work of like 10 people on your own.

It does not mean that you work at 10x speed.

10 January at 15:46 | Open on infosec.exchange
AGTMADCAT :verified:

@Ichinin @jerry Yeah but he said 11x, which is in fact 11x faster, because of the self confidence to not write tests.

10 January at 15:50 | Open on infosec.exchange
GolfNovemberUniform

@jerry stop this hate on X11 you all! I will spend time to report every single one of you.

10 January at 17:35 | Open on infosec.exchange
DamonHD

@GolfNovemberUniform @jerry #X10 was a fine protocol too, both for graphics and for power-line appliance control...

10 January at 17:42 | Open on mastodon.social
DamonHD

@jerry I used to be a 0.09x programmer but on an 11x hourly rate. Is that wrong?

(I got *paid* to force other people to write tests sometimes!)

10 January at 17:40 | Open on mastodon.social
Lightfighter
Kristoff Bonne 🇪🇺 🇧🇪

@jerry I imaged the video would have gone like this:

Girl: (recording her video)
"stop testing. Testing is what users are fo! Push straight to pr.."

PC: Bzzzz!! (PC crashes with a blue screen of death)

girl: "aaahhh! Noooo!!!
I just lost my complete video"

10 January at 15:13 | Open on m.krbonne.net
Cat Pandering

@jerry Jerry the only test I'm writing today is for the script that will automate posting this at 4:59p local time on Friday directly to each of my colleagues accounting for their time zone. i18n and personalization are both hard and important!

10 January at 15:15 | Open on infosec.exchange
vampirdaddy

@jerry
Unit tests (more precise: regression tests) come in handy whenever you refactor, so you don’t break consistency/compatibility.

10 January at 16:03 | Open on chaos.social
scops
Dave Flater 🏞️🌲🌌

@jerry This is gold. Faith-based QA is the best thing since statistical QA.

10 January at 16:56 | Open on infosec.exchange
Chris Hessert

@jerry 🤣🤣🤣

Git ‘er done! 🤣

10 January at 17:05 | Open on mastodon.online
Cybarbie

@jerry we joke I hope but the really funny thing is that this is actually Twitter - there is no 'prod'... lol

10 January at 17:23 | Open on mastodon.social
nixCraft 🐧
tortie

@jerry I see you’ve met our lead developer.

10 January at 17:32 | Open on social.vivaldi.net
funnymonkey
Bernie the Wordsmith

@jerry I sent this to my DevOps brother and he is texting back in capital letters 😂

10 January at 17:41 | Open on masto.es
MatthewChat

@jerry believe in yourself! the computer will know what you meant to do! :blobfoxfloofexplode:

10 January at 17:41 | Open on mstdn.social
eenric
Karl Auerbach

@jerry I run a company that build tools to test internet protocol implementations

And so many of those protocol implementations fail. It is sad.

Speaking as a long time programmer (since 1968) and lawyer, it is long past time that code developers are made responsible - via legal liability - for negligent flaws. (Notice that I used the word "negligent"; I'm not asking for strict product liability - at least not yet - although that will probably eventually arive in the context of software that could present a physical risk to humans.)

A video like this would be rather damning evidence of such negligence or even recklessness.

@jerry I run a company that build tools to test internet protocol implementations

And so many of those protocol implementations fail. It is sad.

Speaking as a long time programmer (since 1968) and lawyer, it is long past time that code developers are made responsible - via legal liability - for negligent flaws. (Notice that I used the word "negligent"; I'm not asking for strict product liability - at least not yet - although that will probably eventually arive in the context of software that could...

10 January at 17:56 | Open on sfba.social
Chris Deluca
Go Up