South Africa has a similar route from Cape Town to Durban, but with more getting robbed at gunpoint. Seattle to San Diego on the 101 works too, substituting cold water for warm and rain for sun.
I found the coastal route between San Fransisco and Los Angeles to be stunning. A road right on the cliff edge by the water. Amazing views. I don't recall name of the route but it shouldn't be too hard to find.
In Europe I would suggest something like traveling in Cornwall in The UK or along the French riviera. Both are well worth a visit. Better in the summer or late spring though.
Also, get a better bicycle for commuting; chains should not break after a few weeks. This shows that the bicycle had been heavily used, or is an ancient rust bucket, and may be a "bicycle shaped object" to begin with.
I carry a Park chain linkpin press tool for opening and closing chain links. Though occasions for using that on the road are rare if the chain is well-maintained and replaced regularly, not long ago I had a fairly new chain derail off the front ring, and by some unfortunate combination of events get itself into a tight kink which jammed and caused a link to bend severely. Having the tool, I was able to splice out and discard the bent link, and be on my merry way. I also carry a short piece of chain that was left over from the original chain installation, because there is only so many links you can throw away before the chain gets too short.
When you get a new chain, the rear gear cluster should be changed at the same time, since they wear together. A new chain can slip on old sprockets even if the old chain didn't. The front rings have to be changed maybe once every three chain changes.
However, when Dutch cyclists do go fast, they wear helmets. In Dutch there are even separate words for everyday cyclist (fietser) and speed cyclists (wielrenner):
I live in Seattle, where we have killer hills and shitty bike infrastructure. I always wear a helmet, and I've had three minor crashes that would have been major crashes without a helmet. When I finally move to the Netherlands, I'm not bringing my helmet with me.
In my own personal anecdotes, I have had one major bicycle wreck where I somersaulted into a car, one bicycle wreck where my chain snapped and I flung myself over the bars onto the street, and a couple of low-speed (~10mph) motorcycle offs where I collided with the ground but my head did not touch. Though there was one motorcycle case where the side of my helmet dragged on the ground slightly from about 5mph; it's arguable whether my head would have hit.
That said, I have hit my head incredibly hard snowboarding, after catching an edge at very low speed ("last run of the day!" type thing), and always always always wear a helmet every single time I ride a bicycle or motorcycle or snowboard, just as I always wear a seatbelt in the car. It's just a habit, and a good one.
Without a helmet, your effective head is "smaller", I know that in an accident of mine - where everyone said "thank god for your helmet" am I certain that the part of the helmet hanging out the back hit the ground, and without the helmet, my head probably wouldn't have touched.
As a long-term bicycist and a long-term motorcyclist (serious crashes in each), I am increasingly skeptical about the technology in current bicycle helmets, especially compared to the technology in my current motorcycle helmets. Bicycle helmets are simply not tested to the same standards. They use very hard shells. They extend the "impact radius" --- basically, your head becomes bigger --- with only some decrease in crash absorbancy.
Reading the literature, it seems that the current bicycle designs are based on voodoo more than good science. The designs look like what bicycle racers used 30 years ago (little leather padded strips).
Compare this to the motorcycle helmet industry. There are plenty of crashes to analyze, mostly of motorcycle racers. There are numerous standards (like SNELL) which measure levels of transient G force within the brain on a simulated head.
We deserve better bicycle helmets, and people are willing to pay for good science and proof of protection. I pay a LOT of money for my motorcycle helmet, and glad to do so. I would pay 4x the price of a current bicycle helmet to buy one with solid, verified science and an international standard behind it.
In my suspicion, the lack of good bicycle helmet science is why the upper level numbers are bad: helmets don't decrease injuries or deaths, except that they cause people not to ride.
Really, we deserve better helmets.
At the hospital they reconstructed my accident and wouldn't you know: I fell on my occiput; elbow shattered as a subsequent side effect. Since I had had the helmet on I hadn't even noticed; without the helmet, well, I wouldn't have noticed either. I went back and looked at the helmet and the foam was damaged at the back of the head (it had absorbed a bunch of K.E.) and the back of th helmet had grit embedded.
Needless to say I ALWAYS wear my helmet.
On a side note, the situation in which the accident happened could have happened likewise in the Netherlands, it was on the flat and I was on a driver lane, except maybe that it was driver negligance that could have been avoided if drivers where more accustomed to bicyclists.
if you have a 0 dollar brain, wear 0 dollar head protection.
Dr Ian Walker did some experiments with a bike fitted with an ultrasound distance meter and found cars kept a greater distance to people with long hair.
Alternatively, fit your bike with a flame thrower - https://www.eta.co.uk/2010/09/29/bond-bicycle-boasts-ejector...
- making people wear helmets will make less people bike, less people biking on the road leads to more accidents with bikes, and more deaths 
- a helmet may make people in general more reckless 
- cars will pass closer to people when they are wearing a helmet than when they are unprotected 
- if people need helmets, cycling is apparent a dangerous activity, attracting risk-seekers, skewing the statistics 
- compulsory helmet use in Australia seems to support some of these (perhaps) counter-intuitive arguments 
- helmet itself is dubious 
Morale: sure, wear a helmet, but don't evangelize its use. It's a tragedy of the commons if you will succeed.
 http://hanlonblog.dailymail.co.uk/2011/07/should-my-son-wear... http://www.tbd.com/blogs/tbd-on-foot/2011/08/idea-of-the-day...
