bitcrusher

Dismissing things that don't make sense probably isn't a good idea. Some of the most interesting things I've learned have been from working hard to discuss and understand something that didn't make sense to me at the time.

Also, there are often cases when someone has an idea or thought that isn't necessarily framed with the right wording. That doesn't make the idea invalid and it is often worth exploring to understand what they were trying to express.

These things is a 'waste of time', in my opinion. In fact, it is often the direct opposite: A wonderful use of time.

It's not just Italy. Places outside of Silicon Valley, within the USA have the same outlook.

Personally, I think this 'failure as a badge of wisdom' is one of the 'secret' ingredients for the 'Silicon Valley' recipe.

Yes, but you can use custom kernels with FreeBSD on DO. In the comments:

"FreeBSD droplets do allow you to customize your kernel. Unlike other droplets these boot from the kernel within their filesystem. This is the reason that FreeBSD is not available in NYC1, NYC2, and AMS1 as these regions do not yet support this option."

Oh please. What's the best way to learn a new programming language? Writing code in it. What problem(s) should you solve? Well, there's the crappy foo-bar thing that would be awesome to solve...

That's a WIN for both sides of the equation. You're expanding your knowledge and learning something new; The company is getting the benefits of you learning new stuff. This is how 'engineering culture' is supposed to work.

It's complete garbage to associate this with "exploitation." If the company were saying "this is mandatory that you do exploratory programming on nights and weekends for the next 6 months" then you might have half a leg to stand on.

FlareWorks - http://www.flareworks.co - San Francisco, CA. Bay Area Only Interested in changing the world? Neither are we! But we are interested in having fun and building cool software.

FlareWorks is a visual messaging startup headquartered in San Francisco, California. Our mission is to build a platform for contextual, visual communication between family and friends that is easier and simpler than Texting. In short - "Kill Text". Our company’s visual messaging service —called Flares— uses visual cues, instead of text, to provide communication shortcuts between friends and family. We're a seed funded, early stage startup, so this is an opportunity to get in on the ground floor. You would be engineer number 3. We're looking for Android developers to help us take our mobile application and platform to the next level. Our mobile apps are the face of the organization and, as such, you’ll be on the front lines of creating an application and experience that has the potential to be used by millions of people every day. We're currently in the Apple app store and are now looking to expand into Android/Google Play. Our app was featured as the "best new app" by Apple the first week it was released and we have consistently received great press for our MVP.

Our Stack: * Node for our API. * Erlang/Elixir for our platform.

What we offer: * We're not fans of 9-5 with a lunch break. Work when you want, where you want. Results matter. "Seat Time" does not. * Unlimited PTO. Take the time off you need, when you need it. We don't offer prizes for 'attendance'. * 5K equipment budget. Buy what you want; After a year with us, it's yours to keep. * Company outings. We like to get out and do things as a team. Lunches, dinners, games, volunteering, concerts. We're always on the lookout for things to do. * A real voice. We want to know what you think. If you have an idea or think something isn't working, we want to hear about it. Your voice counts. * Generous options and an actual competitive salary (no low-balling + options bait and switch here ).

What we're looking for: * Android and iOS engineers. * UX and visual design chops. * Meticulous attention to details. * Android: * Animation and the hardware accelerated rendering pipeline as well as OpenGL ES. * Location, Content and Media SDK experience. * iOS: * Core Graphics, Core Animation, Core Data, Core Location * Comfort with rapid iteration and real-time team collaboration. * Excited about and eager to use Swift.

If this sounds like a good fit for you, email us ( jobs@flareworks.co ) and we'll talk.

FlareWorks - http://www.flareworks.co - San Francisco, CA. Bay Area Only

Interested in changing the world? Neither are we! But we are interested in having fun and building cool software.

FlareWorks is a mobile messaging startup headquartered in San Francisco, California. Our mission is to build a platform for contextual communication between family and friends that is easier, simpler and safer than texting. Our company’s visual messaging service —called Flares— uses visual cues, instead of text, to provide communication shortcuts between friends and family.

