I'm excited to see where this goes because I think it is a cool application of AI. That said, two of the first three paragraph summaries are wrong in this example:
> [Investor Name] gave [Company Name] the right to certain shares of its Capital Stock in exchange for [Amount] on [Date].
This is backwards
> The Post-Money Valuation Cap is a number that is written in Section 2.
This isn't true, the number is here, "additional defined terms" are later.
- In System Preferences -> Notifications & Focus you can switch any apps notifications from "Alerts" to "Banners" which will make them go away automatically when ignored.
It's feeding stdin to ruby code you specify on the command line, either as an array of lines, or repeated strings. So in:
docker ps | rb drop 1 | rb -l split[1]
The output of docker ps is passed as an array of lines to ruby, and the first line is dropped, and then that output is fed to ruby again, but line by line, so each line is split (which defaults to split on whitespace), and returns the second element. With parentheses for function calls it would be:
Can you give some examples of actionable insights you've gained from having these graphs? Are you using them in acute problem solving or in longer term prioritization of where to spend effort improving? What does your pipeline look like for trying to drill into more detail for a potentially concerning metric?
Does anyone have suggested reading on what the estimates of 8% (or 7% or 5% or whatever gets used) are based on? Is there any data to support that the next 30 years will see those types of returns from the total market on average?
How sad. I got to hear him talk in person about functional reactive programing for musical interfaces, and it's a wonderful talk and really neat ideas. If you're interested, I believe this is the talk: https://vimeo.com/96744621. Rest in peace.
Sure, but my question was in the context of the OP definition of "pair programming culture" as "a team that does nearly 100% pairing ... The day-to-day experience of programming is that of a day-long conversation with your pair"
I'm curious how other things that are intrinsically non-pair activities fit in.
In the pairing paradigm (say that 5 times fast), how much of a typical day is spent actually pairing? How do you manage email or other company wide communication? What happens when a server crashes or another emergency comes up? Or when another pair has a question that you can answer? Or when one member of the pair is also responsible for a deploying something? Or one member has a meeting?
Disclaimer: I've mostly been exposed to the code review paradigm (I work with Paul at `current_job`)
Wow, this is a great story. First of all, props to the writer for weaving a bunch of different threads together in a way that made sense and was understandable to non-mathematicians without dumbing it down too much. And this is why I love math. There are so many great characters and themes in this story.
I love problems that can be stated so simply and yet are so fiendishly difficult to prove.
I love the idea that there is room for everybody in mathematics, from the lone genius outside of academia, to the young post-doc, to the unlikely collaborators.
Most of all, I love the idea that it's okay to fail, to throw out dumb ideas along with brilliant ones and that everyone makes mistakes, even Ph.D.'s in mathematics. We need more of that in education and academia generally.
Wow, I had no idea Github had 158 employees. I guess I mostly hear about their engineering team here on HN, and didn't realize the rest of the team was that big. Congrats on 5 years guys, it's a great service!
Thank you so much for writing this. I've always felt like I was missing something with Backbone -- I knew that it was mostly infrastructure and assumptions that helped organize and clean up client-side code, but coming from mostly a backend/rails background, I never quite understood the assumptions that were being made and the "magic" that has happening behind the scenes. This step-by-step process is really helpful.
I asked stripe about all this in their campfire chatroom last night, and I was hoping they would chime in on this thread, but let me pass along some of what they said.
Their response was similar to what the grandparent articulated: that by using Stripe.js, you're avoiding the storage requirements and thus don't have to do anything extra for PCI. However, you can also interact with their API without stripe.js, which is where you would need PCIDSS and thus the language in the terms.
Now, all that aside, I think you bring up a great point about the gray area and the risk that a security breach would cause. One major difference is that with Stripe.js, a security breach would not put at risk all cards used in the PAST, the way storing them yourself would.
Matt, for irc you should check out Limechat. I just switched from Colloquy and am loving to so far. I set it up with the three panel view, and was at first confused about the lower window (which is like a "everything you can't see in the main room window" view), but i've found myself using it a lot just to glance at conversations in other rooms.
This is such perfect timing for me. I've been bumping into their 80MB memory limit a lot over the past few weeks after launching a new site (they were actually letting me get up to about 120 before killing nginx). I was figuring it was finally time to migrate over to linode and then this! Thank you so much webfaction!
To anyone thinking about jumping in, webfaction has been the best shared hosting provider I've ever dealt with. Lots of preset options, SSH, ability to install stuff from source in your home dir, great email hosting.
Just went and checked it out, the specifically list screen as something they'd like to support soon, but that doesn't work (I think because "Multiple processes with hierarchy" doesn't work yet).
> [Investor Name] gave [Company Name] the right to certain shares of its Capital Stock in exchange for [Amount] on [Date].
This is backwards
> The Post-Money Valuation Cap is a number that is written in Section 2.
This isn't true, the number is here, "additional defined terms" are later.