vqc

Would this be useful for people who wanted to leverage GPUs for deep learning, but didn't have the wherewithal or the willingness to set up all the dependencies on the host machine?

you can use this javascript snippet as a bookmarklet:

  javascript:window.location.href = 'https://www.facebook.com/flx/warn/?u='+location.href

and it will let you avoid paywalls

Are you sure Twilio or Nutanix didn't file confidentially before its S-1 was flipped public? I'm actually not sure if there's a way to tell, other than a leak.

Do you have any info that companies that don't have great numbers tend to file S-1's confidentially compared to companies with great numbers?

In my experience, companies that can file confidentially will, regardless of their numbers (and I think all companies now have the option to do so).

Isn't this what the enablement and written description requirements are for?

W/r/t anti-gravity, what about written description and the enablement requirements?

What about businesses tracking and reporting on former employees: http://www.npr.org/sections/money/2016/10/28/499805238/episo...

The employees, apparently, don't usually get access to their U5.

The footer says powered by OpenGov and ckan.

I think it'd be interesting to see the rate of success for rejected companies.

Law firms are now internally tracking the number of hours spent on units of work (e.g. motion to dismiss, MSJ, etc) so that they can provide much more accurate pitches and estimates of cost.

On the latter point: https://www.judicata.com/ understands legal research and has built a legal research tool in the right way.

I get the feeling Big Law firms are reaching the point where they can no longer rely on increasing hourly rates as a primary source of growth. And I think for the first time in the the history of Big Law, the incentives are such that efficiency might finally be valuable. It might be the only way these law firms can continue to grow revenue. Rates can only go so much higher and there aren't that many more hours in the day.

Maybe investor expectation is that a company like HTC or LG or some other none-Samsung/Apple/Google/Amazon company will buy Essential in order to get a strong team that is building a suite of products that tries to compete with Samsung/Apple/Google/Amazon. Can that justify the valuation?

everything by Reg “raganwald” Braithwaite is fantastic

All doctors are human. They probably have higher averages on [X things required to make it through med school and residency] but that doesn't guarantee they are above average on anything else. Like ethics. Or avoiding certain biases.

This is a problem for many of the municipalities in the United States. I'm not familiar with the history of how this ended up happening for Georgia, but for municipalities the cause is often the economics of codifying and publishing the official code.

Assembling the laws into a usable code is extremely labor intensive. Someone has to figure out where the new law fits into the old code and copy and paste as necessary. Governments often outsource the work to a third party vendor in order to free up internal human and monetary resources. The end effect is that the codifier controls the code.

There are all kinds of downstream effects. For one, computer-readable formats of the law are nonexistent. This also means that there is a huge barrier to creating interesting new technologies on top of the law.

I'm the cofounder at Open Law Library (http://www.openlawlib.org), a non-profit that is trying to fix this problem by introducing technology at all stages of the law making process. We're working with Washington D.C. right now, and you can find a glimpse into the future at https://beta.code.dccouncil.us/dc/council/code/ (bulk downloads available at the link at the bottom).

Version control for law drafting and other dev-like tools is something that http://www.openlawlib.org is working on.

I think there is a strong push for standard provisions, definitions, etc. The problem is that while every relationship is similar, there are always enough edge cases that forms are often only good as starting points. W/r/t to building knowledge bases for law firms, parsing existing contracts so that they are searchable and usable as sources of knowledge is a hard problem.

Some well drafted agreements will purposefully not discuss certain conditions the parties are aware may occur. Sometimes that's the only way a deal gets done. Resolving the relationship between the parties when that condition does occur is a complex dance of fitting square situations into round contract provisions and lots of phone calls.

It seems impossibly complex to predetermine the resolution of all possible human outcomes and encode it into a smart contract within a reasonable amount of time and effort.