We're a seed funded, early stage startup, so this is an opportunity to get in on the ground floor. You would be engineer number 3. We're looking for Android developers to help us take our mobile application and platform to the next level. Our mobile apps are the face of the organization and, as such, you’ll be on the front lines of creating an application and experience that has the potential to be used by millions of people every day. We're currently in the Apple app store and are now looking to expand into Android/Google Play. Our app was featured as the "best new app" by Apple the first week it was released and we have consistently received great press for our MVP.

Our Stack: * Node for our API. * Erlang for our platform.

What we offer:

  * We're not fans of 9-5 with a lunch break. Work when you want, where you want. Results matter. "Seat Time" does not. 
  * Unlimited PTO. Take the time off you need, when you need it. We don't offer prizes for 'attendance'. 
  * 5K equipment budget. Buy what you want; After a year with us, it's yours to keep. 
  * Company outings. We like to get out and do things as a team. Lunches, dinners, games, volunteering, concerts. We're always on the lookout for things to do. 
  * A real voice. We want to know what you think. If you have an idea or think something isn't working, we want to hear about it. Your voice counts. 
  * Generous options and an actual competitive salary (no low-balling + options bait and switch here ).

What we're looking for:

  * Android engineers. 
  * UX and visual design chops. 
  * Meticulous attention to details. 
  * Android: 
    * Animation and the hardware accelerated rendering pipeline as well as OpenGL ES. 
    * Location, Content and Media SDK experience. 
    

If this sounds like a good fit for you, email us ( jobs@flareworks.co ) and we'll talk.

FlareWorks - http://www.flareworks.co - San Francisco, CA. Bay Area Only

Interested in changing the world? Neither are we! But we are interested in having fun and building cool software.

FlareWorks is a mobile messaging startup headquartered in San Francisco, California. Our mission is to build a platform for contextual communication between family and friends that is easier, simpler and safer than texting. Our company’s visual messaging service —called Flares— uses visual cues, instead of text, to provide communication shortcuts between friends and family.

We're a seed funded, early stage startup, so this is an opportunity to get in on the ground-floor. You would be engineer number 2 or 3. We're looking for mobile developers, both iOS and Android to help us take our application and platform to the next level. Our mobile apps are the face of the organization and, as such, you’ll be on the front lines of creating an application and experience that has the potential to be used by millions of people every day.

Our Stack: * Node for our API. * Erlang for our platform.

What we offer: * We're not fans of 9-5 with a lunch break. Work when you want, where you want. Results matter. "Seat Time" does not. * Unlimited PTO. Take the time off you need, when you need it. We don't offer prizes for 'attendance'. * 5K equipment budget. Buy what you want; After a year, it's yours to keep. * Company outings. We like to get out and do things as a team. Lunches, dinners, games, volunteering, concerts. We're always on the lookout for things to do. * A real voice. We want to know what you think. If you have an idea or think something isn't working, we want to hear about it. Your voice counts. * Generous options and an actual competitive salary ( no low balling + options bait and switch here ).

What we're looking for: * Senior level Android and iOS engineers. * UX and visual design chops. * Meticulous attention to details. * Android: * Animation and the hardware accelerated rendering pipeline as well as OpenGL ES. * Location, Content and Media SDK experience. * iOS: * Core Graphics, Core Animation, Core Data, Core Location * Comfort with rapid iteration and real-time team collaboration.

If this sounds like a good fit for you, email us (jobs@flareworks.co) and we'll talk.

FlareWorks - http://www.flareworks.co - San Francisco, CA ( Bay area preferred, remote possible ) Interested in changing the world? Neither are we! But we are interested in having fun and building cool software.

