Joe C. Wallace, III (@joecwallace) header
Joe C. Wallace, III (@joecwallace) profile picture

Writes software. Lives in an RV.

Nashville, TN
Joined September 2011
Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)Photo by Joe C. Wallace, III (@joecwallace)
Joe C. Wallace, III retweeted
7/ Built is transforming the way the physical world is constructed. It's one of the fastest-growing companies in our portfolio, but so much still to do. Thrilled to partner with Lee Fixel @jackiereses @gokulr @JeffreyReitman @walkerforehand and others on the next chapter!
3
16
It's been almost 2 years since I tweeted. I'm breaking my silence _for you_ to try to hire you. #PHP #laravel #VueJS #Jobs corecommerce.com/jobs/senior…
1
1
PSA: @matthewtrask is a good person. Thanks, Matt. ❤️
8
In #Seattle, when you see someone you know, you stand a safe distance away and shift your weight from leg to leg while you ostentatiously remove your #AirPods, and then you hug/high-five/whatever. This, I think, is the shitty American version of the Japanese business card ritual.
Canadians are so friendly that in the third day of this music festival they still haven't ruined the portapotties.
8
Just watched a dude throw a piece of bison shit damn near 200 feet. #america #westyellowstone #montana
2
Thinking about doing a software talk at the cities and towns on our RV journey: "What I learned about software from living in a motorhome". It would mostly be an extended poop joke filled with tips on legacy code. There has to be a market for that, right?
1
I have a Google Fit goal of "being active" for an hour per day, but the fitter/faster I get the harder it is to hit the goal. 🤨
1
Every now and then I reread this astonishing and terrifying description of the end of the dinosaurs, via @PeterBrannen1's 'The Ends of the World':
52
2,528
410
5,685
Sometimes, when you live a fairly public life on social media, you challenge and encourage people - even though you have NO IDEA that you're doing it. (S/O @matthewtrask, and he has no idea why.)
"Likewise, a Story is the illusion of what your smartphone saw. Or better, of what the hybrid you-and-your-smartphone saw—as if there was a you without a smartphone, anymore." xitter.cf/kottke/status/99247167…
Difficult thing about continual improvement: the better you are at something, the harder the incremental progress is to see (because it's smaller).
2
1
Another example about running: 27 years ago, Carl Lewis ran a 9.86s 100m. Since then, the greatest efforts of the entire world - including the fastest human ever to live - have not improved 3% on that mark. Because they're already *so good*.
1
1
[I'm not saying I'm that good at software, but I am pretty good - because I've been practicing it intentionally almost daily for the last 15 or so years. And sometimes, I feel like I'm not improving. BUT I AM. It's just hard to see.]
1
I just searched my Gmail for the name of someone I had never contacted before. It returned a thread that had an image that was a screenshot of their name & email address. #sorcery
1
So most of the dentists in Nashville that we have called don't accept @OscarHealth anymore because they aren't paying the bills. I pay $1500+ per month for this "service".
3
1
Just saw a senior dev brag to a junior that he hasn't written a resume in 5 or more years. Same dev sent a resume to me 1 year ago to apply for a job. Why try to be a badass here? How does that help the junior?
1
3
`npm install`: 27 minutes and counting, no output to screen yet
1
2
The software you're working on actually has commercial value, and you can be confident you'll have a job tomorrow? xitter.cf/cmgmyr/status/98204020…
Usually working with legacy code isn’t what developers typically want to do, but what are some positives about working with it? For me: 1. Learn something new - even if it’s what “not to do” 2. Add tests to complex areas of the code 3. Refactoring practice (and more testing)
2