Open Law Library (http://www.openlawlib.org) | Software Engineer | U.S. | REMOTE | $90k-$110k+

Open Law Library is a small nonprofit tech startup and open access legal publisher dedicated to making the law accessible to all.

We take tools and techniques developed for engineers to publish software code - linters, compilers, continuous integration/deployment, VCS, etc - and adapt and transform them for use by governments to publish legal codes. Governments use our tools to save time and money and publish laws in human-friendly and computer-friendly formats.

If you are looking for a meaningful way to contribute to our democracy, you find joy in building the perfect tools for your users, you like deep and challenging problems in such diverse areas as version control, DSL design, UI/UX, and NLP (more accurately, LLP - Legal Language Processing :), and the idea of helping build a team excites you, contact vchuang at openlawlib dot org.

We are looking to fill two types of positions:

Engineer with Legal Experience

We serve our government partners and their citizens by quickly and efficiently solving their legal publishing needs through technology. But every government is different, so we are always looking for strong engineers with legal experience who can quickly understand our partners’ needs and customize our software to their specific requirements. If you are a engineer with legal experience - lawschool grad, paralegal, or lawyer - come apply your passion for technology and the law to meaningfully change how the public experiences the law. When applying or inquiring, please include the phrase law in square brackets in the subject line.

Developer Tools Engineer

We are looking for an engineer with extensive experience writing developer tools who is interested in applying that experience to legal writing and publishing. If you have experience with IntelliSense, IDEs, linters, compilers, etc, and you want to apply it to a completely new field, we’d like to chat! When applying or inquiring, please include the phrase tools in square brackets in the subject line.

How prevalent is the use of non-Word tools in drafting legislation? At Open Law Library[1], we're building a linter for legislation drafting as a Word plugin under the assumption that most drafting is done in Word. Would love to learn more about your process (vchuang at openlawlib dot org).

[1] www.openlawlib.org

Judges like to see how other judges have ruled in similar situations. A generic SCOTUS opinion on a topic doesn't help too much.

We get them directly from the source.

Previous attempts at accomplishing our mission saw organizations scraping government websites and re-hosting the laws on prettier websites. The problem was that a) the laws were only as up-to-date as the law the governments made available (which, unfortunately, are not up-to-date at all) and b) the projects were not sustainable because no one pays to access the law and websites needed updating every time the law changed.

Sites like these are potentially very harmful. They haven't been updated in years and people who stumble upon them and miss the fine print end up relying on laws that have long since changed.

Because timeliness matters, the only way to guarantee that we get it is by working directly with the governments. So we build software into the law drafting, codifying, and publishing process that governments can really benefit from and enjoy using. The software changes the economics of codification and publication and permits publishing the laws freely and openly.

That is magnificent. It seems to "end" at the province/territory level (*this is not a critique at all). How does lawmaking work at the city level?

The contact form goes straight to my email. Also try vchuang at the domain.

With respect to contributing code, the short answer is that we're not sure yet. There is certainly no shortage of code to write, but we want to make sure that we work with volunteers in the right way. For anyone that's interested in please reach out here or through the contact form on our website. I will personally respond to everyone.

Other than writing code, we need advocates in and out of government who understand and believe in the value of free (as in freedom) and accessible laws. Contact your local, state, federal representative and let them know that free and accessible laws are important to you. Let them know that a system exists that can not only make this a possibility, but that it will also make their lives a lot easier.

We would also love to hear about what you would want to build on top of computer-readable, always up-to-date laws that could programmatically alert you when something changed and let you diff against old versions of the law. E.g. a) internal annotations for civil servants that wouldn't immediately be obsolete once the legal code changed; and b) legal alert system for the part of the law you care about.

We'll put together a form that makes it easier to collect this information!

I'm not familiar at all with Canadian law. Does canlii.org provide statutes, regs, case law from every jurisdiction from the local level (cities/towns) up through the federal level? Is this a distinction that matters?

Casetext and Judicata are great companies working on searching through judicial opinions. There's a lot to be said about PACER and publishing state judicial opinions. Suffice it to say, those companies could probably save a lot of time on parsing and focus on other problems instead if judicial opinions were released with some structured information, e.g. party names and procedural posture. Open Law Library makes it possible for legislatures to, among other things, publish their laws in structured formats.

One thing to consider is that on a day-to-day basis, an individual might be impacted more by city/county/state law than by federal law.

#2 is a really big barrier to innovation in this space.

Another issue is that the economics of codification and publishing disincentives existing publishers from releasing laws and codes in open and accessible formats. And without open and accessible formats, it makes it extremely difficult and unsustainable to build things on top of the law.

Co-founder of Open Law Library here. Happy to answer any questions about what we're building, the law, and anything else people are interested to discuss.

Open Law Library (http://www.openlawlib.org) | Software Engineer | U.S. REMOTE

Open Law Library is a small nonprofit tech startup and open access legal publisher dedicated to making the law accessible to all.

We take tools and techniques developed for engineers to publish software code - linters, compilers, continuous integration/deployment, VCS, etc - and adapt and transform them for use by governments to publish legal codes. Governments use our tools to save time and money and publish laws in human-friendly and computer-friendly formats.

The founders are two lawyer/engineers. Our funding is a mix of donations, grants, and government contracts.

If you're looking for a meaningful way to contribute to our democracy, you find joy in building the perfect tools for your users, and you like deep and challenging problems in such diverse areas as version control, DSL design, and UI/UX, then we would love to have you. To apply, email vchuang@openlawlib.org with "[Your Name] - Software Engineer - HN" as the subject.

Experience with C#, .NET Core, and building dev tools like IntelliSense is a big plus. Government lawyers live and breath MS Office, so our tools must integrate seamlessly with their MS-centric workflows.

FYI: "they immidiatly" --> "they immediately"