FlareWorks is a mobile messaging startup headquartered in San Francisco, California. Our mission is to build a platform for contextual communication between family and friends that is easier, simpler and safer than texting. Our company’s visual messaging service —called Flares— uses visual cues, instead of text, to provide communication shortcuts between friends and family.

We're a seed funded, early stage startup, so this is an opportunity to get in on the ground-floor ( we have not launched yet ). You would be engineer number 2 or 3. We're looking for mobile developers, both iOS and Android to help us take our application and platform to the next level. Our mobile apps are the face of the organization and, as such, you’ll be on the front lines of creating an application and experience that has the potential to be used by millions of people every day.

Our Stack:

  * Node for our API.
  * Erlang for our platform.

What we offer:

  * We're not fans of 9-5 with a lunch break. Work then you want, where you want. Results matter. "Seat Time" does not.
  * Unlimited PTO. Take the time off you need, when you need it. We don't offer prizes for 'attendance'.
  * 5K equipment budget. Buy what you want; After a year, it's yours to keep.
  * Company outings. We like to get out and do things as a team. Lunches, dinners, games, volunteering, concerts. We're always on the lookout for things to do.
  * A real voice. We want to know what you think. If you have an idea or think something isn't working, we want to hear about it. Your voice counts.
  * Generous options and an actually competitive salary ( no low balling + options bait and switch here ).
  

What we're looking for:

  * Senior level Android and iOS engineers.
  * UX and visual design chops.
  * Meticulous attention to details.
  * Android:
    * Animation and the hardware accelerated rendeing pipeline as well as OpenGL ES.
    * Location, Content and Media SDK experience.
  * iOS:
    * Core Graphics, Core Animation, Core Data, Core Location
  * Comfort with rapid iteration and real-time team collaboration.

If this sounds like a good fit for you, email us (jobs@flareworks.co) and we'll talk.

I think part of the reason is that the story is being positioned incorrectly. Yahoo owns 24% of Alibaba, so it's not China vs. Silicon Valley, or any such nonsense.

It's definitely news worthy that they're going to IPO here in the US and they have a HUGE market in China/Asia... Even so, will they be able to crack the US consumer market? Time will tell, but so far, their efforts haven't born fruit.

They have a stealth 'target vertical' shopping experience that's developing right now in the Bay Area, however, they're significantly behind schedule, having trouble integrating teams from several locals and their product is dubiously "useful" at this stage of the game.

All of that being said, eventually they'll find some combination to get a foothold of the US market and it will be interesting to see what happens then as competition heats up.

FlareWorks - http://www.flareworks.co - San Francisco, CA ( Bay area preferred, remote possible )

Interested in changing the world? Neither are we! But we are interested in having fun and building cool software.

FlareWorks is a mobile messaging startup headquartered in San Francisco, California. Our mission is to build a platform for contextual communication between family and friends that is easier, simpler and safer than texting. Our company’s visual messaging service —called Flares— uses visual cues, instead of text, to provide communication shortcuts between friends and family.

We're a seed funded, VERY early stage startup, so this is an opportunity to get in on the ground-floor ( we have not launched yet ). You would be engineer number 2 or 3. We're looking for mobile developers, both iOS and Android to help us take our application and platform to the next level. Our mobile apps are the face of the organization and, as such, you’ll be on the front lines of creating an application and experience that has the potential to be used by millions of people every day.

Our Stack:

  * Node for our API.
  * Erlang for our platform.

What we offer:

  * We're not fans of 9-5 with a lunch break. Work then you want, where you want. Results matter. "Seat Time" does not.
  * Unlimited PTO. Take the time off you need, when you need it. We don't offer prizes for 'attendance'.
  * 5K equipment budget. Buy what you want; After a year, it's yours to keep.
  * Company outings. We like to get out and do things as a team. Lunches, dinners, games, volunteering, concerts. We're always on the lookout for things to do.
  * A real voice. We want to know what you think. If you have an idea or think something isn't working, we want to hear about it. Your voice counts.
  * Generous options and an actually competitive salary ( no low balling + options bait and switch here ).
  * 