My helmet hit the ground hard, I was perfectly fine.
The ambulance guys were pretty sure I would not have been if not for the helmet.
Please, wear a helmet.
I'm a severe traumatic brain injury survivor. I was wearing a helmet (skiing crash) but lived with the effects for two years. It was incredibly frustrating -- I was surrounded by loving friends and family that cared enough to give me some painful feedback.
I'm still skiing and researched helmets in depth before returning. There's some interesting technology called MIPS. The protect against moving impacts, a large improvement. Current helmets are just dropped straight down and these helmets are tested while spinning/moving/etc. That's how crashes happen -- while you're moving, whether it be on skis or on a bike.
It's a little more expensive, but it's your brain. Please protect that.
Isn't anyone's personal account of risk and danger pretty much irrelevant?
Many on my cycle run have been attaching go-pro mounts to their skull cover; I wonder how ineffective it renders the helmet if you landed straight on it.
I got my handlebars hooked on a rail going downhill and flew over the handlebars; my training allowed me to take the whole impact with my hip and butt. Light graze on the forehead, I'm lucky my reflexes told me to tuck in the head. (However, I couldn't walk that day. Cycling was fine.)
I'm wearing a helmet now, but I'm not sure the situation would have ended as well if I had been wearing it then, because of the bigger head radius.
A person in the thread (so value accordingly) said they worked in an ER and their estimation of the result of the impact, were there no helmet involved, was "likely death."
Also, as kazinator said, helmets are only good for one crash (or even drop from very high off the ground). Get a new one!
There was nothing I could do to prevent the impact, as I've trained myself to pull my money makers under me in a fall and let my body take the hit (the broken finger got wrapped up in the brake lever on the way down). There was something preventative that I could do in case of an impact, and boy am I glad I did: wear a helmet.
My wife works in healthcare and has worked in settings looking after patients with acquired brain injuries and she always tells anyone (even if she barely knows you) to wear a helmet. She's met too many young people turned into living vegetables or something similar to idly stand by and watch people take that risk.
If I had been wearing a helmet the cushion around my head would have lifted most of my face off the ground. Probably would have ended up with nothing but a chin scrape.
Your head is arguably the most important part of your body. I'd like for it to be socially acceptable to wear a helmet at all times.
Good if you know the routes you generally try to ride with other cyclists, safety in numbers. Plus the wide green lanes help make it abundantly clear to cars that this is a bike lane.
Bad the other streets turn into crazy biking gambles. Every once and while I see someone riding on Guerrero and want to yell at them to go one street over (Valencia) and reduce your collision chances. It emboldens bicyclists to not follow the law quite as well, or maybe since the sample size is high, I don't know.
In Minneapolis? Yeah, it's not in season right now, but bookmark http://oneononebike.com - not affiliated, but I've recommended plenty of people over to Gene and they've always thanked me.
I managed to go over my handlebars while riding down a quiet side street (with no hands, like a badass :/ ), when a gust of wind blew me sideways and caused me to overcorrect and crash.
The Lord protected me on that one and gave me a chance to be a bit more proactive :)
The following day, one side of my body was covered in contusions, and I had a severe phone-shaped hematoma on my thigh.
I have every reason to believe that wearing a helmet prevented a serious brain injury. Also, Otterbox makes a pretty good product.
Also, check regularly the tightness of your wheel spokes, and replace a wobbly wheel if you can.
Headlights aren't a bad idea either.
"While they do protect your head during accidents, there's some evidence that helmets make it more likely you'll get in an accident in the first place."
Now buy a new helmet and go get your head checked (literally, a helmet will protect against a skull fracture but not a concussion or other brain injuries)
So yeah, don't play around... just wear the damn helmet. That's my advice anyway.
2 * allegedly stupidity and dumbing down of the USA3 increases and the 'i wear a helment' is an example.
4 * At age 58.34 years, I still ride a bicycle. I have5 survied various adventures, including learning to6 ride as a child in New York City, NYC, USA.
7 *the WISDOM OF AGES to SAVE YOUR BRAIN
8 1.) fastest way to lose your career, and live in9 the 'nursing home prison' for a life sentence is10 'bicycle cycling cyclist.'
11 2.) Do I have the best equipment like helmet?
12 3.) Do I assume that the 'impaired driver' or13 old driver with OLD EYES does not see me?14 Do I assume that I am running Microsoft Windows15 XP and I have alreaady been 'cracked'??
16 4.) Do I practice FALLING OFF MY BICYCLE in a17 controlled procedure? Do I know how to tumble18 and roll?
19 5.) Like driving a car, where is the escape route?20 Like soft grass and NOT lighting poles?
21 6.) Do I practice tumbling on 'hard ground'/22 DO THIS PRACTICE to strengthen your neck muscles!23 Push on your head with your hands, while rolling24 and rotating your head.23 Push on your head with your hands, while rolling24 and rotating your head.
25 7.) Why does this work? The reason GRANDMA dies26 SLOWLY is hip fracture from falling down.27 That's the reason why TAI CHI WITH WEIGHTS works.28 It 'strengthens the BALANCE FUNCTIONS.'
29 8.) WEAR ALL PROTECTIVE GEAR. Ater a few falls,30 and YES I AM STILL ABLE TO WALK AND HAVE ALL31 MY FINGERS, wear the 'dollar store cotton gloves'32 and the knee covers and yes SAFETY GLASSES.
33 9.) Most sunglasses shatter. Blind for the rest34 of your life and then you go to the 'nursing home.'35 Even MURDER in the USA has an average sentence of36 less than seven years.
37 10.) 1.) fastest way to lose your career case:38 THE CENTRAL PARK JOGGER with TBI traumatic brain39 injury. When you LOSE YOUR short term memory,40 your career, especially if you are a programmer41 or white collar work IS FINISHED due to TBI.
42 11.) A truck tractor trailor jack-knifes and43 skids. The car crash and 'multi-car pilup'44 cuts off your legs. What a pity!45 Seeing in the old age homes in Florida, FL,46 USA, this is not a problem.
47 12.) Think of it this way. Would you rather have48 dementia - Alzheimers or 'wheelchair no legs49 disease.' For me the choice is 'wheelchair.'50 http://theinvisiblegorilla.com/blog/2010/06/22/51 unexpected-bicycles-and-inattentional-blindness/52 "unexpected-bicycles-and-inattentional-blindness"
53 14.) YOU ARE INVISIBLE for this is the USA -54 United States of Attention Deficit and55 USA - United States of Amnesia.56 Europe and even Asia - cyclists are treated57 with respect. In the USA, expect loose dogs,58 even wasp nests operating out of abandoned59 houses, sand and slipperty stuff on the roads60 and drivers who don't care and can't see well.
61 15.) the most dangerous times are are dawn62 and dusk. Simply test your OLD FRIENDS with63 OLD EYES who have a driver's license.
64 16.) How do we know this is true? The65 rate of motorcycle accidents in Florida66 and Arizona is very high. The old driver67 or teenager texting says in the court:68 " HE CAME OUT OF NOWHERE; NEVER SAW HIM."
PPPS. There is little penalty in the USA for 'manlaughter.'or Traumatic Brain Injury. Let's take an alleged legal casein FL or AZ, USA, shall we??
the worst penalty for BAD DRIVERSthat might happen is two (2) years in jail.Florida, FL, USA protects the house. Civil courts cannot usuallyget the 'pension/annuity.'The worse that can happen to the GARBAGE TRUCK DRIVERis he gets fired and usually the company will try to protect him.LIKE THE BIG BANKSTERS, company fines are a 'small inconvience.'
PPS. Some of the garbage truck drivers may be hearing impaired,SO THEY DO NOT HEAR YOUR WARNING BICYCLE HORN.
Have you ever seen 'rear view mirros' on GARBAGE TRUCKS andother commercial vehicles THAT HAVE NO BLKND SPOTS??
plenty BLIND SPOTS.
Or you know, don't, because you've got perfectly safe bicycle infrastructure and you're never going faster than 20 km/h anyway.
What works for you is not a universal law.
You know how this bicycle helmet issue always turns into a shouting match on the internet? I think it's to a large extent because people don't have the empathy to see themselves in the situation of a bicyclist on the other side of the world, in a different automotive culture, with different laws and history.
It seems to only be available in San Francisco right now, though.
A good plan to avoid wasting your time is to give them a ballpark figure up front for what it will cost to make this happen. That figure should not be less than six figures if it involves any significant effort on your part.
If you've already packaged everything up, and it really is as simple as delivering a VM image, you might only quote them 20X - 100X the retail price of your most expensive subscription plan. Naturally, this will be an annual contract, with the first year paid in advance and a fair amount of lead time.
Keep in mind that your email outlining this will typically be the last contact between you and the customer, since they're often simply middle manager types with an expectation that the price will be the same as your "Big Customer" subscription level, except that it will somehow magically run behind their firewall. Your mail will simultaneously give them a heart attack and correct their understanding of Enterprise licensing. If they do engage after that, you can start your Enterprise Sales cycle.
Expect to spend three or four times longer than you think you should dealing with their IT department.
Make sure you charge a healthy amount for all this because it will take more resources than you think on your side.
A week or two after signing the contract, they said they couldn't get the hardware after all and could we go hosted instead. I look back at that moment, and thank my lucky stars. Now 2 1/2 years later we would never offer on-site as an option.
Be sure of what you're getting in to. Will they allow automated deployments with updates to your appliance (as that's essentially what it is). Will you need permission to access it? How will you support users accessing it? Often those same 'security' reasons apply. And then you'll find yourself stuck in the old model of yearly release cycles, supporting old versions and all kinds of pain.
Think long and hard and be 150% sure it is worth it.
They might be understanding if you told them there would not be updates or new features aside from critical security patches. When they're desperate for new features 10 years from now, dispatch a team of on-site consultants to help them upgrade.
Do they consider having it hosted on a private cloud environment? So you guys still control the systems while they can access it securely (i.e. VPN tunnel between their premises and your cloud servers).
The difference with your current offering is that this "instance" of your APP won't be shared with anyone else and you can land a nice maintenance contract, plus keep everything under your control.
Otherwise: where are your prospective customers presently in their purchasing cycle? The channel you use depends on where they are.
Also, smack your employers and tell them that there is latency involved in doing e.g. creative development and negotiating private placements (which are, n.b., one thing you really want to be doing), and that two weeks before the planned sale is way the heck too late to use many appropriate techniques. There is a reason why traditional retailers start going into war footing for Christmas in early summer.
1. Advertise on Google (adwords)
2. Advertise on Bing (which is the same thing as advertising on Yahoo at this point)
3. Advertise on Facebook
4. Advertise on Twitter
5. Open an affiliate program (CJ, Shareasale, etc)
While that's happening: Run split tests and optimize every part of your conversion funnel. Up those conversion rates, lower those bounce rates and abandoned shopping cart rates. Every little bit helps.
"Chronicles of Amber" by Roger Zelazny - for imagination and badassery
Favorite short story is "Understand" by Ted Chiang - mind-expanding ;)
Also in general the lesser known Heinlein books are amazing. Not a fan of Stranger in a Strange Land. Named my current company after a reference to The Moon is a Harsh Mistress.
"Diaspora" by Greg Egan has a great story, huge ideas, and probably the most cogent explanation of sentience/sapience ever written.
"The Diamond Age, or A Young Lady's Illustrated Primer" and "Accelerando" have already been mentioned.
"Reteif!" Made me laugh out loud. Larry Niven's "Destiny's Road" points out the difficulty of interstellar colonization. "Ringworld" blew my mind. Gene Wolfe's "The Book of the New Syn" taught me to pay attention; "Dirk Gently's Holistic Detective Agency" by Douglas Adams reinforced the lesson.
There are a lot of good ones; I could go on for ages...
It's easy to categorise these as wonderful and well written space opera, but that undersells them. Their author (Venor Vinge) invented the idea of the Singularity, and worked as a computer science professor. Both won both the Hugo Award.
As good as people say it is.
Most of Richard Morgan's works (esp the https://en.wikipedia.org/wiki/Takeshi_Kovacs series). Not his fantasy books though.
For fantasy books, Patrick Rothfuss is doing good stuff. The Kingkiller Chronicles is excellent. Read his other books before "Slow Regard of Silent Things", though, because that is one weird story.
From more recent SciFi books:
https://en.wikipedia.org/wiki/The_Windup_Girl is excellent.
I'm currently reading Ancillary Justice and I'm really enjoying it. https://en.wikipedia.org/wiki/Ancillary_Justice
This is seriously impressive considering that it was published in 1998. My current hypothesis is that he's a time traveller messing with us.
It's one of those books that just takes a while to digest after you are done reading it. I highly recommend it.
Accelerando (Charlie Stross) - truly epic, hard-scifi, from near to far future, truly hardcore
Diamond Age (Neal Stephenson) - awesome tale, plenty of nanotech, almost fairy-tale-esque
I still love Gibson, even his later books.
I want to say one of my favourite books is "Salt" by Adam Roberts. I love the characters and description of political views and the way the war between factions plays out. Roberts' other books are pretty good too.
I loved REAMDE - I could have done with a bit more inside the game and a bit less tramping through the woods. I love Stephenson's other books too.
Finally: Bruce Sterling seems to be under-appreciated. Hard to recommend one of his books.
This question is perhaps a FAQ. Has anyone on HN ever scraped the answers posted to the various threads, added information about number of mentions or votes; with links to Amazon (and other book sellers)?
Having some carefully chosen adds and duplicating all the links with affiliate links would turn this into a mostly passive income project.
The Left Hand of God Trilogy The Bad Company seriesIain M Banks Sci-FiPhilip Jose Farmer Riverworld
Every time I read a novel written by Dukaj I start feeling smarter. The ideas presented by characters are always worth considering and eye-opening.
Today, it's a bit less clear, but here is what comes to mind.
Rendezvous with Rama - Arthur C. Clarke
Worthing Saga - Orson Scott Card
EDIT: Come to think of it, I don't know is in the right category as Sci/fi. Well if not cryptonomicon, then SnowCrash probably :-P
Neuromancer - William Gibson
Nineteen Eighty-Four - George Orwell
Perdido Street Station - China Mieville
Snow Crash - Neal Stephenson
Ender's Game - Orson Scott Card
Foundation series - Asimov
You could also work to simplify/automate the on-boarding, spend some of your monthly revenue on creating some videos that cover the features/questions people seem to ask the most about. You can make a few videos, 45 seconds or less, and have those on the site for users to view without registering. Then record a full demo that is say 5-10 minutes and if someone registers for more information then send them a link to that video and then follow up with them. You may help shorten your need to be involved in every sale, and decrease on-boarding time. This doesn't mean you can necessarily make a sale without jumping on the phone, but it does mean you may be able to minimize those conversations more and therefore make them more scalable and even possibly easier for you to train others to help you close deals.
In the end, raising money takes way more time and effort than you initially think, and even with friendly investors it can change your ability to go the direction you want. Lastly, remember a lot of investors try and minimize founder salaries, and if you need 10-14k a month to survive then you may struggle to find an investor that will commit when 85% of his investment is just paying for you. If you are thinking you just need 50k to make it for 3-5 months, you might be able to get that more through friends/family/bank to help bridge the gap until you get more signups.
You're making enough you could hire an assistant to handle some of the support, inquiries, billing/accounting so you can focus on demo's and growing . . . support would probably be the first thing to outsource . . . setup a google doc outlining typical questions/responses . . . so it's pretty straight forward and have them send something more complex on to you to handle . . .
That will free up some time for demos, etc.
You might get a bump from conversion optimization, reducing churn, etc . . .
Could you go to 4 days per week at your day job . . .
Start doing one demo call over lunch a few times per week . . .
I think there are lots of less expensive ways to gain more time/revenue vs. losing equity.
Good luck scaling your SaaS.
That suggests to me that either a) you're not going to be able to raise in the end, which is bad because you're wasting time, or b) you are going to be able to raise but only from unsophisticated investors with unrealistic expectations, which is a hell of a lot worse.
It would be a real shame to give up a lot of control and attach yourself permanently to unsophisticated investors with unrealistic expectations - just so you can quit your job a few months sooner.
If I were you, and if I really thought my business' potential was $10MM in revenue in 7-10 years, I'd gut it out and do what I needed to in order to continue to bootstrap until I could safely quit. You've got the potential for a great personal outcome - if you can just keep it personal.
I have a nice consultancy that developed many unique software products. Over the years I have not been able to maintain them. If I had taken outside money I could have taken those tools to market and probably grown beyond my current stagnation point.
Happy to introduce you.
PS. I'm totally intrigued now to find out what your WP app is!
>Great, Ive built a bunch of systems Now What?
>You have one job left: Fire yourself.
>Thats right. Once youve built the process and have tested it to be sure a) its doing what its supposed to and b) has a feedback loop that lets you monitor its progress, you need to fire yourself from executing that process. Outsource it, hire someone part-time, hire an employee, use a virtual assistant, automate it with code, etc. Whatever the case may be.
>If a process youve developed is functioning properly, then as the business owner, you probably shouldnt be doing it.
>Your job is not to build products. Your job is to build systems.
>Thats how profitable companies are built.
Wow this described my situation exactly.
Same revenue, same costs, same lifestage (2 kids, mtg), same high paying job, etc.
I've found some ways to make the process even more self-serve than it already is, maybe we can compare notes?
Could you hire an employee, part-time, using the revenue you are currently bringing in?
From a community perspective, we do want all devs to be able to get involved in the site, so it's not ideal if the solution set is actually so comprehensive that it raises the bar for getting involved.
But I'm not too worried. SO still gets over ten thousand questions per day, which gives devs who want to contribute to the programming community a ton of opportunities to share answers and help. Plus, and new languages like swift leave a lot of blue ocean for asking new questions.
Don't get me wrong, our two biggest product priorities are focused on how we can make it easier for new users to get involved, and how we can ensure that more active users continue to feel appreciated and find it rewarding to share their knowledge on SO, where so many others can benefit from it. There's plenty more we can do on both fronts, but I'm not too worried that we're running out of ways for devs to contribute if they want to.
Disclosure: I work at Stack Exchange. I love Stack Exchange. I am not an unbiased observer of Stack Exchange. My mom says I and my company are special, and I believe her.
The other problem is when questions are sort of the same but not quite.
Best of luck to you.
Just a future suggestion for you in the future. If your employer doesn't pay on time even if it is the first time it is time to leave (from personal experience). The longer you stay the higher the wage and time losses will become.
An employer should always have money set aside for payroll, payroll taxes and pay the employees first. If this is not possible it should be a hint to the employees that the business is failing and will eventually start bankruptcy proceedings or closing up shop.
If your boss does not let you go before they are in this state as they know in well in advance before this ever occurs, it is an even worse sign that their pride and emotions are now running the business.
I would just walk away.
Unfortunately, if you are in China, while I'm sure there are some laws that protect you, you aren't subject to all of the American labor laws unless you were qualified for work in America. Texas has strong labor laws that protect this sort of event - including subsidized representation. It is possible that they may still represent you, depending on the situation, and if the company failed to pay wages beyond just simply yourself. If nothing more, they can point you in a helpful direction I should hope.
They are specifically around Texas workers of course, however it is also their job to police Texas companies. Ultimately, if indeed you have a US citizen in your work force, you may have a greater leg to stand on.
As others have said, your single greatest asset is representation by a lawyer. If at all possible, I suggest having one of your US counterparts start with the Texas Workforce Commission as I stated before. Have all of the documentation ready, including the contract, emails, and so on.
Lastly, it's too time consuming sometimes when I need to login to a critical service in a PC in a public place. I need to install LastPass (and hope I can install it), then login. if I remembered my password I could just login without LastPass. Those precious few mins are critical if I need to login to my host provider if my site goes down for example.
A really simple example would be:
cabbage123!face <- Facebookcabbage123!goog <- Googlecabbage123!twit <- Twitter
I only have two things to remember - the root part of the password and the way to generate the last part. Obviously, just using the first four characters isn't the best idea, but you can change that part to whatever you want to - it's kind of your own secret key.
1) Seamless sync between my devices. I want to be able to access my accounts on any laptop or mobile device. I use a BlackBerry, so good luck with that! (I can sideload the Android app, if that helps. :P)
2) Automatic encrypted backups. Sure, I can throw the database into Dropbox or something, heck I can set it up to sync back to my tarsnap account. But if you do this for me, I'll pay you.
3) Shared accounts. This is useful in two scenarios:
a) Accounts & passwords for use within teams/companies/etc.
b) Sharing accounts with my wife.
Right now, she doesn't have full access to my financial accounts. I really want to change that. Make it easy for me to do that.
4) Dead Man's Switch. IMO, the value of a centralized password manager is this last feature. Heaven forbid that I'm no longer around, I'd like my family to have access to my complete online & offline life to take care of things as needed.
Fear that the tool (or database) will become corrupted and lose all of the passwords that are stored in it.
i) I want it to sync across all my devices but
ii) I don't trust cloud providers. I especially do not trust the cryptography people use.
Also, I am poor / mean and I the price I am prepared to pay is below what people are prepared to charge.
2. No guarantees that it won't be vulnerable at some point.
Camayak provides assignment creation with submission and publishing deadlines, and tracks the assignment through your custom editorial workflow.
We provide an editorial calendar which shows assignments by their deadlines, current status, etc.
There are pitches, comments, activity feeds, various notification streams, multiple content desks per account, customizable workflows, and a ton of other features.
Camayak can publish directly to WordPress, and any other delivery CMS or service through our content API. We support multiple delivery platforms per account and a single assignment can publish to multiple platforms at the same time.
Feel free to shoot me an email at email@example.com if you have any questions!
Outside of that, you could try Basecamp to manage your projects and use the To-Do list as a reminder system to send your team the reminder to do the blog post etc, and then they can mark the task complete in Basecamp once it is done.
Just some ideas as I am not sure of any specific software built for your need.
If you arent truly a marketing agency, then it may be better to augment your existing project management solution (like basecamp) to track this with calendars/projects for each customer with recurring tasks. This will provide great visibility and alerting.
- Talk to a family member who is employed in a business.
- Find out a task they do that is repetitive, inefficient, automatable, and enhanceable. Spoiler alert: there will be a lot of these.
- Automate/improve/streamline said task.
- Get noticed by said family member's boss.
- Arrange to do more of same in exchange for 1099 compensation.
- Lather, rinse, repeat.
- Get referrals from said boss to other companies in same industry. To them, you are not an employee's family member, you are an experienced industry consultant. Raise your rates.
My article about freelancing:
As another commenter suggested, codementor.io is a good place to go. gun.io is my favorite. There's a ton of interesting projects on there.
(My background: I started doing Java Swing before college; wrote a bunch of PHP in college; got my first job working on Java webapps with servlets and JSF; founded a startup that successively ended up using web.py, Pylons, and Django; got into Google where I ended up writing webapps in C++; participated in the rewrite of that C++ server in Java, and am now using straight Django for my second startup. The technology world really does move in cycles. Use whatever you're most familiar with, learn it well, milk all you can out of it, and then move on only when you have to. You can save yourself years of effort by avoiding the latest fad and "grass is greener" syndrome.)
Right now I think you should concentrate on Node.js - finish your degree, maybe join some exciting startup or start something yourself. Keep looking at python from time to time. Maybe do some hackathons or tiny projects by yourself.
Node.js is certainly fast moving train. But where would it end up in? I don't really keep my hand on the pulse of the node.js community, but I'm not sure node.js is here to stay in the long run. Node.js will be used for various things for a long time. It has amazing websockets implementation, asyc execution does have some great benefits, but the code. My god is it messy. As mundanevoice points out below - you have to be a very solid and experienced developer to keep it all sane.
About python. I think it'll be around for a while. It is solid, it is readable, it is fast. Python community is large, there's a lot of very high quality tools written for it. It may not be so hip as node, but there's a lot of jobs for python devs out there.
All said, I myself is still torn about this question, though. I know both languages, but I've used node.js in more exciting projects than python. Python is so beautiful, but node.js stuff is interesting. So I'm still on the crossroads - which way I want to go all the way. And should I?
Python is a solid choice in the long run - it'll be around. Node.js? Most likely too, but for what purpose and how many companies would go with it?
Node.js is all cool to experiment with and build some projects but it gets incredibly tough when you want to write something complex. I am not saying that it is impossible to build something complex, but it would take a very experienced developer to do all of that in acceptable time.
Python/Django on other hand has a very mature ecosystem and the development is really fast as compared to Node.js which also has a fast start but you get stuck when you need to build something complex. There are many quality plugins for Python/Django which in IMHO much better in quality than npm packages.
Python on other hand is a better language than JS and you won't need to fight the language to write better code (The point is it is very easy to shoot yourself on foot while using JS).
If I were you at this stage of your career, I would suggest to start doing Python/Django and maybe learn some good Golang/C++.
Node may turn out to be a fad, so don't hitch your wagon to it fully. To be a good (web) developer you are often going to need to learn new languages and frameworks as the tech landscape changes.
At this point in your career I'd suggest polishing your Node / JS skillz and make yourself valuable to a potential employer. Being so-so with Python (or any other language) is not likely to increase your value in the marketplace.
If I were in your situation, I'd sooner look at Go or Rust than Python, but only once you are earning good money.
You need to learn multiple languages/platforms, and learn to use the best tool for the problem.
Both are possible in Python, while leveraging a MUCH better language.
If so, wouldn't time be better invested in improving that?
Since the bulk of the web runs apache, that'd be the best way to improve the speed of the web, no?
This the reason you see:
The real question is whether or not they should open-source it... and I'd lean in the "yes" direction, but I'm biased.
Of course that means this is a regular popularity fest, complete with sock puppets, politics and the rest.
I have put two libraries on "pub", the dependency manager for Dart. An implementation of the Levenshtein distance  and a tool to build lexers .
What I've found is that I like it more for back end stuff than front end stuff. It is very easy to refactor, and once you've got something rather stable, type annotations give you great feedback.
Another thing that bothers me with Dart is that "pub" is bound to your Google account. I had pushed the two projects mentioned above with an account I don't have access to anymore. And since I am not able to recover that account, and "pub" does not allow password recovery, I have no way to update things. This can be seen as a security feature or as a blocker. But the truth is, right now, I have lost access to these projects. With a more open system like NPM , I can at least get a new password sent to my email address (which uses TLS when possible and is secured by a veerryyy long password, so I don't think it's less secure than "pub").
One nice thing that Dart used to be criticized about is that is actually a standard .
In the meantime:
+ Check out as many conventions or conferences as you can, but focus on the "hallway track" and the bar (you don't have to drink, either!).
+ Check out Meetup.com or even OkCupid.com (or the EU equivalents). Other people are trying to make new friends through those sites.
+ Chat with the folks where you work. Spend time in a coffee shop or co-working space if you don't already. I made a good friend, for example, out of a totally random Starbucks encounter.
Hope that helps!
- local groups for your preferred hobby (there are lots of tabletop gaming events, I met some cool people in Europe that way)
- taking classes is a way I've met lots of people. Even if it's short courses
- going to events
- sports and other hobbies - as some mentioned, biking, trekking, climbing, running. In southern Europe there has to be some kind of sports app.
Other family members use other kinds of social support:
- couchsurfing (there are local couchsurfing events almost everywhere)
- churches / NGOs / charities / volunteer work
I was gonna suggest meetup.com but looks like you do not have interesting meetups in your area.
Maybe pickup some sport in your free time. Leisure, fitness and socializing all rolled into one.
The only advice I have is: Take haircuts and dancing lessons as often as you can.
Hit the bar, have a few drinks, talk to other people at the bar.
http://nodetuts.com/ video tutorials)
When you are done, look at this list of extensive node at Stackoverflow:
Great tutorial to get up and running with a web framework (Express), database (MongoDB), and simple, functional app:http://cwbuecheler.com/web/tutorials/2013/node-express-mongo...
I realize the title suggests free resources, but I've also found the $9.99 book Hands on Node.js to be very helpful.
What general role does she need from her partner?
Maybe, for a taste of it: Paypal ships API documentation as X00 page PDF files. Their Payflow Pro product, being relatively simple, requires only 176 pages.
Or, in terms of design decisions, consider all the fun of writing software which implements a case statement that maps error code 100 to "Invalid transaction returned from host (Processor), in the case where the processor is Global Payments East or Central." to, well, whatever the heck you're supposed to do when that happens.
Yes, a merchant account. "Start accepting credit cards using your existing merchant account."
PayFlow is just a gateway. A gateway cannot process credit cards without being attached to a merchant account; it is just an API to bridge the web with the processing network of the merchant account provider. You can't use it to charge credit cards for $25 and $0.10 per transaction, you pay that _on top of_ the processing fees charged by the merchant account provider.
PayFlow was previously a Verisign product that PayPal acquired in 2006.
That isn't to say you can't save money over Stripe with PayPal. PayPal Payments Pro is their integrated gateway and processing solution, and discounts below Stripe's rates start at $3,000 per month of volume instead of $80,000 per month.
It's been a while, but I've set up a few Payflow-based systems, and it's been a great way to go... Payflow allows you much more control and detailed logging than, say Stripe. Yes, it's a bit of a pain to get it all set up at first, and there are a few tricks with error handling, but it's a good way to go to implement your own payment system.
Second, ease of use reputation. Paypal is not known to be easy to integrate with and use.
Third, reputation in general. Paypal has a history and reputation (whether deserved or not) of freezing your accounts and leaving you in the worst situation etc.
If you want working with SQL to become extremely easy to you, you will need to start creating websites, bring traffic to those sites and implement the scaling procedures you have learned from the books below.
As if you go to a job interview and want to blow it out of the water it is to your best advantage to know for example MySQL in and out so well you make the interviewer smile inside and go yes we have found the one. You will probably see a little smirk as the interviewer is trying to hold in their smile when this happens but you will know when this occurs very easily. Upside to this is you will be very comfortable getting started on day one and the only training you will need is the current architecture and backup or non existent backup plans in place so you can get to work.
I recommend the following hardcopy books in order:
If your wanting to do Microsoft SQL Server, I recommend the following:http://www.amazon.com/Microsoft-Server-2012-Step-Developer/d...
Install MySQL on your machine to play with. If you have access to a Wordpress install that has some data in it, take a backup of that and restore it to your machine and learn how to write queries for it. The way to figure out what to query is ask yourself questions, like, how many blog posts were posted in the past year. What was the count of blog posts per month for the past year. Stuff like that. And anything that you could see someone asking you to answer. BTW -- I am not suggesting that Wordpress is an amazing database design, but it is fairly typical of what people do so its a reasonable place to learn.
Then once you feel pretty comfortable there, take a couple of the public datasets you can find online, Amazon shares a bunch of them and you can find others. Then create a database, import the data and write queries against it, following the same process of asking questions that seem interesting. You can even take the max-mind CSV file they provide and create a database out of that to learn how to query it and get answers. It is a small and simple dataset but there are a number of things you can figure out using it.
While I personally prefer postgres, I think MySQL is probably a good place to learn as there are a ton of tutorials and resources for it. After you master the concepts then you can switch between platforms much easier, MS SQL, MySQL etc. The basics are the same between them all, even though each has their own quirks and gotcha's, knowing how to work in one you can always ask Google how to do X in Y if you already know how to do X.
That'll give you some understanding of the richness that's available to you when you start to use SQL. Until you get why SQL is amazing, SQL will feel like a chore.
Once you feel comfortable with custom reports, you should learn about performing queries on queries (via subqueries, CTEs or views ... all very similiar) and queries between tables (JOINs).
Once you have JOINs and subqueries down, you'll be able to do things that are both blazing fast (compared to similiar operations in your application) and extremely memory efficient.
To my point: make sure you learn how to do complex SQL queries including subqueries and correlated subqueries. Also, learn to create stored procedures and triggers in your favorite database.
You might look into the book "Refactoring Databases" by Ambler and Sadalage. It challenges you to think about the database as an evolving system, which is different than the kind of textbook exercises where you just sketch or build it once and then move on to the next problem.
Rosen believed that the contemporary model of physics - which he thought to be based on an outdated Cartesian and Newtonian world of mechanisms - was inadequate to explain or describe the behavior of biological systems; that is, one could not properly answer the fundamental question "What is life?"
"Mainstream biology" isn't particularly interested in the "What is life?" question (ADDED: rather, it's an interesting philosophical question brought up when viruses are seriously taught), and is quite productive with its current reductionist approaches. That would include, for example, MIT's Biology department, infamous, as of the '80s at least, for not looking much above the level of the cell.
I'd look at two things: there's a semi-joke item or two about how mainstream biologists would never understand a radio based on their methods, and look at the ones trying to understand the brain, or why MIT created a Brain and Cognitive Sciences department (http://bcs.mit.edu/aboutbcs/history.html) or some of the reasons why e.g. Jerry Lettvin was in the EECS department instead of biology (https://en.wikipedia.org/wiki/Jerome_Lettvin).
I personally believe in show and don't tell. So if I am interviewing with someone or vice versa I would rather appreciate that I get to see some code that an individual has written or have someone assess me on that rather than how I well I can articulate myself or conjure up jargons and buzz words.
I am comfortable taking on large problems as long as there is flexibility in time. I spend about 15 hours over three days solving a problem that intrigued me when I interviewed 5 years back. I learned a lot about company, programming and myself int those three days.
Years later as I am trying to make that experience smoother for others, I have done a 5 series blog on what we look into coding solutions. Hopefully, that solidified them a little bit and doesn't make them look like "vague" and "just a whim and fancy" coding round.
Find my detailed take on coding problems given out by Thoughtworks recruiting here.
I've been asked to write constraint solvers for hexagonal Graeco-Latin squares which I did complete. It took me days, I got an optimal solution and was the only candidate able to do so. Still didn't get the job.
My current strategy is to only agree to solve puzzles if the recruiter can tell me how many of my potential coworkers solved what puzzles when they were hired. If it turns out most of them solved very challenging ai or dynamic programming problems, then I could jump through almost any hoops to get the job. Because working with people smarter then you is just invaluable.
If they aren't able to divulge such information, or most of the employees didn't solve any puzzles at all, I would be weary.
So here's the question: is the code being asked to be production-ready, or otherwise real-world useful?
Because one possible thing that's happening is that they're mechanical-turking their codebase by doling out assignments to hopeful applicants.
Calibrating tests like this is pretty difficult though, anecdotally. We give out a work sample test that we think should take 2-3 hours maximum and try to frame it that way in the problem description. Nonetheless, we have gotten a few in the past where it was clear that way more time was spent, and I feel bad when they don't make the cut.
Tip - if you are giving out tests like this, ask for feedback from hires on how long they spent and then adjust accordingly. Anything you give out is probably way easier for you than the candidate.
The longest off-site coding test I've ever been involved with took 1.5 hours, split into two parts of 45 minutes. If they can't gauge your chops in an hour and a half of technical questions and real-time problem solving, they're not doing it right.
what i have a problem with is companies that want you to do the coding test before they've even talked to you. i may rule them out as a potential employer as part of that process, in which case it would be a waste of time.
10 hours is outright. That company is unlikely to value your time when you work for them.
1. Take a week or two off. Go on vacation. Maybe you just need a short break.
2. Find a new job as a developer. The change in environment (people and/or technologies that you work with) may do the trick.
3. Switch to a PM role for a while.
4. If you think being a developer is no longer fun, consider a career change.
Whatever you do, do not wait too long for the problem to fix itself. Do something now, before you start to drain out and find yourself unable to muster the energy and enthusiasm to come up with a solution.
Incidentally, if there exists a job orthogonal to your skill set as a developer that you can jump into and make upwards of half your current salary, that's a good sign you're not billing enough today.
- How old are you?- How senior are you in your profession?- Are you the sole provider for your family?- How much savings/equity/etc do you have floating around?- What other skillsets do you have that you could leverage?
The problem (I found, anyway) with 'alternative careerpaths' are that they either require some sort of previous experience (to get them, or earn a good wage, depending on where you live), or the ones that don't will have 1e10 other people lining up for it (again, depending on where you live).
It may be more productive to find a way to cut down on expenses and tap into savings, and try and learn something new, or get in touch with your inner geek again. A side benefit might be getting to spend more time with the kids/wife, or discover a talent or skill you didn't know you had.
My experience has shown that I don't want to get out of development, but having to do seemingly meaningless drivel for other people sucks the life out of our profession. I'm going to try and actively keep that spark alive going forward (not sure yet how, but at least it's a start).
I'm happy to chat privately if you're interested...
Time to maintain motorbikes or sailing boats. Do you know any craft, e.g. sewing, that could be used to make money in that market. Motorbike saddles, tarpaulins, seats and cushions are things I produce when tired from coding. Hand crafted quality sells well, and builds up a customer base that is even more loyal then a mainframe service contract.
Especially the biker scene has the tendency of regular up or outs. Some bikers move up, others move out, when ever a club closes, or is patched over. Same happens to good quality saddles also. So even if you do not sell to the Angles right now, they will might ride your saddles in 10 or 20 years, and they will be top paying customers.
Same same but different with sailing boats. Even if one can not move a tarpaulin from one boat to an other, like you could do with a Harley saddle, the sailors themself move up or out regular. They either buy a bigger boat, or quit sailing. Selling quality ensures a loyal customer, who tells his club.
You'll soon be invaded by wanna be customers every winter, if done right. Do not take to many, keep it to a maximum of 2-3 month of 20 hours work per week. Some of the sailing club customers might even become software customers next summer.
Other than that - I think it's hard to give an advice about career that would be both fun and wouldn't require a lot of skill to start with.
But if you are willing to invest time and effort - writing, painting, and computer graphics are the thing that I massively enjoy in my free time. I bet you could use your programming skills in 3D graphics as well.
Also - some sort of internet marketing. It isnt usually considered fun or worth doing among programmers, but it can actually be fun and profitable, and obviously a useful startup-related skill that you can utilize to make/sell your own products if you ever want to.
So I guess what I am saying is that maybe you can find a place where you can continue on your career path while saving your sanity.
Also when I get out I can go back to school and I'll have a huge leg up on government jobs. OTOH, if I can become a warrant officer I'll just stay in.
Yes it's risky/dangerous. I can't deny that. But I can say for sure it will get you in shape and builds a lot of discipline and character.
EDIT: Sorry didn't read the question well enough. Gardening isn't an good alternative career path to programming IMHO, just a nice distraction. Even helps you think about programming and/or other problems.
edit: source - https://news.ycombinator.com/item?id=7693262
> Ok, when people start racing to post these at midnight, and beg for upvotes on top of it, this experiment has officially jumped the shark. I'm going to bury this post and ask you all not to post any more of them.Only one account (whoishiring) is allowed to make regular feature posts that we don't kill as duplicates. (That's for the obvious reason of preventing karma sweepstakes and race conditions.) Should we make this "Idea" thread a regular feature? I've thought about it quite a bit. I think the answer is no.Experiments are worth trying, but this one has gone on for a month now and I don't think it has cleared the bar . Something about having all these ideas in one place makes the whole less than the sum of its parts. The threads seem to me to have gotten less interesting as they've become more regular.I'm sorry to disappoint those of you who disagree. But our job is to optimize HN for quality and I don't think the quality is high enough here. Ideas are better in the wild. Let's discuss them as they come up organically, rather than try to organize an idea-fest.1. https://news.ycombinator.com/item?id=7682938
But there's this:
PHP, as you probably know, started as a really basic (if obtuse) preprocessor for HTML pages. It plugged nicely into Apache via mod_php, and was relatively simple and low-footprint to set up, so a lot of cheap shared-hosting sites set it up. For beginning/inexperienced web developers on small projects, this was great; you no longer had to go host your own Java/ASP/whatever web server to have server-side logic, now you could just use a text editor and FTP.
Unfortunately, this also meant that PHP attracted a lot of inexperienced developers -- the kind who haven't yet learned things like why you should hash (and salt) your passwords, why you should use stored procedures, and so on. (Editorial: it didn't help that the language itself didn't, at the time at least, make it obvious how to do such things.)
Granted, there were some developers who knew better who picked up PHP. But generally developers who have some working knowledge of web security best practices get that knowledge by working in the field -- which at the time, typically meant "heavier-weight" stuff like Java or ASP.
So with large numbers of inexperienced, security-unaware devs enabled to write webapps in PHP, large amounts of poor, insecure PHP code was written. So PHP got a bad rep, which only exacerbated the problem by creating a self-fulfilling prophecy that turned companies who could hire more-experienced devs off from PHP.
I haven't personally touched PHP in a long while -- I personally just don't like some aspects of the language -- but I've heard some steps have been made in the PHP community to make best-practices more easy/commonplace. Which is great! But the old reputation is still there, and bad reputations are hard to dispel -- especially in the corporate world.
These people are probably thinking: "If you truly knew infosec, you would have moved onto a more advanced language by now."
PHP has a reputation as a "training wheels" language. It's seen as a great starter language to learn the fundamentals of web development, but the expectation is that a "good developer" will eventually migrate to Python/Ruby/Node/whatever once they outgrow PHP.
By staying with PHP, you're signaling that you haven't cleared the bar of being a "good developer" yet.
Take something like == to compare two strings. A reasonable person would compare them as strings. A PHP developer would try to compare them as numbers (losing information in the process). Many PHP users don't consider that a problem. Many PHP developers don't consider that a problem. (Some realize it's stupid but don't want to break backwards compatibility).
Edit: It also doesn't help that two of the biggest PHP projects are Drupal and WordPress, two pieces of software with atrocious security records.
I don't share this belief mind you.
that's reason enough not to take that person seriously - a truly experienced fellow programmer would have a tough time making that presumption about another programmer in ANY language