Just blogged about my career mission: "to give software developers knowledge and tools to help them reason about their programs" (https://t.co/sSNRo1m32S). A summary thread: (1/N)
Hi all, this will likely be my last tweet. I don't want to even tacitly support Elon Musk and the kind of company and community he's trying to create. Thank you to those who made this site what it was until now. I'll be on Mastodon at @[email protected]; hope to see you there!
@ShriramKMurthi The It Will Never Work in Theory mini-conferences are arguably more SE than PL, but may still be of interest: https://t.co/ksWPn9VlW3. Note that the talks are bite-sized: just about 8 minutes each
As an academic writing coach, here are the 7 mistakes I see supervisors and PIs make in the process of co-writing a paper with their PhD students or mentees.
A thread. 🧵
#AcademicChatter#newPI#PhDchat
I've seen a lot of people asking "why does everyone think Twitter is doomed?"
As an SRE and sysadmin with 10+ years of industry experience, I wanted to write up a few scenarios that are real threats to the integrity of the bird site over the coming weeks.
@tomaspetricek I think https://t.co/gJxaOg8BAE and systems.discuss are both good fits for you. But from what I've learned so far, the choice of server doesn't matter all that much and it's reasonably easy to switch later.
With Twitter's change in ownership last week, I'm probably in the clear to talk about the most unethical thing I was asked to build while working at Twitter.
🧵
@TaliaRinger Big +1 to all of this. I don't want this community to break apart and fracture across N different services, many of which are less accessible than Twitter. But my dislike of Elon is making me want to join Mastodon as soon as I have the time to do so.
Twitter employees, DO NOT SIGN ANYTHING when you're laid off.
Consult with an attorney first.
Buried in the fine print may be a waiver of your rights under CA and federal law.
Those rights are important and valuable!
#TwitterLayoffs
@S_Hanenberg@Felienne And that seems true here. I'm not fluent in Fortran, but I can at least recognize an if statement, a do-while loop, and other common constructs.
@S_Hanenberg@Felienne I'm confused by this comment. I've never taken that statement to mean that by knowing one language you can instantly understand all others. I've always understood it to mean something more like "It takes less time to learn Fortran if you already know another language".
@jhemann The task was to make a little robot car that would stay inside a drawn perimeter and stop when it found an obstacle. But we also found the sound API and got it to play an approximation of "A pirate's life for me" when it succeeded.
@TitusWinters According to research cited by @hillelogram, code review is is one of the few SWE practices that has a consistently measurable positive effect. See https://t.co/DKVdhurFDN and https://t.co/OwM81ckipE.
Clean Code? Helps a bit with adding features but might make debugging harder https://t.co/970o4rzg71
Design by Contract? Good luck finding any empirical studies on it.
Code Review? Okay this one is actually really effective
Hey, DevOps and Software engineering research folks: what're your favorite research results?
(I almost said "Favorite under-cited results" but I think it's all under-cited.)
RTs appreciated. 👍