ryanthejuggler

As a Node coder I used to avoid SASS since it was Ruby-based; now there's a fully-featured SASS parser in Node that keeps up with the specification. Bootstrap is moving from LESS to SASS, and they've always had their build step in Node.

If 90% of all egg-crackers are short, it's likely that there's a huge problem driving tall egg-crackers out of the field.

Docking stations ARE awesome. Seems like USB-C is going to kill docking stations though. Already they feel a bit like a relic from the 00's.

Honestly, ES6 offers many of the advantages of Coffeescript (arrow functions, destructuring, etc.) and has the advantage of being a standard that will soon be natively understood by browsers, is fully backwards-compatible with ES5 (and therefore widely understood by developers), and also has a lot of IDE support and tooling available.

I agree with you, with one addition in GitFlow's favor--it standardizes how your team works. When you have multiple team members collaborating on a project, a poor standard is better than none at all.

Ironically, for that reason, GitFlow would work better in Mercurial. Go figure.

> ...the history of a project managed using GitFlow for some time invariably starts to resemble a giant ball of spaghetti. Try to find out how the project progressed from something like this...

It's simple. Read backwards down the `develop` branch and read off the `feature/whatever` branches. Just because the graph isn't "pretty" doesn't mean it's useless.

In general, I'm starting to dislike "XXX considered harmful" articles. It seems to me like you can spout any opinion under a title of that format and generate lingering doubt, even if the article itself doesn't hold water. Not to generalize, of course--not all "XXX considered harmful" articles are harmful. They generally make at least some good points. I just think the title format feels kind of clickbaity at this point.

That said, kudos to the author for suggesting an alternative rather than just enumerating the shortcomings of GitFlow.

> if I abstain from voting for a number of cycles

The whole point of the system is to railroad people into only voting for what really matters to them, by "saving up" their votes. I think this isn't a flaw but a feature.

I'd expect that there'd be a fairly large number of tokens so that quantization wouldn't come into play too much.

I feel like this could potentially work with "voting tokens" or something else that's not money. Maybe with some sort of crypto verification. You'd still have the scarcity that the system demands, but without the "inequality baggage" you'd start out with if the system were implemented with actual money.

If you implemented this system using money to buy votes, then you'd end up... well probably with something like the inequality situation we have today.

If you're already weeding through the code, why not invite the coworker to sit down next to you? In my experience, sometimes all someone needs is a pattern to adhere to, and once you show that pattern things might work out.

Of course, this is only good about 80% of the time. Sometimes people just don't get it.

Favorites:

* Social Justice Bullies: Google Sued by Google

* Deleting the Teacher

* Show HN: Code

* Sorry grandma, That Way

Thingiverse does this: http://www.thingiverse.com/search/page:1?q=puppy&sa=

Notice that when you scroll, the page value changes, and when you scroll back up, the browser re-fetches the content.

Hey, if you want some content for thismeetingcost.us, I whipped up a little something: http://jsbin.com/rubale/

This is embarrassing, I've got so many started/abandoned projects. I suppose if anyone were interested in one of these projects I'd be glad to chat about either working together or selling the domain, depending on the project.

warning: this post contains sarcasm

- http://subwaytim.es - subway tracking service

- http://thankyouforriding.com - game for coders to optimize operation of a subway system. Thought of this during Boston's terrible public transit struggles this winter

- http://gitforgovernment.org - wanted to encourage city/state govts to put their legislation on GitHub and accept pull requests. THAT would have gone well

- http://enginomicon.com - planned to put my course notes from my mechanical engineering degree online; make a Wikipedia for all types of engineering

- http://everyref.com - created before I discovered devdocs.io and wanted to make a quick ref for coders. Right now you can search HTTP statuses, but the project is pretty much dead; I'm not sure if I even still have the code for it

- http://stupidprogrammertricks.com - place to put little projects and small demos. So far the only demo is a properly-installed nginx server :-P

- http://uwherever.com - wanted to create a place where people applying to college could organize their efforts, see when deadlines fell across colleges, publish their acceptance/rejection for other students to see, etc. As you can see I spent a lot of time picking a name for this

