mvzink

This is exactly why I think Talko is so cool. Not quite a replacement for email, but has some good ideas.

Epsilon-delta proofs are beyond me, but we still teach calculus in high school. Just because some parts of a field are esoteric without study doesn't mean the field is doomed to obscurity.

SEEKING WORK - Seattle or remote

A friend and I recently upped sticks and moved from Chicago to Seattle to put our tech chops to use. We've been consulting together for a little over a year, and I personally have been doing it for one more than that.

Between us, we have experience with a lot of different areas from distributed systems and networking protocols, to, of course, full stack web development. Our main common ground is that we both feel equally at home with C and JavaScript—weird, huh?

Lately, we've been focused on frontend web development and have a lot of experience with Angular in particular. We're quick learners and eager to experiment, but we're also pragmatic and will always choose the right tool for the job. That said, we would especially love to get onboard with a Clojure/ClojureScript project... just saying.

Anyway, if you have a project in need of some love from one or two clever developers, or if you need a solid MVP, shoot me an email: [email protected]

SEEKING WORK - Seattle or remote

A friend and I just graduated from the University of Chicago, and decided to put our technical chops to use in Seattle.

Between us, we have experience with a lot of different areas from database implementation, to distributed systems, networking protocols, and of course web development. Our main common ground is that we both feel at home with either C or JavaScript—weird, huh?

Lately, we've been focused on frontend web development and have a lot of experience with Angular in particular. We're quick learners and eager to experiment, but we're also pragmatic and will always choose the right tool for the job.

If you have a project in need of some love from one or two clever developers, or if you need a solid MVP, shoot me an email: [email protected]

SEEKING WORK - Remote or Seattle area

For hire: a pair of...

  - Distributed systems theorists
  - Database implementors
  - Web designers
  - JS coders (Angular anyone?)
  - Clojurians
  - Assembl... on second thought, we'd rather not
  - Jacks of useful trades

If your project needs some love, we can probably help. Get in touch: [email protected]

They seem to approximate with recurrence relations; they cite a bunch of literature about the technique, referring to "cost relations".

The two main inputs to their model are the IR and the ISA.

True. However, as a graduating CS major, almost every non-CS major I know here and at other schools has taken some programming-focused class or done Codecademy or something. Few if any are looking for what we might think of as "tech" jobs, or are motivated primarily by any promise of money. I can anecdotally attest to the fact that all the reasons listed by the author are playing a significant role.

(As a side note, a fair number of the people I know who are doing straight up startup-style "tech" jobs after graduation aren't even CS majors.)

Exciting prospect. How about DataScript for your app state + tx-listen/om-sync mirroring transactions? Might require wrapping the datascript/transact! call, and I haven't thought about reading from the cliente. Maybe as simple as lazily mirroring datascript/q calls and filling those back into the DataScript map.

Funny; the article has me thinking about being more open with our humanity on the web, then you reference an apparent brush with death as a sort of backstory—something many, myself included, would be uncomfortable sharing. Thanks for being candid!

Ideally, in the future, yeah. But for now, two reasons I can think of: first, Multipath TCP doesn't cover the same use cases as dispatch. For example, having one proxy only route to low-latency connections (e.g. for gaming) and another to all connections (e.g. for downloads). Second, Multipath TCP isn't widely implemented and would require application developers to use it, whereas this can give many of the same benefits without waiting for your applications to support it.

It's not designed around global state. It's true that just about every HTTP router has this "feature", but all it's doing is allocating a "global" server object by default and adding the module-level helper functions. In other words, if you only want a single server object and don't need to configure it, or if you just want a quick hello world example, you don't have to allocate the server object yourself. Without those extra convenience methods, this would be hello world's main:

    s := web.NewServer()
    s.Get("/(.*)", hello)
    s.Run("0.0.0.0:9999")

Same goes for net/http and gorilla. net/http calls it the "default" server, web.go calls it the "main" server. I blame the influence of Sinatra etc.—the examples (for all three libraries) don't make it clear that this is what's going on and don't encourage making your own server objects to minimize global state.

This is great news. However, all this discussion of "semantic this-or-that makes my site look like shit" or "semantic tags are just for template clarity" and "well at least web crawlers and Readability can make use of it" is really annoying.

If you think <main> exists to make SEO easier for you, I'm willing to bet that around 7 million blind people in the US alone won't bother trying to use your site. Why? Because their screen reading software won't be able to make it through your mess of markup and get to the part that matters, for one.

It's hard enough getting people to care about accessibility at all, but trying to drive ARIA adoption must be a complete nightmare. <main> is taking one of the most obvious, simple, and useful pieces from ARIA, which just happens to fit in quite sensibly with existing "semantic" tags, and allowing you to remove an important accessibility hurdle without even knowing about ARIA!

I, for one, am extremely glad that I can now make my sites a bit more accessible with almost no extra effort.

I know this is asking a lot, but would anybody like to weigh in with some explanation/evidence for the descriptions of those four parts of the brain?