jenseng

8 ms·

1.
by jenseng 5y ago
Nobody said "quarter" means multiply by 4. They said "quater" means multiply by 4, which it essentially does [1]. In addition to being a real word, it's also a prefix, e.g. "quaternary" means fourth in ord
2.
by jenseng 5y ago
You get "clean and DRY" at the expense of "not beginner-friendly" and "you need be to very careful". Thanks, but no thanks. I'll take clear, understandable code over clever footguns any day.
3.
by jenseng 7y ago
Someone built one a couple years ago: https://gizmodo.com/todays-hero-made-an-ai-that-annoys-telem...
4.
by jenseng 10y ago
Does the trademark office just rubber stamp anything they get and let the lawyers fight it out? IANAL, but these look pretty similar: 85632326 (Instructure): IC 042. US 100 101. G & S: Application service provider (ASP) featuring softwa
5.
Show HN: A friendlier style sheet, eh?(github.com)
4 points by jenseng 12y ago|1 comments
6.
by jenseng 12y ago
The API is pretty comprehensive, and is growing daily. With the exception of some legacy features, all of the web app's UI is built on top of it, as are the mobile apps. https://canvas.instructure.com/doc/api/
7.
by jenseng 12y ago
something like this will find any associations that share a name with a column in each model: https://gist.github.com/jenseng/2039fd57f5db40779871
8.
by jenseng 13y ago
It's a shame these aren't actual database ENUMs, but rather ints (with the mapping in ruby land): https://github.com/rails/rails/commit/db41eb8a6ea88b854bf5cd... Even a text column would be preferab
9.
by jenseng 13y ago
This approach works well when you want to cache data from an existing integration database and don't have the luxury of rearchitecting the whole thing. At my previous job, we had a bunch of systems talking to a single database. Some we
10.
by jenseng 13y ago
UTC offset is well and good if you are talking about today, but as soon as you start displaying past or future datetimes, DST will bludgeon you over the head. And depending on your app, users might want control over the timezone. When a t
11.
by jenseng 13y ago
We did a two-day hackfest at work recently, and this was my project. As canvas-lms has grown, we've seen our GC runs get slower and slower, and this seemed like some good low hanging fruit (especially as we keep adding more languages). I mo
12.
Show HN: Faster ruby I18n backend written in C(github.com)
5 points by jenseng 13y ago|1 comments
13.
by jenseng 14y ago
There were several factors, but the two big categories were: 1. Familiarity. The original decision to use MySQL was arbitrary, and as the team grew, we just so happened to hire lots of postgres-philes. 2. Death by a million paper cuts. Lock
14.
by jenseng 14y ago
This looks promising. The MySQL -> Postgres replication possibilities are particularly interesting for people looking to switch over a huge database with (almost) zero downtime. At Instructure we essentially did this last year when we m
15.
by jenseng 14y ago
I guess the real lessons there for users is "don't do anything sensitive on a device that's not yours. or on one you just acquired, unless you trust every hop between you and the server". But users generally don't know/care/think about thes
16.
by jenseng 14y ago
I should clarify, I was referring to the first visit to the site. So yes, I can see how this greatly reduces the vulnerability, though it doesn't completely remove it. As an example, a rogue Apple Store employee could insert him self as a M
17.
by jenseng 14y ago
The author seems to gloss over the importance of browser built-in HSTS lists. If you're just relying on a response header to tell the browser to use HTTPS, aren't you still vulnerable? Isn't that the same fundamental problem with redirectin
18.
by jenseng 14y ago
to put it simply, browsers are really good (these days) at executing javascript, thus the biggest factor in this test seems to be the large(r) HTML payload. though to make this a better test, I think you should serve both the JSON and HTML