integraton

17 ms·

121.
by integraton 13y ago
It almost makes him a folk hero for anyone else running up against the "cultural fit" barrier.
122.
by integraton 13y ago
It's interesting how neither of the founders fit any of the stereotypical valley founder profiles. They don't look like Mark Zuckerberg, they are older, Brian Acton barely used twitter, and his tech background is more traditional
123.
by integraton 13y ago
The Bay Area tech community has a widely-held dogmatic bias against remote teams due to a widespread belief that remote teams make it difficult to communicate and create a company culture. Outside of the Bay Area remote work is more accepta
124.
by integraton 13y ago
Customers should not be able to access other customers' data under any circumstances.
125.
by integraton 13y ago
Any company that has ever stored data on DigitalOcean now needs to operate under the assumption that other DigitalOcean customers have accessed it. Even if every staff member believes they checked the "Scrub Data" checkbox or used
126.
by integraton 13y ago
> Who cares? I care. Semantic HTML is easier to work with when creating, maintaining, interacting with, or consuming HTML.
127.
by integraton 13y ago
I'm guessing by your name that you are the author. In the post you ask: > why does every single Sass/Less framework suggest first in the documentation that you should write your HTML like this? Most major Sass grid frameworks
128.
by integraton 13y ago
Regarding point 1, there's a widespread view in the Bay Area that it's good to get a "fresh" perspective in companies that are toxic enough to continually burn out employees, which is many companies, probably most. Furth
129.
by integraton 13y ago
(In response to some of these comments) Concise, semantic markup results in: * less complexity * easier maintenance * greater portability For one example, what happens when you want to use another grid framework instead of
130.
by integraton 13y ago
FYI, big_red_text is presentational (specifies size and color, while saying nothing about what the role or purpose of the text is) while alert is semantic (describes the content, says nothing about presentation).
131.
by integraton 13y ago
Launched with a Series A in 2009, has taken 3 up rounds of funding in the years since, now files for an IPO in 2013, exactly 4 years later. Not only is this a textbook VC-funded startup, it's pretty much a perfect illustration of the i
132.
by integraton 13y ago
See "github flow": http://scottchacon.com/2011/08/31/github-flow.html
133.
by integraton 13y ago
Really happy to see this. The only thing that seems to be missing is pl/v8 support. In case anyone from amazon is reading this, I've noticed that the functions floating around on github for the new json data type are using pl&#x2F
134.
by integraton 13y ago
Microsoft absolutely does implement experimental features and use vendor prefixes when it suits them. See, for example, CSS Grid Layout: http://caniuse.com/#search=CSS%20Grid%20Layout
135.
by integraton 13y ago
See slide 44 here: http://thebuild.com/presentations/pg-as-nosql-pgday-fosdem-2... GIN indexes are big, but Mongo's indexes are bigger than all other PostgreSQL indexes, and Mongo also requires much more space for
136.
by integraton 13y ago
See also the PostgreSQL as a Schemaless Database slides (includes several benchmarks vs MongoDB): http://thebuild.com/presentations/pg-as-nosql-pgday-fosdem-2...
137.
by integraton 13y ago
Just for the record, my comment didn't intend to imply that JVM frameworks are strictly better in all cases, and I don't believe that at all. In fact, I'd argue that for the majority of applications, choosing any modern frame
138.
by integraton 13y ago
Summary: if you want performance, use Java, Scala, Go, Clojure, Lua, or C++. Honestly, now with all the great Scala frameworks, Clojure, and the ability to run Rails, plus Cassandra, Storm, etc, I'm a little creeped out that I'm a
139.
by integraton 13y ago
> [1,2,"10",3].sort() [ 1, '10', 2, 3 ] That's the problem.
140.
by integraton 13y ago
Both Python and Erlang would return [1,2,3,"a"], Ruby and Clojure won't allow the comparison. Either of these approaches makes more sense than JavaScript's.
141.
by integraton 13y ago
Yet somehow it works just fine out of the box in plenty of other languages, including Python, Erlang, Clojure, Ruby, etc.
142.
by integraton 13y ago
It's not delivering instant gratification now. More importantly, it's very standard practice to do asynchronous jobs and notify users on completion, as seen in the data export or input features on many web services. Whether users
143.
by integraton 13y ago
It looks like you and jroseattle are demonstrating the main two competing views about how to approach new software projects: 1) deterministic, controlled, strong planning, avoidance of failure vs 2) nondeterministic, flexible, embracing unc
144.
by integraton 13y ago
Market share is often not the best metric to base those decisions on, especially considering iOS has historically generated more revenue for developers than Android, despite market share. It's also pretty common for companies to sink m
145.
by integraton 13y ago
If you make 12 schema changes in month 1 and then no schema changes for the next year, does it really make sense to keep a month's worth of data in 12 different formats and maintain code to support all of the different versions? Why no
146.
by integraton 13y ago
Agreed. PostgreSQL: ALTER TABLE posts RENAME COLUMN author TO writer; MongoDB: db.posts.update({}, {$rename:{"author":"writer"}}, false, true); (I'm excluding RethinkDB since it's still under
147.
by integraton 13y ago
You are misusing the word "proprietary." http://en.wikipedia.org/wiki/Proprietary_software
148.
by integraton 13y ago
> Do you always start with the perfect data structure? I find myself adding, removing, and restructuring schema often. Which is why it doesn't make any sense to claim that using MongoDB somehow eliminates needing to migrate your d
149.
by integraton 13y ago
> You don't need to worry about updating the schema at the db level What's your magic non-db level, supposedly-easier-than-updating-a-schema approach to renaming a field common to all existing documents in a collection, eg, r
150.
by integraton 13y ago
> while it's pretty easy to do schema migrations, it's not easier than _not_ doing them. Regardless of whether you are dealing with a strict schema or flexible schema, you still have to make changes to how you structure your

More ›