What we're looking for:

  * Senior level Android and iOS engineers.
  * UX and visual design chops.
  * Meticulous attention to details.
  * Android:
    * Animation and the hardware accelerated rendeing pipeline as well as OpenGL ES.
    * Location, Content and Media SDK experience.
  * iOS:
    * Core Graphics, Core Animation, Core Data, Core Location
  * Comfort with rapid iteration and real-time team collaboration.

We're hoping for local talent for our first hires, but are open to the possibility of remote for the right person.

If this sounds like a good fit for you, email us (jobs@flareworks.co) and we'll talk.

"Once taught is twice learned."

Still digesting this, but it doesn't pass the smell test. There are too many assumptions that are just plain... wrong.

For example:

There seems to be an implicit assumption that all of the REST endpoints are just maps to CRUD operations. Perhaps for the most barebones, basic API this is true, but service APIs are more than just CRUD ops. They're abstracted interfaces to a complex series of tasks (for the sake of argument, we'll call them 'orchestrations' ). Just because you're doing a "POST" to /user/foo doesn't mean that the service is only doing a simple insert. It might be looking up similar users, sending out notifications, validating data, de-duping, etc.

The more I think about this the less sense it makes. Perhaps I'm missing something.

That has not stopped them from making it available on the iPad... It works just fine, you just have to use the browser to buy new things.

It's interesting how different perspectives work:

> The gaming aspect of this will make it a winner. OUYA's big problem is that it didn't do streaming and was a bit clunky. Amazon has a big game library and just needs controller support.

I think the gaming aspects are the worst part and are entirely useless. Who wants to casual game with an underpowered box on a giant TV screen? Goofy games are fun on a 4-7" screen because expectations are low. On my TV I expect a crazy immersive experience, not "Candy Crush".

Perhaps they would have been better served by spending their time getting HBO-Go, Starz/Encore and Spotify all hooked into their little box. If they want to be the central hub for all things "media" and want to compel people to move off of their existing platform ( Roku and ATV ) it seems like they need to offer a more complete package.

It's a well known technique... Stream of Consciousness writing in the morning is very effective at clearing out the mind before the day starts.

Some Artists use this and call it "morning pages" (Check out "The Artists Way". )

Sure, email address is in profile, email me and I'll send you one.

Sure, my email address is in my profile.

Following dewey's lead, I've got 6 invites to share. Shoot me an email or reply here. First come and all of that.

You're kinda all over the place trying to defend MongoDB...

So, what is your stake in it? You like it? You have a lot of customers on it and you want to validate your decision?

I'm just curious, because by my tastes, MongoDB is an awful database. It's like the PHP of Databases. It seems like there are a lot of better choices out there especially in the last few years.

Absolute poppycock. Redis, Riak, Postgres, MSSQL drivers all work quite well.

Did you?

That works perfectly if you already have python3 installed.

"Quite the contrary. I've had abundant experiences with both event-based models (which hardly started with Node!) in several paradigms (GUI, server, network) and models like Erlang, Go, and Haskell. It is no contest. The latter is sane. The former is not. If you have the opportunity to choose freely, and you choose the event-based model, you have chosen poorly."

Nonsense. First, if you read what I said, I explicitly stated that this IS NOT new and has been around forever in many different forms, even citing some of the same domains you did ( GUI ).

Second, everything you state here can be summed up with "I don't like it." Your preference for the models in Erlang, Go and Haskell are opinions, nothing more. I agree with you that there are some interesting approaches to different event-systems, across many different styles and languages, but there is nothing inherently superior to one over the other, beyond "taste".

"Believe me, it is not the critics of Node who are the inexperienced ones. All the evidence I've seen points strongly in the opposite direction. Node advocates could start by getting their understanding of how their competition works out of the mid-1990s."

