Have you explored any non-digital marketing channels for growth yet? I am working on a sales model for companies like yours that sell to small/medium sized businesses. Would love to chat if you had some time to discuss. Is there a good way to contact you?
I can't be alone in being exhausted at these studies. Doctors and Lawyers have spent the better part of the last century working on little to no sleep. Academics too. As an engineer, I would regularly work through little sleep because the process of loading a large project into my head to work on it would take more time than the gains from being more well rested. I'm older now, and no longer work as an engineer. I value my sleep and appreciate how much more I can task-switch on a good nights rest, but the idea that I'm not being productive when I'm grinding through work that has to get done and I'm tired seems an overwritten idea.
I'm not arguing against rest and recharging and clearing your mind. I just don't see what these articles are trying to prove. When I was in college I had several stints of no sleep days to finish projects. Even into my early engineering career, I once billed 40 hours straight. Was I as "productive" per minute for that entire time as if I had slept through 5 nights? No. Would the work have gotten done faster than those 40 hours if I had slept for 8 hours in the middle a few times? No. I had a deadline, and there was nothing getting around the work needing to be done.
The argument seems to be against a constant sprinting mode, which I don't think any company employs. Humans burn out after continuous work for weeks, sometimes months. But a week or 3 of little to no sleep to get through everything you need to? It's worked for a long time. Arguably building up muscle memory while forcing rote things to be learned while on little sleep works. What are we trying to prove by this? That "the man" is out to abuse workers? Of course he is. But did anyone make partner at a law firm by claiming he's going to more productive by working less? If you're goal is work life balance, go ahead. But if you're goal is to excel in a field, then it probably involves some sleep deprivation. PG wrote an article about the reason startups were suited for youth is that you could push through unreasonable hours to crank a lot of life into fewer days.
Sorry for the rant...just wondering if I'm alone in thinking this
If you're saying that in the short term, short-term thinking works, sure. If you're in college and are doing a bunch of work that doesn't matter to deadlines that are entirely made up, sure, you can get away with it.
You claim that doctors do fine without enough sleep, but even doctors don't claim that any more. Doctor friends tell me it's a big focus for reform. [1] And in areas where safety is even more important, like piloting planes, they take mandatory rest even more seriously.
Software is mostly not life-critical, but I think it's uniquely bad in this regard. Doctors can bury their mistakes, but version control systems preserve ours forever. It's too easy to be negatively productive in software, and enormously easier if you're not getting enough sleep.
I don't mean to claim doctors do fine without enough sleep. Doctor friends I have spoken to talk about this talk about the reforms but it is not uniformly positive. I am trying to posit that the claim that we function better with more sleep is true. But that claim is made in a vacuum. Person A operates at 100% well rested. But operating at 80% or 60% is more valuable than 0% if averaged out over time. So I can write better code when I'm well rested, sure. I agree with that. I think everyone logically will. If I have 1000 lines of code to write. And it will take me 10 hours to write it. And I have 2 days to do it. I'll spread it out over 2 days and write good code, and maybe it only end up taking 800 lines of code. But if I have 1 day to write it. I might end up writing 1200 lines of code, but still get it done in that day, it is more valuable to me, than a day later when the code doesn't matter anymore. I'd argue I'd rather a doctor save my life that day, than do a great job and make sure I never scar over two days when the option isn't there.
Medicine is a regulated industry in that the number of people trained almost precisely matches the number of jobs available. The training process is designed to prune out people who cannot function when they have to choose between life saving procedure, and doing the life saving procedure perfectly but losing the patient. It's a straw-man I know, I'm just tired of everyone being absolutely fascinated by this idea that resting is better than not resting. Isn't that just obvious? Does anyone feel like they work better when they are tired? What knowledge are we gaining by these discussions?
If you are throwing away your tired-brain code a week later, godspeed. Do what you like. But if you are checking in that code and making other people deal with it, then quality becomes much more important. If you write 1200 lines of code instead of 800, then you have something that has 50% more maintenance cost and 50% more bugs. (And it's probably worse given that you were tired and thinking with a short-term mindset.) So hell yes, it matters to me whether my coworkers are putting long-term value above short-term incentives.
> I'm just tired of everyone being absolutely fascinated by this idea that resting is better than not resting. Isn't that just obvious?
It is not in fact obvious. So many places reward time spent more than quality work. Just today at a meetup we were talking about how to shift people away from damaging and expensive heroics to investing in not creating such big problems that you need work-all-night heroes. The industry is notorious for death marches and work-all-the-time startups. And it's also notorious for buggy, low-productivity, high-tech-debt code bases and giant rewrites caused by years of accumulated short-term thinking.
If it's obvious to you, skip over the articles. Not everything has to be for you.
> I'd argue I'd rather a doctor save my life that day, than do a great job and make sure I never scar over two days when the option isn't there.
> What knowledge are we gaining by these discussions?
Sure, if that was all there was to it, then you'd be 100% right. The knowledge we seem to be gaining from these discussions is that a programmer who works 6 hours a day is overall more productive than one who works 8 hours a day, let alone one who has been on a 16 hour death march for 6 months. The same idea applied to the doctor example may mean that your doctor is less likely to save your life if they're on the 28th hour of their shift than one that wasn't.
Yes, there's a time and a place for burning a candle at both ends, but we seem to think that this is OK to do in the long term. So sure, if you need to pull a rare 20-hour marathon to fix an urgent problem, do it - the value might well justify the cost. But don't tell yourself that it's sustainable or even optimal in the long term, evidence seems to suggest the exact opposite.
The comment about stickers makes me think you don't understand how much money they make and how much people use them. It's massive. Look at Line made 17 million from stickers in Q1 this year, Kakao made 311 million in revenue and I'm not sure the breakdown but stickers is significant enough that it's mentioned in with gaming as the main source of revenue.
Stickers, whether it's reasonable or not, are a great way to monetize on messaging.
Snapchat also allows you to find someone to talk to that no other service does as seamlessly. From my understanding anyway, people will send out snaps to a group of people, many time everyone they're connected to and after a few snaps back and forth with one or two of the responders, they'll switch to another channel and chat. One could argue adding messaging here would increase the stickiness, but I think snapchat is right in that adding it in would just be distracting.
I think if your main source of income is stickers, that's risky. They will (and already are) become commoditized - with MessageMe, Path, etc... all jumping onboard.
I'm guessing that stickers (siloed in each app) are a fad that will eventually go away.
Are you just boring? It's obviously not something that should be done everyday but that doesn't detract from how awesome it is. Were you never young? Did you not try to go for glory on something that had risk?
You can do things that are risky, and require awesome amounts of skill, without risking innocent lives.
I watched the Rendezvous Video described in the article - but, the skill demonstrated in something like http://www.youtube.com/watch?v=LuDN2bCIyus tops that signfiicantly. Also - note - street driving, closed course.
It is natural to want to go for glory, but it's just plain selfish to pursue personal glory by risking other people's lives. It's awesome in the same way that the Conquistadors were awesome.
Having survived several accidents at the hands of other drivers going too fast, I can say I don't find it awesome at all. I think it's more just ignorant, particularly of how stupid and horrible you would feel if this kind of driving resulted in injury or death of anyone.
I'll bite. Your comment doesn't say anything...what are you talking about? What is your world? Why is it different? If you want to throw a comment it in, it would be a lot more useful to have some context and reason...
Before I really started coding I worked in electronics (designing mixed-signal design kits at the semiconductor level) and I remember I used to judge programmers by how much "better" at google they were than me. Since I've switched over and become a full-time coder (and co-founder which is a whole different exercise) I have become far better at searching for solutions to my problems than I was in the past. That being said I don't think it's the fact that I default to searching that makes me a good programmer. I think it's like some of the other comments have mentioned, the ability to filter what information is useful or not quickly and then apply and test the useful information so that you do not have to re-derive every action. This has led me down a rabbit-hole a few times where I would be testing different solutions when just building it myself would have been much faster, but overall I definitely think it is part of what makes me work at the speed at which I do.
I'm reminded of Mathematics from college. When first learning something it's difficult and simply seeing the solution won't improve your ability to recognize it. But once you figure it out once, you may not immediately remember how to apply it when faced with a similar problem, but recall is very quick because your brain has already wired the pathways of understanding.
