tieTYT

> [SaneScript] Accessing missing properties throws (on both reads & writes)

Ah, I would love this. I have a small, thoroughly tested JS app (15k+ lines of code) but the biggest pain in the butt to debug is, "how did this 'undefined' get here?" I wish there was a way to fail early without putting tons of guard clauses everywhere.

> Why not just show functions that are easy to use and harder to use, and let callers decide what works best for them.

Won't you be stuck exposing those APIs for the lifetime of the product or risk breaking backwards compatibility?

What if you could make the code significantly faster by changing the parameters you pass in to an internal function? What if you discover a bug that you can only change by changing a method's signature? What if you just want to refactor? Doesn't exposing your internals prevent you from doing these things?

(Note, haven't read the article yet).

What is "this"? You mean blog articles?

It's not clear to me: Is that list at the bottom new things in v.3?

That's great, thanks for the info. I wish most getting started guides would set this up first/early.

The scariest thing to me about AWS is that I might accidentally bankrupt myself while I learn to use it. I've seen horror stories on HN before. Articles titled "How I spent $32k with AWS, a for loop, and a simple typo" or something like that.

Normally when I learn something new, I learn by tinkering and breaking stuff. I don't feel comfortable doing that with AWS. I'm hoping people will tell me I'm way off base because this fear has stopped me from getting the ball rolling.

Missing figures, unfortunately.

EDIT: I was wrong. It's just that the figure is waaaay below the paragraph that mentions it.

Weird coincidence you bring this up. I just found this on reddit: TIL That although we picture the Founding Fathers as old men, many were quite young. By July 4th, 1776, Aaron Burr was 20, Alexander Hamilton, 21; James Madison, 25; John Jay, 29; and Thomas Jefferson, 33.

> The first principle for would-be networkers is to abandon all shame. Be flagrant in your pursuit of the powerful and the soon-to-be-powerful, and when you have their attention, praise them to the skies.

I'm reading "How to win friends and influence people" right now. The author would disagree. He would recommend compliments, not flattery. Compliments are sincere, flattery is transparent brown-nosing that makes you lose credibility. I'm paraphrasing the book not giving my opinion: I have no idea what I'm doing.

That said this is very relevant to me because I've recently quit working as a full time employee for 10 years and want to have a go at consulting for companies. I jumped in head first and it has not gone as smoothly as I would like. My biggest issue so far is I don't know where to go to network with the people that I should be talking to. I can go to free networking events with founders of companies, but all of them seem to be at the pre-funding stage and can only pay me in equity. I'm looking for people that can pay in cash. Any advice would be appreciated.

Interesting theory. What prevents other sites from scraping SO posts? If the answer is "nothing", that suggests it's just a matter of time until it's just as bad. Right?

The one thing this is missing is a search/replace example. That's a very common thing to do and annoyingly clunky in Awk.

I haven't researched it, but I figure if the glassfish developers themselves aren't willing to put in the effort, it must be a big effort.

Interesting. Doesn't git (a pretty new tool) violate this? I think running log from the terminal pauses per page of output but if you pipe it to something it pipes all the content.

We are using an open source app server: Glassfish.

I'd love to be using Java 8 but I can't because we deploy to an app server. The latest version of the app server has some critical bugs that prevent us from upgrading and we can't use Java 8 until we upgrade. We also can't switch to a different app server because the app server dictates which implementation of JPA you use and we wrote a lot of code tied to the implementation.

This makes me wonder if Java EE app servers have ever been marked as "Hold" on any of the previous ThoughtWorks Tech Radars. I certainly wouldn't recommend them.

This is the first time I've heard the phrase "twelve-factor app". Although I'm ignorant of this term and docker, it wasn't obvious to me how it violates the concepts. Which factor does it violate?

For reference: http://12factor.net/

I'd like some clarification. If you purchase a closed source add-on from a third-party, aren't you now locked in to 2 vendors instead of 1?

> Perhaps more useful, we also sifted through and analyzed each post-mortem to identify the top 20 reasons for startup failure.

"But you must provide an email to get access to that."

> Sometimes writing faster code is the difference between using a hash instead of a list. Sometimes it's spending an entire day optimizing a function that's called once. The former is performance aware, the later is premature.

I disagree, it depends on the context. If using your original list is so fast that nobody human can notice the difference, it's a waste of time to turn into a hash, not "performance aware".

Actually, whether it's a "waste of time" also depends on the context. It could be worse. It could make your code harder to understand and maintain.

> The feeling of powerlessness one has when Cabal does not do what one wanted and one does not know how to fix it.

I experienced this immediately after I read Learn You A Haskell and it made me give up on the language. I develop on Windows (currently?) and I was passionate about creating my first hobby project in Haskell. But every direction I turned, I ran into an issue where a dependency or transitive dependency expected some linux library to be there and I couldn't install.

Maybe I'm just spoiled and need to be more open minded. I come from Java-land where I take "write once run anywhere" for granted. I eventually switched to Clojure but that was unsatisfying for different reasons. I wish there was a language with Haskell's purity and type system but Java's ability to "write once and run anywhere".

I think Frege is very close, but I feel uncomfortable learning something with such a small community (damn... I am spoiled).

> The kicker with one-tailed tests is that they only measure ­– to continue with the example above – whether the new drug is better than the old one. They don’t measure whether the new drug is the same as the old drug, or if the old drug is actually better than the new one. They only look for indications that the new drug is better...

I don't understand this paragraph. They only look for indications that the drug is better... than what?

I'm reading the faq^1 and I'm having trouble figuring out why I should use this over MongoDB (even after skimming the very detailed comparison page). From what I gather, it seems like they are pretty similar in features but rethinkdb is easier to administer. What am I missing?

Sorry to be so curt, but I've spent over 15 minutes researching and by now I feel like I should have an high level understanding of the advantage of this database.

^1: http://rethinkdb.com/faq/

How does Erlang deal with these problems? It often touts minimal downtime and the ability to run updates to your code while it's running.

I think that means you can have Process V1 and Process V2 running on the same server simultaneously. If they read from the same database, won't you run into issues?

For those that want to get started, I've been reading the Erlang Thesis^1. It's a really good read. I recommend it even if you don't plan on learning Erlang because it will teach you why it's difficult to build reliable systems when processes can share mutable state.

1: http://www.erlang.org/download/armstrong_thesis_2003.pdf

I have a question as a potential remote employee: If I live in a city with a very high cost-of-living, will it be difficult to find a remote position that pays reasonably well relative to my cost-of-living?

I assume one of the biggest benefits to hiring a remote worker is you can hire someone with a very low cost-of-living and pay them relatively relative to that. But if I'm living in a place with a high cost-of-living and the company can hire someone from any part of the world, why wouldn't they wait and find someone that's super inexpensive?

Is it recommended that you learn Erlang before you learn Elixir, or can you jump straight into Elixir without Erlang knowledge?

Technically, it can act on integers:

    Prelude> let zero s z = z
    Prelude> :t zero
    zero :: t -> t1 -> t1
    Prelude>

t and t1 can be integers. Really the point of my comment is that the article could be written much better (assuming I'm the intended demographic).

To my surprise, the Haskell was not the difficult part for me. I spent more time wondering why this is the definition of "zero":

    zero s z = z

My understanding is you can call this like so:

    zero 3 7 #returns 7

So.... in what way does this relate to "zero"?

I got to the definition of "one" and that made me realize that `s` is supposed to a function (because AFAIK, Haskell can only return 1 thing). This doesn't clarify my initial confusion, but it does make the type definitions a little more concrete in my head.

Yeah... I'm going to stop reading. I think this could be written better. Maybe it would be a good reference if I already had a decent grasp of what Church Numerals are, but I don't.

> when someone offers you an exploding offer, it's because they really, really want you to take it.

Couldn't it be because they've got a lot on their plate and after a certain period of time they want to free up their brain cycles and stop wondering if you're going to accept that deal?

Couldn't it be that you're barely preferred and making the deadline shows them that you're excited about the offer? Missing the deadline shows that you're not excited and they'll know to go with the second best candidate?

FWIW, I'm relating this to exploding job offers as I have no direct VC experience.

Become really good at breaking down tasks into 15-30 minute increments and work on at least one increment per day. You may not get much done per day, but over time you will.