- http://spinner.graphics - planned to spend a quick weekend making a few AJAX loading animations and presenting it with ads, because who doesn't have at least one site that they're only doing for the money?

- http://beer-n-code.com - planned to make a public directory of bars with wifi suitable for meetups. So far only has a mesmerizing ASCII beer mug on it

Assuming you mean 'forking': my guess would be that if you fork it, it would look like you're making contributions that could be merged back into the original project. If you import it then it will appear as a completely separate project.

Suffering from HNDoS; read it at http://webcache.googleusercontent.com/search?q=cache:http://...

Also links to http://impossiblehq.com/get-disciplined-not-motivated and http://thereallimegreenandloki.tumblr.com/post/101385465984/...

The "official" way to do this is map, then reduce. The way reduce is meant to be used exactly matches this implementation.

Consider that you have a large quantity of numbers that you want to get the min, max, mean for. If you write something like the following:

    function minMaxMean(list) {
      return list.reduce(function(lastState, n) {
        var min = lastState.min,
            max = lastState.max,
            sum = lastState.sum,
            count = lastState.count;
        if(n < min) min = n;
        if(n > max) max = n;
        sum += n;
        count += 1;
        return {
          min: min,
          max: max,
          sum: sum,
          count: count
        }
      }, {min: Infinity, max: -Infinity, sum: 0, count: 0});
    }

...then you're assuming that the reduce function will run once, over a single list of numbers, in order from left to right. However, if you implement it as the following:

    function minMaxMean(list) {
      return list.map(function(n){
        return {
          min: n,
          max: n,
          sum: n,
          count: 1
        }
      }).reduce(function(a, b) {
        return {
          min: (a.min < b.min ? a.min : b.min),
          max: (a.max > b.max ? a.max : b.max),
          sum: a.sum + b.sum,
          count: a.count + b.count
        }
      });
    }

...then you can distribute this out across multiple threads/machines/etc, update it when new data comes in, reduce in any order.

Side note: that re-implemented scrollbar is terrible. Makes it very distracting to read the whole thing. I'd suggest at the very least halving the time of the scroll "animation", if not ditching the whole thing altogether.

I got a bunch of 500 errors and stack overflows.

Considering "he lacked the attention span" in GolfyMcG's comment, it shows the dev can create, but doesn't demonstrate any long-term follow-through or team dynamics.

So, is it required that you start with an existing project? It seems to me that the only requirement explicitly listed is that it needs to be playable in a browser.

If there's the potential for multiples then I'll have a CameraManager (TheCameraManager) that finds out what's connected to the system and provides enumeration and access. I'll generally try to make the cameras look like a singleton and hide the Camera class. Sort of like a factory, except you'll only ever get N instances of your Camera class for N cameras.

Also, singletons are great in robotics control software. It removes a lot of complexity if you have one singleton corresponding to one device.

I used to play _The (Even More!) Incredible Machine_, which had a similar scheme. You'd be given a page and have to look up a series of three items from the game.

https://www.youtube.com/watch?v=R6etb0_u_hk

Anyone else remember that game?

I think the title was written in the spirit of "It's Uber for <X>". Agreed that it could be clearer though.

I'm in the blue/gold(brown) camp too, although I can consistently see white/gold looking at the top half and blue/black looking at the bottom half.

I came a little late to the party; wasn't really on Twitter a whole lot yesterday.

Does it just show the title of the matched question? I can't seem to get to any actual answers from this.

Theoretically, yeah. Someone just needs to make it "cool" enough that people actually start using it as their primary method of social networking. RSS has a niche now, but it would be really cool if it were adapted to fix this problem.

I think centralization is the problem here. "One central hub" just becomes susceptible to all the same problems that we face with Facebook et al. To truly create a solution to this, we need an open-source service so that people can go to spacebook.com or whatever for normal use, but properly motivated folks could run their own server too. Sort of like Diaspora, only with a centralized hosting option.

You burn out once a year? Is this common? I'm contemplating a venture but I'm trying to evaluate the {mental, emotional, financial} toll it will take before I do.