seymour333's comments

This reminds me of a time when I had become jaded as a camera store employee. I got in the habit of telling people that the cameras they were hoping to buy were essentially landfill filler. This website would have been a useful resource for confirming that point.

Oddly, it was an effect tool for up-selling cameras. The higher end cameras tended to last slightly longer before getting binned.

A few years ago I made the decision to go back to school (for two years) to be a web dev. It cost me approximately $25k. Immediately after graduation I added $25k to my yearly income. There is a ton of work for web developers, and there will continue to be for some time (even if something comes along that makes web devs redundant, there is still decades of maintenance work in the market).

It may be important to clarify exactly what you mean by web developer though. I work in many different portions of the web stack every day (database, server side code, front-end code, etc). The more diverse your skill set, the more opportunity there will be.

At any rate, web is a really good entry point, and after a few years in industry you'll probably start to see different branches of development that appeal to you more. If you start out as a web dev there will always be different avenues and opportunities as your career advances.

This probably applies more to homes with an East to West facing pitch, but I find it really odd that it isn't standard issue to have a track system that moves the solar panels from one side of the roof to the other. A simple track and something basic like a garage door motor would allow the panels to be in a more optimal position throughout the day.

As someone who developed parnosmia later in life (I can only smell certain things), I found this article very interesting. Living without the ability to smell is somewhat more isolating than one would think. That, and I have to really trust someone if I want an opinion of whether the milk's gone bad

We definitely need to give Swiffer an honorable mention. Dust in your house? Why not clean it up and create an enormous pile of trash at the same time!!!

I always appreciate commit messages that are informative and well structured. That said, I'm not a fan of specific formats for commits. The commit messages in a project are where a lot of that project's collective "personality" is stored. If you look through the commits for a project with a "colorful" variety of messages, you'll get a sense not only of the work that was done, but of the people who helped create the project.

Somewhat related: @git_commit_m on twitter has some great (and amusing!) examples of what not to use for commit messages, which are pulled from github's public data set.

This whole article seems like an offhand way to get people to stockpile aquarium antibiotics. This guy is obviously on Big Aquarium Pharma's payrol.

“It’s like salmon,” he said. “They’ll return to the place where they were spawned.”

Mark my words, someone is going to memorize the entire thing and use it as a party trick.

The company I work for pays for Ag-Grid, which makes me sad. Overall I find it has been fairly difficult to work with, and there are a lot of breaking changes when upgrading from older versions. I think we could get away with something like Tabulator for most of our use cases. I'm definitely going to try to sell it to the team

Anyone have comments on how this might stack up against AG-Grid?

"Start with a phone screen interview"

I have to disagree with this point. Phone and screen interviews are awkwardly paced and some individuals simply don't come across well in this type of setting. If the qualifications on their resume fit your requirements, just bring them in!

I feel like this essentially exists for the sole purpose of generating a large training set for some sort of drawing analysis.

I wonder if google has some new use case where they want to be able to quickly tag human doodles with their subject matter?

Semantic pedantics and the developers who love them

I've witnessed this first hand. After having a sleep study and finding that I have mild OSA my ENT suggested removing my tonsils, uvula, and part of my palate to open up my airway. I told him that sounded like the nuclear option and he seemed somewhat surprised by that conclusion.

He also suggested palate coblation, which seemed more reasonable. I chose to forgo both of those procedures and eventually ended up with a mandibular advancement device from a TMJ specialist, which has made a huge difference.

There is a secondary solution to CPAP machines that may apply to some people who find their breathing/sleep improves with sleeping position. About a year ago I got a Mandibular Advancement Device from a TMJ specialist that pushes the jaw forward, preventing the tongue from pushing the against the palate and obstructing airflow.

I had tried a CPAP machine previously and still felt that it wasn't working (although the data said otherwise, I just felt like I wasn't breathing properly).

If, while laying on your back, moving your jaw forward improves breathing significantly, this type of treatment might be a good alternative to a CPAP (costs are similar though).

Wait, dogs can get cancer? Fuck. That is super depressing.

As far as I know I made it up. It's the term I typically use to give potential employers (and other devs) a general sense of where my competencies are.

The way this works out at the shop I'm currently at is that you get a bunch of devs who are, for lack of a better description, 3/4 stack developers (back-end, database, anything on the front-end that isn't CSS), and a few other devs who are strictly involved in the design/HTML/CSS portion of projects.

This system seems to work out pretty well on most projects. There is a significant body if knowledge required to get the styling and markup in an application built properly, with a high degree of cross-browser compatibility, and in a reasonable amount of time.

When I think of a front-end dev I tend to lean towards this definition. Which leaves me at somewhat of a loss to describe my role as a "back-end" developer, as I spend a generous portion of my time coding with Angular.

What can be done to prevent a climate catastrophe? Start an economical catastrophe.

We need to immediately, and meaningfully, move away from oil, gas, and other carbon heavy industries in any way that we presently have the means to do so.

If everyone who is presently in the market for a new vehicle could afford to buy an electric one, we'd probably be in better shape. If every household could put solar panels and take a load off of the grid, we would be moving in the right direction.

The problem is these technologies are new, and expensive, and they can't be effective at solving the problem they set out to solve without mass adoption.

Mass adoption won't even _begin_ to happen until the average person can pick up a used Model 3 for around $10k. Where populations heavily use mopeds and motorcycles we need a flood of affordable electric alternatives. Both of those scenarios are at least a decade out.

If we need to solve this in 12 years we're screwed. Best bet is to move somewhere cold and inland. Then at least you can be somewhat comfortable while the whole thing goes down. Although the process of moving the world's economy away from oil (to whatever extent that can be achieved while still producing plastics etc.) is going to make life miserable no matter where you are.