I wonder if it's possible to create a streamlined platform for this kind of work. Like others mentioned being able to start at an outline stage and then move on to fleshing the parts out would be interesting. I could see the outline being its own repo and each "unit"(probably chapters) get their own repo and maintainer. Nightly builds could be conducted to merge the work in the repos into a coherent whole, reconciling missing parts with their outline bullet points. An interface over the "build" to make quick commits and PRs would be nice too.
Additionally a community style guide and "story bible" would probably be in order. I believe a lot of writing projects which involve a large number of writers like video games and TV series do things like this. On an unrelated note, are there any tools to enforce natural language writing style compliance? Like code linters for human text?
Wow, as someone that switches between two language inputs(coincidentally English/Japanese actually) a lot on a variety of OS's, and never uses caps lock, I think this is a great key-binding.
This is a bit of tangent, but I looked up Idris since I'd never heard of it. I'm currently learning Haskell and they look really similar. What differentiates the two? What can you do in one that you can't do in the other?
And it's equally possible to interpret this data positively. Perhaps VCs are becoming more selective and concentrating their money on better teams/ideas instead of casting as wide of a net as possible(I am not saying this is actually the case).
I don't understand why so many journalists try to find catastrophe in the absence of contrary evidence.
What's the financial outlook for this career path? I've always heard bad stories about early hires dealing with a below market salary(for a while) with worthless stock options. Is this a myth? It never made sense to me since I feel an early hire should make significantly more than average, since they don't have the power/equity advantage of a founder, probably have to work long hours, and a large part of the success of the company rides on their shoulders.
I think even before you bring responsibility into the picture, there's a lot for each actor in this situation to gain from reestablishing communications(I certainly can't see what they would lose, except for face). This is assuming the other party is mature and rational though.
For Clojure there's a plugin(albeit a very big plugin) over IntelliJ IDEA, called Cursive that I've heard a lot of nice things about: https://cursiveclojure.com/
I wonder how this will affect the Internet Archive. I understand they're based in the US(and hopefully their servers are too), but will the EU courts take any action if a sufficiently high profile lawsuit occurs over the archive's contents?
I know of one startup, Compathy(in Japan) that are working the other way around -that is, they're building a product that's first for post-trip sharing and then adding pre-trip planning elements/partnerships to it:
I think this is a good strategy since even a small population of traveling power-users who are keen on sharing their experiences can generate a lot of content and value for your site.
Perhaps Keurig should print their logo onto the cups with said special ink, and the machine should identify the logo with an image matching algorithm. If I understand trademark law correctly, competitors wouldn't be able to reproduce the Keurig logo without the strong possibility of facing repercussions for trademark infringement. I mean in reality it wouldn't work well at all and just make consumers pissed, but I wonder what the legal situation would be if they could pull it off.
Perhaps Keurig should print their logo onto the cups with said special ink, and the machine should identify the logo with an image matching algorithm. If I understand trademark law correctly, competitors wouldn't be able to reproduce the Keurig logo without the strong possibility of facing repercussions for trademark infringement. I mean in reality it wouldn't work well at all and just make consumers pissed, but I wonder what the legal situation would be if they could pull it off.
If the only requirement is to run it on a raspberry pi, and you find that a RDBMS will be too resource intensive, you can always use one of the cloud data storage services out there. Amazon has an RDS offering as part of AWS, MySQL, Postgres, etc. Then your app only needs to talk to the database over the wire with zero local resource consumption by the database.
I work for a fulfillment house, we do tens of thousands of orders a month. Despite this, we're still what would be considered a "small business". Forecasting has been a really big pain point so far so we're watching AzureML closely. If they can make this as low-configuration as they promise I think it'll be killer for us, along with many other small businesses with big logistics components that have a LOT of data they wish they could act on.
Additionally a community style guide and "story bible" would probably be in order. I believe a lot of writing projects which involve a large number of writers like video games and TV series do things like this. On an unrelated note, are there any tools to enforce natural language writing style compliance? Like code linters for human text?