I don't believe you, because I've been programming since the late 80s/early 90s, and I think Node is a fine choice for building certain types of software. I've been around the block more than once myself, through a ridiculously long list of programming "shifts".

The things you're espousing about Erlang, Go and Haskell's superiority were the same things that C/C++ programmers were saying about Java in '95.

"Ironically, in the end Node will eventually work their way around to working like these models. The signs are all there, the parallel evolution is clear, and apparently the process has already begun with Meteor. I wonder if the community will ever acknowledge how crazy they've been as they careen from one "solution" to the next at breakneck speed, all the while crowing about how much better their stuff is, even though what they consider "their stuff" can't seem to stay stable for 3 months?"

I don't know where this 'community' is, but frankly, most communities have advocates that talk too loud about things and make ridiculous claims about things. I believe it was Scott McNealy who said "I don't know what your question is, but the answer is Java". These things have nothing to do with actually writing code and creating good/usable software. I submit that you should ignore these people and focus on working with tools that help you write software.

If Node does not help enhance your ability to create software, it's not the tool for you. That doesn't mean that Node is inferior or stupid or useless, it just means it's not the right tool for YOU to use.

I have a hard time 'listening' to these rants about how hard it is to reason about asynchronous code. It's NOT hard, it's DIFFERENT.

This isn't some new Node-Sauce. The idea of an event-loop asychronous programming domain has been around forever in various forms, first in games and desktop GUI programming and the way one reasons about it hasn't changed, just because it has been applied to a new class of problems.

I suspect that there are two things going on here:

1. A LOT of people dislike Javascript. As a result, they're starting with that negative point of view and then finding reasons to support it.

This is not unlike people who argue about Python white-space. They're really saying "I don't like Python." The white-space issue is incidental.

2. Lack of experience / exposure

I suspect that folks who have trouble with this, frankly just aren't experienced enough. I'm not saying they aren't skilled, just not experienced in this realm.

Once upon a time, these same sorts of 'arguments' were used against Ruby ( ala the Rails explosion ). Nothing much has changed about Ruby, other than it has managed to be around long enough to influence a new generation of programmers.

What markets are you trying to get more in front of? US? Europe? China?

What device levels are you trying to get in front of?

Android seems like a "no brainer" until you start looking at the details... For example, if you cut out all "cheap shit 2.2 android devices" and focus on new(ish) Android 4.0> things get REALLY murky... In the US iOS still holds a lead over Android in those markets; in Europe Android is ahead, but then you have localization to deal with.

Additionally, Android might have an edge in some markets, but the fact that iOS users actually PAY for apps also makes a big difference.

The point is that Android is a sensible choice but it's not an automagic choice, nor is it as cut and dry as it appears.

Generally speaking, it's the lack of a linear service bus and orchestration.

In a 'traditional' SOA architecture, the workflow is defined as a linear progression from one state to another, where each 'service' mutates ( or not ) the state of the data.

Determining 'which' services are used/called in the service bus is typically defined in an orchestration.

They definitely have some similarities, however one thing to note about 'Architecture' is that it's often more about ways of thinking about a problem as much as it is about 'solving a specific problem'.

Another helpful comparison might be:

SOA is like GNU Hurd and Micro-Services are like Unix.

Personally, I think using NPM is more idiomatic; Both Grunt and NPM are third-party tools, however NPM is FAR more pervasive with Node than grunt is. Essentially, if you write Node, you use NPM. Not so with grunt.

It's a total nit and pet-peeve for me, but one does not "Architect" code. You architects domains.

You "design" code.

It has never polluted the water table? Oh really?

http://www.usatoday.com/story/money/business/2014/01/05/some...

That's the first hit on a google search.

hold down control and hit w, twice, when in visual mode. That will move the cursor from frame to frame.

If you want to see a 'file browser', open VIM and type ":sp ."

Strictly speaking you don't need nerdTree (though I love it ).

That's alright... you wrote it anyway.