brian_c

Aquaphor's the best thing I've found so far. Just takes a tiny bit, so whatever's left over on my fingertip gets rubbed into my knuckles which are probably also chapped.

Netflix's _How to Change Your Mind_ (based on a book with same name, I believe) has been a nice digestible look at psychedelics' uses in various therapies, now and in the past, if you're interested in that kinda thing.

(And, off-topic, but the scrollbar on the left here is interesting. Looks like it's a LTR block overflowing a RTL block. I don't think I like it, but, interesting!)

Ah, in that case: Still seems kinda risky? Like, what if someone else submits a solution for the ticket I'm in the middle of? What if my solution is valid, but not accepted? What if it's incorrect, but in some subtle way that won't be discovered until next week?

Production work on an unfamiliar project warrants some discussion. I think in general I wouldn't make any significant contributions to a project before talking with the people running it and making sure we're on the same page.

And apologies for the initial curt reply—asking people who are looking for a job to work for free sets me off a bit. Algora looks like a really nice platform!

Free labor in exchange for the possibility of an interview? I think the fuck not.

ISeeChange | Back-end developer (with some devops) | Fully remote | Full-time contractor | https://www.iseechange.org/

ISeeChange is looking for a back-end developer to own our API (Node.js and PostgreSQL) and devops (AWS and Kubernetes) work. Upcoming features will involve machine learning, GIS, and setting up more robust access to our data for clients.

We're a small but growing company; the dev team is myself on the front end, a data scientist working on machine learning and analysis, and some part-time support from the devs who initially built the platform, so there's a lot of opportunity to help shape the company. Our broad mission is to connect folks with their environments, specifically with regard to climate change.

The full job description and application details can be found here: https://stories.iseechange.org/backend-engineer-at-iseechang...

Disappointing that all the images are built on the same shade of white skin. You're leaving out a whole lot of folks who are already underrepresented in a whole lot of research. I think it'd be helpful to vary the skin tones shown, or stick to a medium-tone (enough to be ambiguous) grayscale.

Giant thanks for making this. A suggestion, though: the "remote" switch should probably imply "or". A search for jobs in Chicago OR remote would be more more useful than Chicago AND remote. The latter currently returns Chicago-based companies that hire remotely.

Nice! I worked out a little proof of concept a while back for a pan-and-zoom wrapper around any ol' HTML, if that's of any interest: https://github.com/brian-c/react-zoomable I haven't tried it with SVG, but I imagine it'd work fine.

You can probably use 90% of React's functionality with like, four or five functions and four or five component lifestyle methods. What's not minimal about that?

I've had one of my package names transferred away from me with no warning, presumably after some period of inactivity. Npm as a repository seems to have gone totally insane, and I don't think I'll be publishing there anymore. I'll recommend people install my modules from a tag in the repo.

`curl ... | sh` installations don't really bother me. The scripts tend to be short and commented, or at least readable. Sure beats running an opaque .pkg installer, which invariably asks for your password (presumably for no reason) and installs god-knows-what all over your hard drive.

So basically follow the example of pre-standards browser-specific HTML features?

In a fair world, the time and energy that went into Bower would have been spent making npm just a little bit better for front-end stuff. `npm dedupe` is halfway there. Now I have to deal with two arbitrary sources of dependencies.

Every time I start writing a new node module, I stop and see if substack (or visionmedia, for that matter) has already done it.

Yeoman makes it quicker and easier to generate boilerplate code, but I think the goal should be to eliminate boilerplate and abstract it away. Yeoman keeps spaghetti organized, but it's still spaghetti.

You can turn on Safari's awful console in the Settings app, I think under "advanced".

This is useful in a pinch, but transitioning a 100px high element from max-height 9999px to 0 means there's going to be a huge delay while it's transitioning between 9999px and 100px followed by a very fast transition between 100px and 0, which is usually worse than having no transition at all.

It breaks returning object literals because `return` on its own line is a complete statement.

Sort alphabetically. It's not arbitrary, everybody understands it, and no tool needed. This is silly.

I really want to like this, but I can't get behind Sprockets when RequireJS and Browserify exist. Code in comments, obtuse file extensions, `require_tree`, etc. make code modularization an inelegant kludge.

The install script takes staggering liberty with your system to fetch its dependencies. Make sure you read it before running.

http://get.yeoman.io

This bookmarklet will make it work in a desktop browser. Hold alt to get a second "finger", and shift to lock it with the first, like in Apple's iOS Simulator.

https://github.com/brian-c/phantom-limb/blob/rewrite/bookmar...

Neat! I made something (I think) similar a while back, also inspired by Clojure. Mine's more of a proof-of-concept, as I have zero Clojure experience outside some very casual reading.

https://github.com/brian-c/patterned-function

You seek the Rosetta Code. http://rosettacode.org/wiki/Hello_world/Text

Have you seen James Burke's Connections? Sounds like it'd be right up your alley. http://topdocumentaryfilms.com/james-burke-connections/

I wrote something similar a while ago, mostly inspired by the various Zen Coding plugins. Nice to be able to compare my approach with someone who knows what they're doing.

You can play with mine here: http://viewinglens.com/dojo-modules/brian.util.create.html

And the source: https://github.com/brian-c/dojo-modules/blob/master/brian/ut...

Why? Write your CSS. Test it in browsers. If something doesn't look right, fix it. Resets are bloat.

I honestly had no idea Cappuccino was still even a thing since Motorola bought 280 North. Didn't they kill development?