rtomayko

5 ms·

1.
by rtomayko 5y ago
Interesting to see this as I’ve never heard returning to adolescent interests being common but that’s exactly the path I followed after leaving tech. I tried getting into sound engineering because I loved recording with rented 4 track recor
2.
by rtomayko 6y ago
This is specifically allowed in the Linux kernel coding style guidelines as well FWIW: https://www.kernel.org/doc/html/v4.10/process/coding-style.h...
3.
by rtomayko 6y ago
I made the jump to a System76 Adder WS laptop and pop!os for development after buying the lemon first gen MBP with the terrible keyboard. It was my seventh and possibly last MBP (including powerbooks before it). I was considering one of the
4.
by rtomayko 6y ago
It definitely was: https://web.archive.org/web/20140416021831/http://lists.cano... (Related)
5.
by rtomayko 6y ago
I’ve seen this referred to as “satisfying your inner Linnaeus“ and have spent way too much time in that weird place myself.
6.
by rtomayko 7y ago
I’ve been thinking about bike vs scooter a lot lately too. Austin is overrun with scooters and I used them for a little while before finding the electric Uber Jump bikes. They seem superior to scooters in every way in Austin, which makes th
7.
by rtomayko 9y ago
I’ve used a chemex + quality grinder for a long time and haven’t found anything better so not much to add there. I’ve started experimenting with roasting at home, though, and am surprised at how easy it is. Time since roast seems to be one
8.
by rtomayko 9y ago
https://auth0.com I've just started dabbling on a small project and would be interested to understand how features overlap and differences in license/distribution model.
9.
Assess the security of a site's HTTP headers(securityheaders.io)
1 points by rtomayko 9y ago|0 comments
10.
by rtomayko 11y ago
I've always loved this idea. Fun fact: a blame-based suggested reviewers UI was included in the original Pull Request design mockups. We shipped with a much weaker list of everyone with write access list and eventually dropped the list
11.
by rtomayko 11y ago
I'm as keen to see memory safe systems languages become commonplace as anyone but some 90% of our stack is C - Linux, MySQL, Git, MRI, nginx, haproxy, memcached, redis, and many other internal components that we'll be talking abou
12.
by rtomayko 12y ago
"Unfortunately, your request for a 5% raise was rejected. We're sorry to see you go. Can you help hire a replacement? Just write up a quick job posting w/ your basic work experience and daily routine. Thanks."
13.
by rtomayko 13y ago
We thought the Downloads feature was doing more harm than good in its previous form. Quality-wise it just wasn't up to snuff (failed frequently, flash, lack of design). Bad experiences on the site need to be fixed or killed. No one was
14.
by rtomayko 13y ago
We don't talk about unshipped features as a rule. It's hard to do so in a way that doesn't imply promises or timeframes.
15.
by rtomayko 14y ago
Ouch. Sorry about that. Opening an issue now.
16.
by rtomayko 14y ago
I'm looking into why those are showing up in the issues list. Likely a bug. The user has been marked as spammy for over a month, though, which means notifications (email or web) are not delivered. We should have this cleaned up shortly.
17.
by rtomayko 14y ago
Your commits will count for the day they were committed once they're merged to master. i.e., It's the date on the commit that matters, not the date it's eventually pushed to master. A little weird since it means past days can fill in later
18.
by rtomayko 14y ago
These buttons are only displayed for users who have installed those tools. We're not using it as advertisement, we're making it convenient for people who have already installed the tool.
19.
Your team should work like an open source project(tomayko.com)
62 points by rtomayko 14y ago|8 comments
20.
by rtomayko 14y ago
We actually don't care about rate limits with this type of raw request. The limits are in place because people (usually porn sites) hot link js/css/image assets which can lead quickly to an insane number of requests. If file extensions coul
21.
by rtomayko 14y ago
I couldn't agree more. There are also many practical issues that I rarely see touched on in these yay SOA articles, like: Scaling down for development. If you need to start N separate services and work in three projects to get work done, th
22.
by rtomayko 14y ago
No. There's simple conventions for adding feature flags (user.some_feature_enabled?). Features are enabled and disabled by changing the code and deploying. This works because deploying new code is fast.
23.
by rtomayko 14y ago
Wow, really? Really sorry to hear that. Moving through trees is one of the fastest page level operations on the site as far as perceived performance. We'd like to make it faster but it's definitely in the area of perceived performance we're
24.
by rtomayko 14y ago
I'm a developer at GitHub. This is a really good writeup and touches on many of the frontend issues we've had our eye on for a while. In fact, the <script> related bits are already dated. We've just rolled out defer support for thes
25.
by rtomayko 14y ago
Yeah. I mean 4,517 seems like a big number to humans but meh. You're talking about a highly optimized parser. It's likely going to rip through those quotes in about the same time it takes to dispatch a single unjit'd/unoptimized javascript
26.
by rtomayko 14y ago
Do you use parenthesis to denote order of operations in all cases, even when extremely obvious? If not, should we assume your position is absurdly immature hipster posturing that serves no engineering purpose?
27.
by rtomayko 14y ago
I'd agree with you if not for the many subtle and critical bugs I've seen introduced into our production environment due to and/or precedence problems. The increased expressiveness when used correctly is just not worth it.
28.
by rtomayko 14y ago
Do you use semicolons in Ruby, Python, shell, or other semicolon-less language where semicolons are allowed? If not, what's your justification for omitting them?
29.
by rtomayko 15y ago
Assuming your main product is on the web, you really only need a few things to do this right: - Automated tests that run on push to any branch. - Rolling deploys (no downtime) from any branch. - Exception reporting system (Exceptional, Hopt
30.
by rtomayko 15y ago
This is exactly why Hubot was created in the first place. An excerpt from the original project README: This is Hubot, a Campfire chat bot in node.js. The goal is to make common systems stuff seem less like black magic by turning frequent

More ›