Twitter | Search | |
Ian Littman
I solve problems with code. Mainly of the web variety. I'm also a bit of a network tech nerd. Well, nerd in general. I also help organize .
25,532
Tweets
1,672
Following
1,622
Followers
Tweets
Ian Littman 41m
Mood today: if your library is active enough to average two commits per day for a year, with a bazillion versions, it's active enough that you need a dang changelog goshdangit.
Reply Retweet Like
Ian Littman 3h
TIL Presta valve cores are removable on some bikes tires. Confirmed multiple times, in fact. :|
Reply Retweet Like
Ian Littman retweeted
John Cutler 14h
Instead of asking developers for an estimate, I prefer to ask the product manager this: How long would this need to take for you to reconsider prioritization order? Why?
Reply Retweet Like
Ian Littman 8h
Today, brought to you by "you're optimizing for the wrong things".
Reply Retweet Like
Ian Littman retweeted
Star Simpson Sep 24
TIL . - 13 months - 4 weeks exactly (28 days each.) - Every date fixed to the same weekday every year - One extra day every year ("Year Day!" Dec 31) to sum to 365. Kodak (film/camera company) used this calendar internally from *1928 to 1989*
Reply Retweet Like
Ian Littman Sep 24
Reply Retweet Like
Ian Littman retweeted
🔎Julia Evans🔍 Sep 24
more git fundamentals for : a branch is a pointer to a commit
Reply Retweet Like
Ian Littman retweeted
Durham Constabulary Sep 24
Replying to @JamesLiamCook
Fortunately no, that’s not genuine guidance. It’s a satirical slide from an internal presentation that’s been taken out of context. Everyone knows the only real way to spot a hacker is to look for the guy with the hoodie and question mark face.
Reply Retweet Like
Ian Littman retweeted
ıllıllı 𝙽𝚒𝚗𝚊 𝚉𝚊𝚔𝚑𝚊𝚛𝚎𝚗𝚔𝚘 ıllıllı Jul 25
⚡️ TIL git has a safer force push: `git push --force-with-lease` Git will first check if the last commit you fetched from the remote is still the last one. If not, the push will be aborted, avoiding accidentally overwriting later changes.
Reply Retweet Like
Ian Littman retweeted
Scotland PHP Sep 22
We still have some sponsorship opportunities available for if you'd like to sponsor the lunch (happening in exactly two weeks) get in touch organisers(at)
Reply Retweet Like
Ian Littman retweeted
Troy Hunt Sep 23
A heap of people have pointed me at this so here’s the problem : you’re showing “agents” the same password people use for their social accounts, their email and their bank. You’re also storing them insufficiently (not hashed) and putting customers at a heightened risk
Reply Retweet Like
Ian Littman Sep 23
My guess was that the constant would be ilined in the opcode phase. Looks like that's the case: /cc
Reply Retweet Like
Ian Littman retweeted
SaraMG Sep 22
Ooof. ⁦⁩ this is poor use of image alt tags. Screen readers used by the visually impaired depend on semantically meaningful alt tags to provide information. Don't treat your blind users this way. Do better.
Reply Retweet Like
Ian Littman Sep 23
So far it appears that you have said nothing against the Packers. Or I'm too lazy to check further back in the thread.
Reply Retweet Like
Ian Littman Sep 23
/mute
Reply Retweet Like
Ian Littman Sep 23
iansltx
Reply Retweet Like
Ian Littman Sep 23
PSA: async/await are apparently supported by new browsers without having to Babel-ize down. If you have an internal app where you can control which browsers use it (no, this isn't e.g. Chrome specific), take the code cleanliness win :)
Reply Retweet Like
Ian Littman Sep 23
Replying to @AmbassadorAwsum
Perks of actually having a real time bag tracking system.
Reply Retweet Like
Ian Littman Sep 23
Replying to @AmbassadorAwsum
oh no
Reply Retweet Like
Ian Littman Sep 23
Turn off "show best tweets first". If you already had that turned off the new behavior gets you reverse-chrono (aka How It Should Have Been All Along).
Reply Retweet Like