John Kisor @johnkisor

johnkisor.com Virginia Joined July 2009

Tweets

2K
Followers

170
Following

792
Likes

4K

Clint Kisor @ClintKisor

10 months ago

That ole Bub. — #wolverine #marvel #marvelcomics #DeadpoolAndWolverine

5 7 22 621 2

Download Image

First time drawing the Punisher. I prefer the green over the black - but that’s just me 👀 — $125 +shipping - 8”x10” on Bristol if anyone wants this one. PayPal/venmo. Send me a message if you want to claim 👍 #punisher #marvelComics #marvel #ArtistsOfTwitter

0 2 18 542 2

Download Image

Clint Kisor @ClintKisor

10 months ago

Batman in blue just feels right. 🤠 —- #batman #dccomics #comics #drawing

54 251 3K 52K 239

Download Image

Clint Kisor @ClintKisor

2 years ago

Cosmic Caveman is now on Kickstarter! kickstarter.com/projects/cosmi… #kickstarter #indiecomics #comics #cosmiccaveman

0 7 14 554 1

Download Image

Clint Kisor @ClintKisor

3 years ago

Elon Musk! Please Send This Drawing Into Space! youtu.be/pgM7rEVNnUM via @YouTube @elonmusk

0 2 3 0 0

Clint Kisor @ClintKisor

4 years ago

Batman and Robin are so fun to draw 🤤 — #batman #michaelkeaton #TheFlash #batman #characterdesign #illustration #dccomics @DCComics #WarnerBros @wbpictures

1 32 116 0 5

Download Image

Jez Humble @jezhumble

4 years ago

The thing that I found most valuable - and most generally underrated - from learning TDD 5 years into my career is the art of developing by making lots of small, targeted commits that each deliver an increment but leave the codebase deployable. Multiple commits per day.

14 173 655 0 78

Jez Humble @jezhumble

4 years ago

If you think pair programming is inefficient, try waiting hours to get your code reviewed & having to context switch between tasks while you wait. And then switch back when you get the feedback & have to rethink your approach because you weren’t discussing it as you wrote it.

37 548 2K 0 171

Kent Beck 🌻 @KentBeck

4 years ago

Sometimes you know the answer & asking the question is still valuable.

8 53 271 0 3

Tim Ottinger @tottinge

4 years ago

There are a few pervasive fallacies that make software hard: 1. We need accurate, precise estimates 2. Low output is motivation-based 3. We need to get more work started 4. Throughput comes from isolated individual coders 5. We need to program faster

17 194 475 0 53

John Kisor @johnkisor

4 years ago

Writing a testing library, test-first, using itself johnkisor.com/2021/08/30/tes…

0 0 1 0 0

John Kisor @johnkisor

4 years ago

Displaying Game Server Population in MacOS menu bar johnkisor.com/2021/08/26/ash… ( Shoutout and thank you to @matryer for xbar!)

0 0 2 0 0

dannyodwyer was here @dannyodwyer

4 years ago

IF YOU HAVE NEVER WATCHED DARKPLACE YOU NOW HAVE NO EXCUSE. IT IS THE ABSOLUTE BEST UK COMEDY SHOW YOU’VE PROBABLY NEVER HEARD OF AND THEY ONLY MADE A FEW EPISODES 👇👇👇👇👇👇

Chris Evangelista @cevangelista413

4 years ago

IF YOU HAVE NEVER WATCHED DARKPLACE YOU NOW HAVE NO EXCUSE. IT IS THE ABSOLUTE BEST UK COMEDY SHOW YOU’VE PROBABLY NEVER HEARD OF AND THEY ONLY MADE A FEW EPISODES 👇👇👇👇👇👇

170 1K 7K 0 265

Download Image

47 83 751 0 35

Diana Montalion 🌻 @[email protected] @dianamontalion

4 years ago

Empowered teams don’t simply happen because leadership “empowers” them. Empowered teams proactively communicate, think abstractly as well as concretely, work strategically as well as pragmatically. They set expectations and meet them. They value trustworthiness over status.

0 14 47 0 4

Jessica Kerr @jessitron

4 years ago

Code is cost, and production code is by far the higher cost. If you can write more support code (tests, automation, developer tooling) in order to write less&better production code more smoothly, Win!

Trond Hjorteland @trondhjort

4 years ago

5 57 165 0 19

6 82 334 0 34

Kent Beck 🌻 @KentBeck

4 years ago

Purpose is a surer path to productivity than pressure. Pressure keeps knocking you off the path. Purpose keeps bringing you back onto the path.

15 378 1K 0 47

Justin Searls @searls

5 years ago

I think it's time to discuss the efficacy of Pull Request Reviews as a way to ensure code quality and shared understanding on software teams. Here's a little thread on some of the experiences I've had in my career, why I think this matters, and what we can do about it.