Though, that said: there's no guarantees that when you have the conversation in April 2019 that you'll be in the best hiring market for your interest in the history of ever, which is approximately where we are right now.
Us Brits might have conceived the idea of "received pronunciation" as a location-free English accent and exported it via international schools (though South Africa is the only place I can think of with non-trivial numbers of people whose accent is defined more by RP-norms than local norms), but in practice, very few people speak anything resembling the traditional RP, an accent most Britons would see as glaringly indicative of some combination of the speaker's private-schooling, age and pretentiousness. The southern (or subtly southern-ised) English accents that are most predominant in British run media are quite starkly different from traditional "RP" or "Oxford English" in terms of pronunciation and perceived social prestige.
Yes. From a migrant country like Australia, if you flick on SBS TV News, you get the same phenomena. Fluent English, accented but neutral foreign tongue. You can hear the English equivalent on BBC World News with the announcers speaking RP. 
"Contradictions do not exist. Whenever you think you are facing a contradiction, check your premises. You will find that one of them is wrong." - Ayn Rand
To follow up with 0x400614's answer, you'll want to look at `ab` - ApacheBench.
> fair to the people who are relying on it for their organization?
If there are large-ish organisations that need it, they could take it over or pay you for further development if you are interested in doing that.
So for the chromium project I'd try to work my way through, by performing an action. Then asking how it is performed, and follow the code through.
Hope this helps.
1. Download the code and figure out how to build it.
2. Figure out how to run it.
3. Figure out how to attach a debugger to it.
4. Figure out where to listen/break for an event whose purpose you pretty much understand (like the initial DNS request).
5. Follow the code down the rabbit-hole, you'll be amazed at how quickly it connects you to everything else in the code.
It worked pretty well for me - within 2 years.
There, you're going to have insights. You're going to encounter itches you need to scratch. You're going to find questions that pop up--why you're feeling out of sync with something, why you're annoyed by something.
With luck, you're going to create things that no one else has created. And even if someone else has created it, something led you to create it in the way you did.
All of these observations of self can be noted when they occur, and they can form the premise for an essay. Use a sticky, or carry a Field Notes notebook. Stop and capture them.
Maybe 95% of them will be garbage. File them away--maybe journal them. See if they come up again. If they do, then you're onto something.
The other 5% may write themselves.
For me, essays are about connecting ideas from disparate domains.
Short version: if you have nothing to say when you sit down at the keyboard, then get up from the keyboard and interact with the world around you, and observe. You'll be cured in no time.
For example, there's someone on LW who wrote a chatbot that successfully hypnotizes people over IRC. Would you read an essay about that? You bet you would! There's also someone who sold drugs for bitcoin, and someone who doxxed drug lords, and someone who won AI-box experiments, and someone who independently invented cryptocurrency... My own most successful essays on LW came as as a side effect of my work on decision theory math, which had other nice effects as well (like being invited to speak at conferences). Even Eliezer's essays were a side effect of his attempts to figure out friendly AI, rather than "hmm I want to write something interesting today".
So, instead of mulling over which obvious thing you'd like to write about, try to do some novel work that interests you on its own terms! When you try to describe it afterward, I promise you the words will come much easier.
"I don't have anything to say to people who know less than me, because explaining obvious things seems boring [...] I feel like they are smarter than me and already know everything I am about to say"
I've suffered from this for years. 'That idea sounds stupid - it's far too simple', or 'if I write this / make this my peers will judge me'. When the reality, the people you look up to probably aren't looking at you, and there are far, far more people who, despite you thinking something is obvious, will find value in your work.
Reading HN (and similar) we're exposed to some incredible people - those at the top of their game. Because you or I am not that person doesn't mean that what we write doesn't have value to someone.
My friend has recently published his third novel. It's quite good. He started writing when we lived together at university 15 years. I used to read his short stories back then. It took him 13 years to publish his first book. But he wrote voraciously in the meantime. Most of us don't start great - it comes with practice.
Basically what I'm saying, is pick a topic - even one you consider too simple - and get started. Write 300 words. Then do the same tomorrow. Then the next day. Your writing will improve, you'll read more, research more, learn more - and new ideas will come to the point where you'll have more ideas than time. Like the writing itself, it comes with practice. And those 'obvious' topics you start with - they'll undoubtedly benefit someone in the long run.
1. Writing is a conversation. If you're ever stuck in front of the computer, try using a voice recorder instead (e.g. while going for a walk, or while sitting in the sun somewhere) and then transcribe what you said. I find it has magical effects of simplifying sentences and keeping writing interesting.
2. Write with a goal and a reader in mind. Do you want to inform/describe something or convince/sell something? Who are you writing to? When in doubt, write to inform, try to summarize and distill the essence of the topic.
3. Do not pervert the English language, e.g. if you say "utilize" instead of "use", I hate you. More on that front:https://www.mtholyoke.edu/acad/intrel/orwell46.htm
4. Keep it short: in each sentence you're either getting to a point or setting up some context that will allow you to make a point soon.
You're probably missing the value proposition of your writing in general (what is your set of essays giving to the people who read it), and the thesis of each post in particular.
For the VP I use: "My essays all about helping _________ learn/be/do/become ___________."
Once you've got that value prop, you can get specific ideas by thinking about the type of person you're serving (the first blank) and thinking about the sort of questions that person asks you over a beer when you're hanging out with them.
Or you can use trigger questions like:
* Mistakes you've made or seen in this industry* Most common bad advice in this industry
Etc etc. I made a little interactive version of this process at http://whattowrite.org (it's a free and unsupported old hobby project, but it works all right).
Good luck. In the early days, essays/blogging are more about refining what you think, so don't worry too much about whether or not people read it. Write for you first (but with a reader in mind so you don't wander all over the place).
At that point there will be bits of the topic that I don't think any of the articles captured completly or parts where I agree with one and not others. An original point of view comes out of the synthesis.
If I am struggling at the stage where I spin the notes out into exposition I follow a relativly simple framework that forces me to keep writing. I learned it for exams but I think it is pretty versatile and adds clarty where otherwise you would be waffeling: DICE
>>Define: Define the view / theory / idea / term under consideration. Sometimes this will be pretty involved and amount to the meat of your exposition. If it is getting too long though then you should break the concept up and DICE individual parts as well as the bigger picture.
>>Ilustrate: Give an example of the thing under consideration in non abstract terms.
>>Contrast: Define the contrasting ways of understanding or a competing theory or an example of something that isn't covered by the theory.
>>Explain: Explain what motivates the theory you are considering and why it is different from alternatives.
After doing that for all the parts involved in the topic I usually have some areas that the original articles I considered didn't touch on. Then I get into evaluating.
People imagine that originality is blue sky thinking. Occasionally it is. But usually it is adding clarity or going further than someone already has on a particular topic or presenting old ideas in a new light. Often times a good reading of existing views adds light where a radical new approach just adds heat.
#1 I don't know enough about the content. I love when I have this problem because it means I get to have unique (to me) experiences that will help me flesh out my idea. I also realize that I'm not in a position to write anything, which relieves some pressure.
Unfortunately, "not enough experience" is not one of my common hangups. Which leads me to....
#2 I have a mechanical problem. Uh, I hate these, because they come in all forms. It could be that I'm writing in a style that I'm not used to. Or that I'm trying to write about a topic in a blog post that is meant for a book. Or my first draft is a dumpster fire. Or I can't get through a first draft because I'm worried about said dumpster fire. Or my idea isn't organized. Or coherent. Or maybe I'm a terrible writer and should give up.
And on and on and on goes the spinning top if self loathing.
To combat it, I do a few things. First I make sure the idea and the medium align. You wouldn't want to write a blog post about the geo political tensions the Syrian refugee crisis has caused much like you wouldn't want to write a book about your mom's famous beef stroganoff recipe.
Once you feel they align, tell yourself you're not a genius. Really, do it. What you're about to write will be derivative and boring. It's going to be the steamy turd you wish you never wrote.
Then polish the turd. Revise your writing the best you can. And finally have someone (with some sort of credentials) critique it. Or if you're feeling daring, set it off in the wild. After you do all that, put that piece out of your head and start something else.
This advice, in and of itself, isn't novel. Hell, someone on this thread's handle is FailMore. But that's all it is. Reps, fucking up and learning from it.
And remember you're not the smartest guy in the room. So don't pretend to be. But you can be interesting to some people, so work on that.
>And if you're going to write, write what you want to write. The odds against any creator are insane. If you're going to devote months of your time, don't let it be for an idea you think will sell. Odds are it won't. Write something you want to write, or need to write. Write for yourself before anyone else. I'd rather read someone who is excited and passionate about what they want to say than someone who's obviously trying to say what they think I want to hear.
I had the same issues with my writing recently (why should I even write anything when there are far better people writing about these things). It boiled down the following for me :
1. Self Learning (Writing about it makes you understand it betteer)
2. Sharing knowledge (I want the knowledge to spread)
3. Network Effect (People I know are far more likely to read my post as they trust me)
4. I love writing
Coming up with topics is harder. I tend to read a lot, and whenever I read something I already knew, I put it in my "to-write-list". Essentially, the idea is to write things that you'd like to read yourself, but can't find anywhere. Another good idea is to take "auxiliary" topics instead of a core topic. This means finding things that are interesting enough only when taken together. For instance, don't write about Machine Learning, write about doing Machine Learning with a specific toolkit or language.
Specific topics are always better than vague ones, in my experience.
Verbal style obviously isn't written style. I edit things after I have a lot more words on the page. But that out-loud Q&A gets my juices typing.
So I think the first thing you need to evaluate is whether you really want to write and why. If the answer is you want to seem sophisticated and earn the intellectual respect of being a writer then I can't give you any advice except that maybe you should reconsider the decision to write. Write about topics that interest you. Where does your mind wander when you are in the shower? That's what you should write about. In most cases this is not a topic that you've already fully understood. Those topics aren't interesting any more because you already know the answers. Interesting topics are those for which you need to do additional thinking and additional research. Write about what you are learning now.
It is a gross and yet liberating label to what we do. By just getting the ideas out there in a very loose, non-judgmental manner you get past your own inner censor.
You can always decide later whether it is worth the effort of the second and third draft to get it publication ready, but at least the ideas are out of your head and you've made a start.
I hope this little phrase helps you get past your inner judge.
There are smarter people out there but they might not have your insights into the challenges and rewards of hydroponic banana farming.
Two days ago you might not have known how to perform a particular task, and searching the internet was fruitless. You might not be the first person to have to work out how to do that from first principles -- but you can make sure you might be the last!
Come up with an outline: maybe it's a rant like me talking about Excel ( https://blog.scraperwiki.com/2015/07/eusprig/ ) -- ugh, this sucks because A, and then people do B to get around C, and can't even start to do D, E or F because they're stuck in this way of doing things. Use that to structure what you're writing, flesh out those bare bones.
Some friends and I run a project which could be relevant. It is called Taaalk (http://taaalk.co) and is an online platform for conversations. So if you don't know what to write but have a friend that would happily discuss a subject with you, or know someone you'd like to learn something from by asking them questions then it works well.
We've found that people discover they know a lot of valuable information which they didn't consider valuable until someone started asking them about it. Sounds like this could apply to you. Drop me a line at josh[at]taaalk.co if you want to get involved.
I also majored in literature and philosophy and had to write essays a lot. I got a lot of As.
The first thing to learn is that every group of writers follows different rules.
Think about why you want to publish your writings. Learn that context matters -- that is, your target audience matters. People reading my blog posts don't want the same thing as the people reading my essays at university. My university essays have a different tone and style. To be sure, the essays on my blog are the least popular, because they are very academic. That's okay. I like to write that way sometimes.
Often the things that others find interesting in our writings are things the writer would have never guessed. Because of this, it's all right to swallow your pride and just hit "Publish." Some of it will be horrible, some of it will be great. And there is always the stuff in between.
From a strictly academic perspective, the easiest type of essay to write is a comparative essay. Compare books, ideas, or topics that are similar enough to warrant a comparison; e.g., sexual parallels in Fifty Shades of Grey and Marquis de Sade's literary oeuvre, if you're going for a wide appeal. I just made that up. It's all experimentation.
Another academic "lesson" is when you're stuck writing an essay, it's time to bring in another example.
These are standard techniques that possibly engender a style that is stale and stiff. The more you cater to your reader, the more entertaining it'll be, because you'll speak her or his vernacular.
Having said all that, I have only published my poetry in very small publications. Nobody is interested in my short stories or essays (outside of academia), and I am by no stretch of the imagination a blogger who others read assiduously.
I am read by a very small circle of writer friends.
We have a joke.
We're good at things that don't have much value in modern culture.
It's a big joke.
And we're the punch line.
The most important take away from it was to not to write an essay to defend a position, but to write one so you can express your idea that leads to something interesting which is unknown to your audience, so you can share it!
If the idea you note down is any good today, it'll be a good idea tomorrow too. And a year from now.
If you have enough good starting points, actually spending some time writing out an essay from them becomes easier. Remember you'll probably want to do at least three re-writes if you're hoping the result is going to be any good. Lots of people don't do that -- and it shows. Most half-decent blog posts would've been a lot better if the authors took the time to rework them a bit more. Or, according to Hemmingway: "The first draft of anything is shit.
So with the caveat that I don't actually write much (yet?), the best book I've read on writing is: William Zinsser's "On Writing Well":http://www.amazon.com/Writing-Well-30th-Anniversary-Edition/...
Highly recommended for anyone that have to communicate in writing (ie: everyone).
> I don't have anything to say to people who know less than me, because explaining obvious things seems boring, and I don't know what to say to people on HN/LessWrong, because I feel like they are smarter than me and already know everything I am about to say.
For essays, it can be good to write for yourself. To yourself, or someone much like yourself, but someone who's perhaps not yet encountered one particular idea, one particular technique -- one particular subject.
That usually gives a good framework for avoid "talking down". Write to yourself of one, two or five years ago. There will be many that don't have that last year, years of experience and circumstance that led you down the path to were you are now. Perhaps such a perspective makes it easier for you to share something?
I mostly use Colornote to keep track of ideas, such as app/application/project ideas along with a couple of bulletpoints (eg: Reinvent email: look into alternative client/server sync such as jmap; store email in normalized sql db?; document db?; store attachments based on content hash? (free de-dup); Store email body as same? (Good for multi-user server support for mailinglists ... etc))
Please don't use this name. Its ridiculous that the media use the "gate" suffix to indicate a scandal of some sort, I'd like to think HN reads/commenters can be slightly more intelligent than the average crowd-pleaser journalist.
In any case, you must know that all those practices were very well known by United States regulators, the term "defeat device" for instance appears in regulation since at least 2007: http://www.gpo.gov/fdsys/pkg/FR-2007-02-26/pdf/E7-2667.pdf#p...
86.180910 Prohibition of defeat devices.(a) No new light-duty vehicle, lightdutytruck, medium-duty passengervehicle, or complete heavy-duty vehicleshall be equipped with a defeat device.(b) The Administrator may test orrequire testing on any vehicle at adesignated location, using drivingcycles and conditions that mayreasonably be expected to beencountered in normal operation anduse, for the purposes of investigating apotential defeat device
As you can see it was known that a) defeat devices existed and b) the way to catch them was to try different, random cycles more close to real conditions. The question is, if this was a well known problem and they knew the way to test their existence (and given there were millions of cars on the street with these systems), why start the big scandal precisely now?
By the way, apart from more random, realistic cycles, upcoming European regulation introduces driving tests where the exhaust gases will be collected and compared with the lab test, and only a certain % difference will be permitted.
So, don't fret much. Run a fedora VM using hyper-V client, and deal with it.
In order for an 83(b) election to be effective, the individual must file the election with the IRS prior to the date of the stock purchase or within 30 days after the purchase date. There are no exceptions to this timely filing rule.
Python 3 is IMO a much cleaner and friendlier language to work with than 2. Especially if you're doing anything to do with Unicode, Python 2 can be a real pain. Also, all real development is now taking place on the 3.x series - if you want to keep up, you'd better learn it.
This is a good overview: https://wiki.python.org/moin/Python2orPython3
When I first started learning to program, I thought of every problem in terms of C++ (the first language I learned).
It wasn't until I learned other languages, and really other paradigms (functional vs imperative vs constraint etc), when I really saw that a problem can be framed in so many different ways, entirely based on the language, and some of them are more elegant, more efficient, simpler, or offer some other benefit.
I think if you learn python 2, and really get to grips with it's pitfalls and other nuances, and then learn python 3, you'll get a better understanding into the changes between the two languages, and I think that will give you a better overall understanding. And IMHO, more knowledge is always better.
And even if you have legacy code, I'd learn 3 then learn the difference(s) required to use the legacy code.
Put another way, there is an ever-increasing "tax" being placed on society from those who exploit the masses. Increased production efficiency allows the bourgeoisie to increase this societal tax ever more.
And say you are a good guy, and let me work 3 hours, how would you deal with a competitor who is making 10 times the profit your company is with the same numbers of people and payroll?
As our income has gone up, one of the side effects is that we want bigger homes, more clothes, etc etc etc. If you tried to recreate the lifestyle of, say, 1950s America, with a modest home and home cooked meals (etc), you could probably drastically reduce the number of hours needed to support yourself -- assuming you could find ways to fill your time that didn't involve pissing away the money you do have.
Most people do not have that kind of self discipline. That isn't something policy will create. That isn't something an app will create. There are ways to shape policy to make more small scale, affordable housing available. But, for the most part, making this happen on a large scale and not just for the occasional quirky individual (as it currently happens) would involve somehow radically altering the world's culture.
As much as I think it would be awesome if people in the world generally had more free time hand-in-hand with more financial security, I have significant reservations about the wisdom of attempting to convince people to do what it would take to make this happen. That tends to be in the morality/religion/ethics/culture area and that is very dangerous ground to tread. Historically, it has tended to be the domain of religious figures, many of whom ended up dead at a young age via methods like crucifixion or being burnt at the stake.
Once upon a time I also made some software for a similarly real but niche problem (recording, processing, and building timelapse videos of your work during hackathons). I never promoted it or anything beyond talking about it and using it within the community where the idea was born (in my case, ludumdare when it was still very small). It has actually done pretty well within that context; over the 8 years or so it has been around it has ~50k installs, and it has branched far beyond hackathons -- it made its way onto lifehacker when they still covered real products, there are a handful of completely independent reviews out there, and I get emails from time to time asking for features from a wide range of use cases (everything from documenting cell growth to filming engine rebuilds to tracking video game progress in a modernized arcade).
My only (admittedly weak) advice is to go to the source of how you knew this was a need and share it openly and honestly within a community that is either about that or clearly shares that. From there you'll get some feedback and, if it really does solve a pain point, people will use it and share it. In my story, the flexibility of the product to be useful beyond the initial problem I was trying to solve was also key to its growth - maybe you can do something similar with how your thing works.
I realize that 8 years of being available is the complete opposite of your goal of promoting for only '1-2 days', but I think that amount of participation may not be super compatible with any software these days, particularly for small 'love' projects. How many github projects have you seen that sound nifty but have an empty readme and no commits for 2 years so you wouldn't touch it with a 10 ft pole? I think you'll get much better results by trickling continued time into the product to make sure people know it is alive - respond to posts/questions about it, fix bugs (or at LEAST comment on the issues), etc.
My most recent idea is to offer free services some might want to utilize and linking/advertising on those sites. I don't know if it'll work yet, but I keep trying.
Hopefully this post will generate some new ideas, I'll keep checking back on this to see what people suggest.
Best of luck to you.
If it's a real niche field like you said, they probably won't get swamped by this kind of emails very much and will get curious.
Once you make a few fans, you could ask whether they can spread the word, or, if they're really into it, they'll do it for you on twitter and such.
Also, don't let YC determine the fate of your startup. You are bound to fail or succeed based on your execution skills and hard work, and not whether you get accepted into YC or not. That being said, I wish you all the best! People like you are an inspiration and remind me to always do what you love.
If you're 40 with a high standard of living, and mouths to feed, and a mortgage and car payment etc, then startup life might be rough on you, and outside of your risk profile.
But if you're prepared to live the lifestyle of any other startup founder (at least during the first few months), and assume the same risks as everyone else, then I don't see why age would be a disadvantage at all.
"If you're scared, go to church" - Ice Cube
Not many older than Jack Benny, but you wouldn't have been the only one.
If you want it and you think it makes sense for you, then apply. They are perfectly capable of saying no for themselves.
Cyberwar (ugh, that term) has become white hot after a nuclear reactor meltdown in Russia where every adversary blames each other and America blames Russia for a false flag operation. Packets are now blocked from entering/exiting entire countries unless you have a special permit. Like with radio/tv in Cold War I, everyone begins suspecting spies and government malware in their computers. People increasingly huddle for safety in walled gardens like Facebook, rarely venturing out to unknown sites.
Ethereum still struggles to find any devs who can understand how the fuck their entire platform is supposed to work despite an additional white paper being published.
Microsoft admits no one wants a windows phone and retreats from the mobile market, dooming themselves to simply dominating the dismal "legacy" desktop world only inhabited by developers, people too poor to afford a mobile phone, enterprise customers, and call support centers. Open Sourcing .Net winds up causing large amounts of developers to learn Linux, and they develop a taste for it. C# developers are recognized for their overall brilliance and steadfastness and paid 500K/yr salaries by all employers. (OK, that's a wish, not a prediction)
VR has completely polarized the planet between "pukers" and "players". Thousands die every year from VR-wasting disease brought on by malnutrition and lack of sleep from being fully immersed for weeks on end.
TechCrunch collapses under the weight of it's hideously poor commenters and a management sex scandal.
Self-Driving cars get off to a rocky start, as normal drivers everywhere attempt to run them off the road to "test" their safety.
NoSql replaces Not-NoSql so quickly people begin dropping it from their resume as a skill.
Driverless cars will still not be available for use by consumers, as the flow of edge cases which completely confuse the cars is continuous.
The sharing economy will be governed by protocols.Decentralization will be standard. Companies like Ethereum and OpenBazaar as well as the Bitcoin protocol are already being used/leveraged for this. It will be standard. 1. Decentralized authority will be used for most things and will destroy the power distance between individuals and regulators stripping their power. These protocols provide privacy, authority and identity by design and the govt cant do anything about it.2. Government wont matter muchThis is basically the affect of trrend one. When decentralized protocols become common place there will be no way for government to enforce regulations. Some of this is good and some is bad. On balance it is good. They can still stop people from doing bad things in the physical world, but not govern and collect your communications, interlope into network governance and stop being the worlds sysadmin.Centralized authorities will prosper servicing things like DNS naming authorities, identity, licensing, communications, financial transactions, legal transaction, wills deeds etc.
2. Everyone will realize uber is a logistics company.Uber is building teams to for autopilot and self-driving tech right now.They have a Math Department to create algorithims and heuristics for prediction.They know that ridesharing p2p is something that can only last ~10 years.They will be the first people to do interstate logsitics and transport with self-driving vehicles. They will be the level 3 or cogent to Amazons comcast/verison. By this I mean that Uber will handle 90% of long distance supply chain hubs and Amazon will be the last-mile provider.
WebAssembly becomes popular, js finally has alternatives.
Self driving cars are popular.
Google launches some sort of robotic/AI product.
- Speech recognition has acquired acceptable (par with human) accuracy. This has been a great boon for the digitally excluded. It has also increased the relative prevalence of text based commands in the operating system, not that too many people notice.
- CNC machines that can operate on anything strong now require a license, it was too easy to make guns with them and on balance governments decided that was the important thing.
- VR headsets have failed to gain market share. They were neat, but only if you stayed in one place. Elite Dangerous and co' weren't able to support a physical product of that cost by themselves. There are some fantastic applications of the technology, but you need to find an old headset to play.
- Linux is still waiting for it's year of the desktop and still looks like a poor knock-off of Windows.
- Turing complete systems aren't banned yet, but it looks increasingly likely as phones and tablets start to dominate the marketplace.
2) Microsoft/BSA can fine the company.
3) Civil. It is only criminal if the company was producing pirated materials for profit (e.g. pumping out cracked copies of Windows to sell on eBay). The BSA normally sues companies in civil courts and extracts license fees and fines.
4) You have no personal liability from Microsoft. Between Microsoft and the company it is a contract dispute. However arguably if the company you worked for did get sued and lose a good chunk of change, they could in turn try to sue you, but I've never seen that and it is pretty easy to CYA via documenting the issue for them.
Overall I'd say that as an individual employee you have little to no exposure (other than getting fired). As a contractor "it depends" on what you did and didn't do (since a contractor can be treated like a stand alone entity, and blame can be shifted in part or entirely onto them).
They've given a reason, and this includes a business case for their justification. You're neither responsible nor accountable for their decisions (which you've informed them of).
You have raised your concern.
A bigger question for me, is this a systematic thing in your company? Or just your manager? Or ripping of other things is OK too? If so, at some point there will be negative repercussion, and at that point no order of internal memos will separate you from the brand you worked with.
I don't know how the situation is now (US or UK), but in past years the BSA could show up in the US with warrants and a US Marshal or two in tow to force an audit on their terms.
1) Contribute to (or just read the code of) open source projects in order to improve your coding skills
2) Read up on existing research in topics you're interested in
I understand the desire to be efficient and kill two birds with one stone. However, finding a good, active, community built research project might be a bit difficult. Even if you find it, you may find that opportunities for you to contribute to it are very few.
Contributing to open source projects will give you a good opportunity to understand the open source contributing process (which you'll need to know when you do find that open source project you want to contribute to). It'll also allow you improve you coding skills while you're at it.
Reading research papers gives you much more bang for your buck in terms of developing your research interest, though is not very resume-able. But, who knows, maybe your reading will spark your own open source research project.
Be warned though, there are quite a few research papers, especially those coming out of Academia as opposed to industry, that are cryptic, lacking in detail, or not easily reproducible. And that's intentional. This isn't obvious when you read a paper, it will only become obvious when you actually try to reproduce it. These papers are the result of misaligned goals Academia in, where it's all about publishing as many papers as possible that look good on the surface. When In doubt, I'd recommend focusing on research that has a lot of interest from the industry. That's usually a safer bet.
Gitxiv is an online list combining research papers from arxiv and their implementations in github. So I would say its a great resource for what you are looking for.
Also, they run some kind of competitive implementation runs where you can collaborate with others to implement papers :
I am a JS dev as well interested in Deep Learning. I dont know your specific interest in this domain but I am happy to collaborate with you - if you are interested. You can reach me at raj at dhi dot io. I would suggest you to pick up python or lua. Lua is quite close to JS and Python is extremely easy to pick up as well.
There are several different types of open source projects and I'm not quite sure which kind you're looking for.
Firstly there are a lot of (often hugely popular) tools used by researchers that don't involve research directly. A good example is Jupyter (formerly known as ipython notebooks). Contributing to these projects is sure be of benefit to many people (probably more than anything else you could do), and may be a good place to learn skills because they're more likely to have good codebases written by skilled programmers. But if the project is already too large (like Jupyter), it may be a lot harder to get into.
But this isn't just for him, this is a message to all potential successors saying that if they make the company money, then they'll be taken care of no matter what happens.
The only way to make this sort of thing not worthwhile is to fine them a combination of the revenue made from the vehicles that this was in, and also some sort of punitive amount. Just a small punitive amount will simply be written off.
How much of that was due to breaking the law? How much profit and reputation will be lost due to breaking the law? How much of that would have happened anyway with any other competent CEO?
This wasn't a reward for his contributions. It was most likely in his contract that he gets it no matter what. His golden parachute.
And also why society needs to up the ante.
Not only that, but I'd have to convert it to fiat anyway to pay for 99% of the things I spend my salary on. With the fees involved in the exchange and fluctuations, I'd end up with less money in the end most likely.
Bitcoin is a fun toy, and spending some of my disposable income on it sounds ok. But my whole salary? not on my life. I sincerely hope there is no one around that is so blindly invested in the idea of Bitcoin they are converting their whole salary to Bitcoin.
I enjoy BTC for sending/receiving payments as it is very easy, but I don't see it as a safe 'investment'.
Burned my fingers on freelancing for Bitcoin a couple of times already.
1) Your investors will model $50k as being gone in an eyeblink. In the Valley, that's ~3 engineer-months. Angels will want your round to last about 12~18 months.
2) All entrepreneurs raising their first round are inexperienced in some way, but for better or worse, the combination of not knowing angel investors want rounds to be bigger and not knowing $50k will be gone in an eyeblink shouts Particularly Inexperienced Entrepreneur Here, which counsels against angels believing that your company will be the one out of 10 which > 10Xes their money. Angels absolutely, positively must invest in that company, and it's hard, so they reserve all their shots for companies they think might be that one.
3) You're horrifically mispricing your company relative to market conditions right now [+], which you would think would suggest a savvy investor would think "Hmm deal of the century", but which actually mostly signals "Stay way the heck away" because of the power law of startup returns ("If you make a practice out of getting great deals on good startups, you will lose money; you need to make get good deals on great startups.")
There are more fish in the sea that investors, by the way. If you really and truly need only $50k to make this business a success, one might suggest friends-and-family and/or bootstrapping and/or -- and one hesitates to suggest this but one may have used it before -- credit cards.
[+] If your company is investable, it is worth > $2 million right now. I'm taking the liberty of assuming you aren't valuing the company at that because no one does a round for < 5%.
Your company may or may not actually be investable. If you're curious, you can read on Venture Hacks. Fair warning: what the Valley institutionally considers as investable is, if one takes it as a judgement of one's worth, pretty brutal for most people building tech companies. (It's not -- I've had basically no investable company in my career until maybe the current one -- but many people wrap their self-worth up in what investors would say about their businesses for some reason or another.)
Today, any device with a sim card reader and GSM antenna may be used as a phone: computers, tablets, and so on. I don't know where you live, but, in many country, today, you can buy phone service without a phone, and with no lock-in period.
or if that key is provided somehow,such as pushing a request to provider to get it using internet, then what happened when there is no connection but gsm
or imagine when you use that key for few devices? what will be your main device and you want to suspend the others?
Many problems must be solved if you'd like to use a key instead of a SIM card :D