I am 42-year-old very successful programmer who has been through a lot of situations in my career so far, many of them highly demotivating. And the best advice I have for you is to get out of what you are doing. Really. Even though you state that you are not in a position to do that, you really are. It is okay. You are free. Okay, you are helping your boyfriend's startup but what is the appropriate cost for this? Would he have you do it if he knew it was crushing your soul?
I don't use the phrase "crushing your soul" lightly. When it happens slowly, as it does in these cases, it is hard to see the scale of what is happening. But this is a very serious situation and if left unchecked it may damage the potential for you to do good work for the rest of your life. Reasons:
* The commenters who are warning about burnout are right. Burnout is a very serious situation. If you burn yourself out hard, it will be difficult to be effective at any future job you go to, even if it is ostensibly a wonderful job. Treat burnout like a physical injury. I burned myself out once and it took at least 12 years to regain full productivity. Don't do it.
* More broadly, the best and most creative work comes from a root of joy and excitement. If you lose your ability to feel joy and excitement about programming-related things, you'll be unable to do the best work. That this issue is separate from and parallel to burnout! If you are burned out, you might still be able to feel the joy and excitement briefly at the start of a project/idea, but they will fade quickly as the reality of day-to-day work sets in. Alternatively, if you are not burned out but also do not have a sense of wonder, it is likely you will never get yourself started on the good work.
* The earlier in your career it is now, the more important this time is for your development. Programmers learn by doing. If you put yourself into an environment where you are constantly challenged and are working at the top threshold of your ability, then after a few years have gone by, your skills will have increased tremendously. It is like going to intensively learn kung fu for a few years, or going into Navy SEAL training or something. But this isn't just a one-time constant increase. The faster you get things done, and the more thorough and error-free they are, the more ideas you can execute on, which means you will learn faster in the future too. Over the long term, programming skill is like compound interest. More now means a LOT more later. Less now means a LOT less later.
So if you are putting yourself into a position that is not really challenging, that is a bummer day in and day out, and you get things done slowly, you aren't just having a slow time now. You are bringing down that compound interest curve for the rest of your career. It is a serious problem.
If I could go back to my early career I would mercilessly cut out all the shitty jobs I did (and there were many of them).
One more thing, about personal identity. Early on as a programmer, I was often in situations like you describe. I didn't like what I was doing, I thought the management was dumb, I just didn't think my work was very important. I would be very depressed on projects, make slow progress, at times get into a mode where I was much of the time pretending progress simply because I could not bring myself to do the work. I just didn't have the spirit to do it. (I know many people here know what I am talking about.) Over time I got depressed about this: Do I have a terrible work ethic? Am I really just a bad programmer? A bad person? But these questions were not so verbalized or intellectualized, they were just more like an ambient malaise and a disappointment in where life was going.
What I learned, later on, is that I do not at all have a bad work ethic and I am not a bad person. In fact I am quite fierce and get huge amounts of good work done, when I believe that what I am doing is important. It turns out that, for me, to capture this feeling of importance, I had to work on my own projects (and even then it took a long time to find the ideas that really moved me). But once I found this, it basically turned me into a different person. If this is how it works for you, the difference between these two modes of life is HUGE.
Okay, this has been long and rambling. I'll cut it off here. Good luck.
Until this one project where we were asked to 'fix' an already written Android app (written by an Indian outsource then sent to Canada). The contract was for a massive amount of money, everything looked clear cut and straight forward, how could we say no?
For almost 7 months (!!!) my team and I had endless meetings next to a wall map containing the 5000+ classes that each had to be dissected, understood and reimplemented properly. All the comments were in at least two different foreign languages, and even the best translation services (human included) could only give us at best translations like: 'not class, forwards' or 'use brick making way here', most likely due to the comments being poor in their original language in the first place (not due to the translation).
At first I had great momentum, I was an unstoppable force; then quickly things started slowing down - each task started taking hours longer, than days longer, than weeks longer. Ultra trivial fixes like the placement of one statement outside a try catch, could easily take a whole month to locate (by a team of 4!).
After pouring my heart and soul into this project day after day, grinding myself literally to the bone; I started getting depressed, physically sick to my stomach for days at a time, starting fights with co-workers over absolutely nothing, just so I wouldn't have to look at that fucking code one more time. Anything to just not look at that code one more time.
By the end of the project (which we did actually manage to complete), I was waiting for that moment of euphoria, that release of completion, that I would never ever again need to look at that code, or work on that project.
But it didn't come.
I was paid more than 100k for completion of the project, so I was well reimbursed for my time.
That's when I realized that it's really not about the money, it's not about the team, or the language; It's not about your repo, or your source control techniques. It's not about agile, and it's not about problem solving. It's not about working from an office or from home, and it's not about the mother fucking 'culture'.
When you're lying on your death bed, and you look back; will you be proud that you spent all that time and suffering to fix an app for some asshole who is trying to make a quick buck by exploiting people who aren't technologically wise enough to realize what they are doing?
The next day my boss asked to meet with me privately; thinking I would be fired (and happy with the idea) we met briefly at a local coffee shop. She said that all the anger, depression, and self loathing was 'worth it' because 'I made a lot of people rich' in the process (myself included) and they were happy to deal with that (and even to pay for therapy).
I was offered EVEN MORE money to continue working on projects exactly like these, to the company we had just discovered a cash cow of an app crop, and I was the golden goose. I could easily do this the rest of my life, and lead whatever life I wanted to outside of work.
I quit on the spot, and laughed and cried the whole way home. Knowing that I would be blackballed in the community that I had worked so hard to establish myself in.
Literally career suicide. The company didn't recover, and a lot of people were (and still are very pissed off with me - like angry emails, restraining orders, fucking pissed).
I promised myself that from now on I would only do work that I believed in enough to starve to death for (and it was looking for a long time like that was going to be the case). The truth is, if you want a job where you can make 6 figures (or even 7 if you're doing it right), you will find it. You will always find it, and they will always be there.
There is a vacuum of talent on the community of expert programmers caused by major corporations like ibm, amazon, facebook, twitter, and snapchat just filling up cubes in their 'programmer cluster'. A group of people they can throw whatever stupid, or trivial tasks at - and you won't say shit, because damn that pay is tasty. You're breaking peoples rights to privacy, doing WAY less than ethical things, and you probably don't even know it (because that's how it's supposed to work, or someone else above you clearly isn't doing their job).
My only advice is to get the fuck out. Run, run as fast as you possibly can and never look back.
Never respond to any recruiters for any reason, never respond to job offers, and don't even think about looking for another position at another company (I promise it's the same thing, no matter how they promise you otherwise, and tell you that their culture is the dopest - nothing like clubbing seals with some rad people right?).
Get off your ass, and do something worthwhile. If you can't do that, then learn how. If you can't do that, then you're a drone and you should keep that shitty job because it's the best you're ever going to do (in which case, fuck you, you make the world a worse place for everyone by whoring your skills out to unethical assholes for cash).
Make something that garners zero profit, make something that only helps people, make something that changes the world for the better. You will quickly see your entire world, and all the people in it change before you eyes. You will get more job offers in your inbox than spam, because the world will see that you don't give a fuck about anything but getting shit done and helping people.
Today I run a few companies, the largest of which is a NPO machine learning research firm offering free services to help cure cancer, track missing children, follow and assess viral outbreaks, and front line ML research pushing the needle of science forward (email: freeML@gatosomina.com for services); and some of the others include: organic vegetable gardening as a service (physical outdoor labour, everyday, which I enjoy more than anything) and free apps that assist paramedics and doctors (without ads or bullshit).
If you want to be happy, like, really, actually happy (and not just wealthy) you're going to have to risk it to get the biscuit; and it's going to be the hardest battle you've ever fought in your entire life, by at least a few magnitudes.
Good luck, it's a jungle out there.
If this sounds like it could be your style, grab a buddy and see if you can hammer out some of the small stuff together. If not, some of the other suggestions here are good as well.
First of all, isn't it a bit dramatic to say "your entire being opposes" your task? It's not like you're out committing genocide or something. You're programming, and you have to work on a crappy programming task. Every programmer who ever worked a professional job has had to do this at some point. If the very fiber of your soul is wrapped up in your employer's MegaAccounting Client V3.0 REST API, I'd recommend re-thinking your emotional attachment to your job.
That money you get every two weeks is called "compensation" because it is compensating you for your time, which you would probably otherwise spend doing something more pleasant. This is the realistic world of grown-up work life.
If your company's Marketing bone-head says the customers want a green oval button instead of a system-standard button, well, it's stupid, but I'd laugh at how much they're paying to get this ridiculous code written and just write the damn code. It's really not worth losing sleep or sanity over. Not being emotionally attached to your work allows you to shrug off the stupid stuff that Really Doesn't Matter.
Quit. Get out. Work out a plan with your BF. It's no good to you or himif you destroy yourself on work you hate. Be happy and poor togetherrather than rich and dysfunctional apart.
I've never had to work (for a long time) in a job I truly hated, butI've felt the pain of working in a company with a poor managementculture -- it's taken me a long time to get back the joy of developmentsince I left. I now work in a completely different, low paying job --but it's better being payed less and not having to compromise your workevery day. I'll probably end up with another job in the industry (well,I hope, anyway!) -- but I'll be very careful in choosing where I apply-- unless I manage to make a living independently.
For you it sounds pretty much anything, anywhere would be an improvementthough...
I had a gf that worked in a job that crushed her (shedid the right thing, moved away, got certified as a padi instructor andnow lives with her husband and their child, both working as divinginstructors -- I'd say she made the right choice :).
Quitting might not mean that everything works out for you and yourcurrent BF -- but it sounds like staying will ensure that things willnot work out for you.
Anyway, good luck, whatever you end up doing...
I struggled with this for years and years. This is not one problem , but three: it is a problem with wisdom, speed, and discipline.
Luckily, we can learn tricks to improve each one.
If we want to attack this from the wisdom perspective, it is this: You are afraid of making the wrong decision because you are afraid to refactor. You are afraid to refactor because you don't have sufficient test coverage.
The good news is, for developers like us, test driven development is very helpful as a technique for getting us over these problems. If our team is not test-friendly, however, it will be difficult for us to make the jump because their code will not be written in ways to make it easy to test.
There are a few books I can suggest to help us jump the chasm:
1. Clean Code by Bob Martin. This book helped me think in more testable code, and also helped me understand how to make better decisions the first time around. It helped me by seeing patterns I didn't know first.
2. Refactoring by Martin Fowler. This one is old, but knowing the patterns of changing code gives us more confidence in knowing what is right, rather than hemming and hawing over what is readable and maintainable.
3. Refactoring From Legacy Code by Michael Feathers can help get from here to there. All of these help from three aspects: They help us develop a set of tests so we are less afraid of breaking existing things, they give us the freedom to experiment, and they help us break things down into smaller, more manageable problems by letting us think about "what is the next thing I can test?"
If we have the tests, we can be more aggressive in reducing complexity.
If we want to attack this from a Speed issue, then look for these things.
1. Look for patterns you use repeatedly, and try to settle down into a process. The fewer choices we make, the faster we can go.
2. Look to learn more about your chosen stack and language. It is possible that we are rewriting the wheel over and over. The more you understand the zen of your stack, the faster you can go and the more time you can devote to writing the same thing twice (without them knowing.)
3. Instead of hemming and hawing about the right solution, write all three. It is often faster to write all three and choose one than to get stuck in analysis paralysis. (That isn't to say you shouldn't think before you write code!)
Finally, you can attack this from a discipline angle.
1. Learn to meditate. By doing so, you can become more self-aware of analysis paralysis, calm your mind quickly, and mindfully choose a path.
2. Exercise. In the same way as meditation, exercise helps us learn to clear our mind and focus on command, and it helps sharpen our discipline chops.
With these, we can develop an awareness of how our body feels. Then we can develop an awareness of how analysis paralysis feels. If we can catch ourselves in the act, we can then institute something from our analytical skills: When caught in the trap, set 30 minutes on your timer, and bring out a pad of paper. If you feel you have the freedom, turn off the monitor.
Take deep breaths, and sketch out the solutions in the first ten minutes on the first page. Use UML or your own system.
In the next ten minutes, write a pro/con analysis on each path.
In the final ten minutes, make the decision. After this, your analysis time is up and you must code.
I suggest a combination of the above.
Good luck! It was one of the hardest things for me to defeat.
But I do encounter many chores in my work that are boring, that are bad ideas, that are for difficult customers, or often all three. I can have the same problems getting those tasks done, just like you describe. Actually, you seem to be way ahead of me because it took my far to long to figure it out. I thought I was losing my ability to program. I was wondering if I was going to have to find another career because I had lost my ability to concentrate. I was reading books on getting things done, and concentration and trying to figure out what the hell was wrong with me. I would sit down to do a task, check email, check reddit, check hacker news, check reddit, get coffee, go to the bathroom, check reddit, "Arg! I have shit to do!" Check reddit, check IRC, etc. I caught myself more than once closing a browser tab with some distraction, pausing for a half moment to organize what I should actually be doing and then open a browser tab to the same thing again.
The insite came when I finally got something engaging to do, and I just powered through it. I could still program! How did I get in the zone? How do I get there again when I need it? Well I worried about hat for a while, thinking there was some combo of sleep, nutrition, environment and task management software that I could line all up and get back to "the zone". It finally dawned on me that I subconsciously find distractions to avoid doing things I don't want to do. What a revelation.
How do I get over it? Well I still struggle with it, but simply identifying the problem was a huge step towards fixing it. Here are some techniques that I use:
Pomodoro technique. This is a productivity trick that actually works pretty well for me. The short version is that that you make a list of very small tasks, then work for twenty minutes (straight! no phone, no emails, no coffee, no bathroom), then take a five minute break. This helps with distraction problems because you can tell yourself, "I can goof off in 7 minutes". It sounds like a lot of interruptions, but I'm amazed at how much I get done with it.
Creating crisis. I work harder with the Sword of Damocles hanging over me, so I put those swords there myself. Call me back at 2:30 and I will have this done. Then I'm good for two hours of, "oh shit, oh shit, oh shit," type production.
Pair programming (and rubber ducking). This really helps to power through crummy tasks. Unfortunately, I work from home for a tiny company. I don't have anyone to program with. But if I am really stuck, I can ask my wife to sit next to me, while I explain what I am doing, and what I am trying to accomplish, and the details of what I am coding as I code it. I can use this occasionally to get over a hump.
Change of venue. I have struggled to find some shitty bug in some shitty spagetti code for a crappy website selling stupid things for WAY too long. The only way I broke through was to take my computer somewhere else, in front of other people. David Sedaris has a great story about a book suggesting he make a change in his house to help him quit smoking. Buy a new couch or something in order to change the venue. In our comfortable habitual surroundings we act in comfortable habitual ways. So he moved to Japan to stop smoking. I can't do this every day, it's just for breaking major blocks.
Anyway, I need to get back to work. Good luck!
I'm a manager, and sometimes I feel like you. Sometimes I need to ask developers to do things I don't believe in or things I'll throw away in a few months. This also demotivates me. You need both a lot of discipline and just a bit "aloofness" to keep going. Care less about those tasks, think about friday.
If your managers are any good, they know you have wasted hours, they know you are unmotivated, and they know those meaningless tasks are the reason, this is why you are a valued employee. I'd rather argue to death with an employee because he thinks his idea is best for the company than one that will just accept any task like a robot. But sometimes you have to implement ridiculous things into software, from clients being just crazy or because of some strange contract clause. This is when discipline kicks in. Such situations shouldn't happen often, but if they are, that's when you should move on.
You don't need to get "in the zone" to get the job done. Just start by doing smaller pieces, put your headphones on. You could just ask why feature is being built, but I doubt knowing the reason will motivate you at all.
2.) This is surely arguable, but I think agonizing over a lack of satisfaction/motivation in a job is likewise a waste of time. If you can get those things at work, great - if not, don't try to force it - redirect it to side projects, friends, family or hobbies.
3.) Life is really short and full of trade-offs. Be sure to regularly re-evaluate your position or you might find yourself stuck rather than simply compromising.
>'How do you get in the zone and get it done when your entire being is revolting against the task?'
Through each of the things I described above. Whenever necessary I remind myself that:
* I'm a provider and professional, my family depends on me and I'm paid to do good work - getting this done is not optional.
* My time is short, delay buys me nothing.
* I have no shortage of great things to look forward to when I'm done.
Is waste really the right word here?
They don't see how many hours I have wasted, how unmotivated I am. Instead they treat me as one of their most valued employees (oh the irony!).
"When given a vague, annoying feature to implement, very carefully considered approaches and built it in a surprisingly readable and maintainable way"
What you're experiencing isn't atypical - sometimes programming something sucks! Your employer values your ability to power through it and still get good results.
1. If I'm working on something vague, try to extract more information about it. It's very hard dealing with frequent changes on a complex code base. I'd try to find out who the stakeholders are, customer is, and most importantly, what they are trying to achieve that this serves.
2. Break it down into smaller tasks and measure myself against these. I want to leave work having completed something and not return to work knowing I didn't complete something.
3. Try bringing a colleague in to help you, such as talking through the existing code and bouncing ideas off them. The energy a colleague puts in can help with motivation.
4. Make sure there is an end to it and that it's not an open scope. You'll never finish something if the stakeholder doesn't know what they actually want.
5. If this looks like it's the norm and you're not happy, while you say you can't change jobs now, put the plan in motion for when you can. Think about your CV, learning new things, etc that help. When the time is right you want to be ready to jump.
6. Get enough sleep. I find I procrastinate more when I'm tired. Of course, eat healthily and exercise.
7. Try to remove other distractions, such as any other commitments at work as a 10 minute interruption can cost you an hour if you're not in the flow of the work.
As far as I know the only way to get over burnout is to stop. If you do not you will suffer more. I wish I had better news.
But, enough on that. A few years before then, I felt like you did, but I wasn't actually in that situation. There is a very real positive feedback loop in effect - you feel like you're doing a bad job, so work longer hours on it, end up taking longer, feeling like you have "wasted" hours, and feel worse about doing a bad job.
Believe your employers when they say you are doing great, otherwise you're likely to be heading down the burnout route which had me off sick for half a year. It's not every coder that has such high standards as you, and that is not something to be ashamed of. Be proud of the code that you have produced. Think to yourself "It's just as well I wrote this bit, because if X had, it would have been awful".
I know this sounds like extreme arrogance, however sometimes it is necessary for the purposes of regaining balance. It sounds like you are being a little too humble. If it gets too bad though, get some help from someone.
Dealing with a rough situation that you have no external control over is one thing, dealing with a lousy job you do have control over it. Let go, walk out the door, and look for something more fulfilling.
Those conversations have taken my team and I to interesting places. I've discussed brand positioning with developers, and shared spreadsheets of time-to-value models with designers, at times going far outside of people's skill sets and comfort zones. If someone insists a piece of work is a bad idea, I invite them to argue against it but insist that I need them to make their case rigorously. Sometime they'll convince me, sometimes they don't want to work through the reasoning, sometimes I'll try and develop their case and argue against myself. I want to reach a position where we either change the task, or we're both satisfied that the task should be done. If that's too hard, then I'm after a position where they at least have rational faith in my request and my reasoning, and are ok to do the work on trust.
I spend a lot of time on this, for a few reasons.
First, I don't want to ask anyone to do something meaningless. Burnout isn't caused by workload. Workload causes exhaustion. Burnout is caused by resentment. If my team resent their work, that's a deep and important problem. I'll tolerate a only very small amount of that, but I'll let everyone know I'm conscious of it, don't like it, and am working to get away from it. Burnout is toxic and damaging to people and the group as a whole.
And secondly, this kind of explanatory work strengthens everyone's investment in the team and the work. It strengthens the team's ability to think together. As people become better informed, all of our discussions become richer and more valuable. People enjoy the work more, and can relax and trust each other more, knowing that decisions are made in ways they can understand and agree with.
Finally this is also a litmus test for me. If a company won't let me in on it's decision making, dismisses my concerns as unimportant and tells me to just get on with something, they're indicating they don't value the team in the same way I do.
That being said, I've worked a couple jobs in the past where I felt similarly to you--one of which I objected to much of what I was working on not only from a utility standpoint, but from a moral/ethical one as well. The only thing that kept me going was the social network I built of similar-minded coworkers. The ability to vent, joke, and commiserate with people who felt the same way I did at the company was extremely cathartic and served as my therapy. I don't think that's a good substitute for getting out and finding something else that you actually enjoy, however, which I eventually did when I realized how it was affecting my mood even outside of work.
Pick things that incidentally accomplish the assigned goal. For example,
1. Pick an amount of time, like 3 hours, repeat this cycle
2. make a branch
3. implement the feature in the fastest way you can
4. think about why this isn't acceptable
5. throw away the branch
6. do it again avoiding one thing that made the last one crappy
Also, weighing merits of different solutions and picking one is your job -- no need to feel bad about that. Come up with an assessment tool that will help you decide. Time-box decision making, but don't stop thinking about your solution -- just give it the appropriate amount of time, not unbounded.
Making progress is motivating. You want to end up at the same place but have the feeling of progress making throughout the process. I believe that it's possible you are taking the appropriate amount of time to do the work at hand, but you are getting into an anxiety/depression cycle because you can't get into a flow state.
The other thing is that if they value you, it's probably for a reason. You're fulfilling their expectations and providing them with value. Take the compliment and go with it! http://en.wikipedia.org/wiki/Impostor_syndrome
Your managers demanded a stupid feature, and you took long time implementing the stupid feature due to its complexity.
The only thing missing is you need to warn your managers before you start coding such as "This is going to take long time due to the complexity, many many weeks. Also I don't think it's right for the product either."
As long as expectations are clear beforehand, and you met those expectations, then no one is getting fired, and therefore you should relax and enjoy coding Easter Eggs into each shitty feature.
My suggestion go on a vacation, if it doesn't get better... leave. You say you're not in a position to leave... but you have to, because its not going to get any better. You're not really doing anyone a favor by burning yourself out for them.
One of the things that I found helped me the most when dealing with features like this is to Let Go of Caring about that particular thing. We fight for what we believe is best, but when a customer, manager, or other higher-ranking stakeholder decides otherwise, it's out of our hands. You did your professional duty by arguing for the Better way (as you see it), but now it's time to make the new direction work.
UX team decides buttons should be the way that pisses you off the most? It's OK, you're not the main user.Manager decides that a "Calculate" button is better than auto-re-calculating? That's ok: the users are happier using that. (We can transition later.)They want an e-mail based workflow for approving things, rather than a web-based one? That's OK: these execs spend most of their time with their phones, and don't want to be logging into the website.
Often what we feel is "unnecessary complexity" is a workaround for a key use case that we didn't realize, or yields customer happiness because it's what they asked for. In that case, it's __necessary__ complexity, just like a bit of ugly code that patches a bug. Try looking at it from the perspective of the user or the manager, and really understand why they feel it is important -- quite often, it's addressing a weakness of your software product that you were not aware of, or which you felt was unimportant.
I think many of us know your pain, and as a consultant I'm exposed to it on a pretty regular basis. It takes some of the fun out of my job for sure, but I don't let it stress me out. First, we should always want to be passionate about the projects we work on, and I think this is a result of being passionate in general. Being passionate makes it enjoyable, and it allows you to bring your best work forward (which is rewarding), but in our industry we must always create a balance of cost and quality in the midst of a very complex process. To me, this all boils down to priorities and expectations.
When you take your own priorities and combine them with those of someone else, you will never be able to get them to mesh completely. Your priorities may be to make quality code, or to make it elegant or smart -- easily maintainable, extensible, etc. etc. These are things that make it fun, and programmers all know the benefits of these things. Clients, or your bosses, may not understand the importance of these things, or they may, and they may be willing to pay it down later, whatever the case may be, there are conflicting priorities at play and this is the thing you must mitigate to avoid stress.
For me, I must either disregard the external priorities entirely and do it the way I believe it "should be done", or I must disregard my priorities entirely and adopt the external priorities as my own. This may result in technical debt, or a slow progression in the future, or can raise the potential of bugs to be introduced, but these are not my concerns if they are not part of the external priorities.
It's important that you communicate all of my concerns up front, and if it doesn't impact the priorities that are communicated, you must trust that it's ok. If you don't trust that it will be ok, or think you will be negatively impacted by doing it the way you're being asked to do it, you should leave. A management(or client)/ employee relationship is built on trust, and if you don't have that trust you will be less happy than you could be.
"Unnecessary complexity to the codebase"
It depends on what you mean by unnecessary. If you mean "won't bring in anymore customers", have that conversation with your managers. Not all of them are brilliant, and no one gets it right 100% of the time. If you can prove that the feature doesn't provide value, have that conversation with them.
On the other hand, if your boss ignores your input, and you're 1000% sure that there are other features that are more valuable to your business than the one in question, you can always push that one to the back and work on something that's more productive to the company. Depending on your political and professional circumstances, your boss may not notice or care, and their boss may forget about their red herring feature; you might be able to side-step the conversation altogether. This will only work if there's more than a few items on your plate that need to get done soon, and this feature can get pushed aside without delaying or blocking anyone else.
Bear in mind that if you go this route, you're putting yourself, your career, and your neck on the line. If it turns out that it wasn't a good idea and everyone agree with you, you'll look like a genius and gain some clout as a clairvoyant; if it turns out it was seriously necessary, you'll look like someone who pouts when they don't get their way. Either way your boss may also hold a grudge. I'm not saying it's the greatest way to go, just adding it as an option. It's helped me more than a few times in my career, but it's also frustrated my bosses a few times. Be gracious if you're shown wrong though, and quick to admit defeat if it's obvious you chose the wrong path, and you should be fine no matter what happens.
We have a right to be happy. We should make decisions that satisfy the majority of our lives and where do what we love. For things not under our control, we still need to love what we do.
The easiest solution to your problem is creating discipline and decisiveness. When you give yourself more hours to work than you are expected to, you create a vacuum of inefficiency. You work unsustainably on things of little value. Instead I would force you to a) figure out your success criteria, b) what are those steps, c) prioritize those steps, and most importantly d) set time limits for each of those steps. The constraint of time will force you to get to the 80% quickest. I have written some articles on these exact problems and in the process of creating an app with those insights. Feel free to read more here: https://medium.com/produce-productivity/ee13c1600b6b
I seem to have a finite pool for motivating (or more accurately forcing) myself to do work. And when that pool is empty, it's off to HN or Reddit I go. Frustrating, and I still don't have a solution yet.
Hope this helps.
This time is not entirely wasted. Even in the worst case -- where the code you are so carefully writing winds up not being used after all -- you are getting good practice in code craftsmanship. The next time you are faced with a decision similar to one you are making now, you will make it more easily: not only have you considered the issues before, but you know how one of the possibilities actually worked out. This is how one builds experience.
I usually find that writing code slowly and carefully is in fact the fastest way to get it done, because it minimizes debugging and rewriting. There are exceptions, such as exploratory programming, when you know you're going to throw the thing away anyway, and in small utilities built for personal use; and there are times when getting something working quickly is important (for a demo, for instance) even though you know you'll have to rewrite it. But these are exceptions. When you're implementing important functionality that's going to be in the product for the foreseeable future and that others will have to maintain and build on, the slow, careful way is best.
It seems to me the real problem here is that although your managers value your work, they don't listen to your architectural opinions. That's a serious problem. Maybe at some point you'll need to tell them, "if you want it done that way, you'll have to find somebody else to do it". Pick your battle carefully though -- it needs to be a case where their way is clearly and substantially suboptimal.
Without going into details, in my case the task is implementing a terrible, hacky solution for a total edge case problem. It's something I will probably never do again in my entire career.
It's draining. It claws at my self esteem, as I sit in the office wasting literal hours during a day not doing anything. The output of the 4-5 hours of actual work I put in over the course of a week appear satisfactory to the stakeholders, which is mind blowing.
I know that the sooner I get this done, the sooner I can move onto something more interesting. However, just working on this particular task has sapped my will like nothing I've experienced before in my career as a developer.
They don't know this code is generally unrelated or don't complain to me about it. Only problem with this is I can now be opening up new bugs because these revisions aren't always fully QA'd.
If I cant get the motivation then I need more abstraction. Abstract until you drop! You are naturally conditioned towards completing things and positivity. That's why people get badly addicted to games like farmville and such. You do something simple, you get something back, you do something else, you get something else. Really your just baking time. But the psychology of achieving is where the addiction comes from. It's not the game. It's the fulfilment from completing something. You need to see this progress visually so you feel like your moving.
It's not uncommon for me (when I'm really low and scraping the barrel) to have a task like for a job such as this;
[ ] Open Sublime[ ] Set-up folder structure[ ] Skim read spec[ ] note areas of concern for later [ ] Describe required method to self / colleague / rubber duck [ ] pseudo code initial method [ ] expand pseudo to code [ ] looks in spec for extra details [ ] list who needs to be contacted for further information[ ] email manager estimate[ ] take a break...
Now you can start to get "little wins" even on something you don't really agree with / want to do. The goal now becomes to tick those damn boxes, not to implement some feature you don't agree with. It might seem strange to tick a box for something as simple as opening a program, but if that's the level you need for your motivation then that's OK. The reality is these check box's are just mental milestones for progression. What's really important is your ticking them though. If you find yourself for hours on end not doing the list, the list is wrong somehow. Perhaps you don't have small enough tasks. Perhaps the tasks are too hi level and need to be split into sub tasks on those. Just tick, tick, tick.
Try it, it might work for you, it might not. This sure helped me though! Good luck.
Ultimately, I chose the path of gritting my teeth and getting over it. During that phase, the code quality suffered a little, but I did not have to waste hours and hours of my life freezing on it. This phase lasted for a few months in some cases.
This is by no means a long term strategy - I accept it as part of any programmer's life and simply deal with it without being emotional about it as much as possible. I have been fortunate enough to get more exciting work than mundane stuff
What helps me most is finding a technical challenge that makes the feature interesting and fun to implement. This shouldn't be too hard, if you are free to design the feature technically. Hope that little hack helps you getting things done.
"Also I waste considerable amount of time trying to do things in the most readable, maintainable and simple way possible"
Motivation is tied to your attitude here as you are looking to do more 'interesting' work, whereas the task at hand looks boring. However the task at hand could be important for the company, so it is important to take trouble understand the big picture here. Most engineers (and I am one of them) are too self-centered to do this, and this can be debilitating.
It involves coming out of your shell, being proactive to talk to the business, product and other areas and see why these set of features that needs to get done has important implications.
At the end of the day, everything is about service. If you enhance your attitude to think more in a service-oriented way (it is not all about you), this changes your 'attitude profile', and in turn can boost your motivation factor by several orders. Suddenly what looked boring becomes very important. It may mean to be more pragmatic ( no ideological fixations on 'purity of code'), roll up your sleeves and get it done.
The valuable service to the customer, can lead into repeat business, which adds to the bottom line, and that later could mean more bonus for you, which you can use it up for that special time with your BF that you have been planning for a while.
Sometimes I have the impression that the younger don't know how to take it like a man. There is a difference between complaining and whining, guess which one makes a man miserable...
Reality is hard to change, but perception is easy. You can really improve your happiness by reworking your perception.
Take some distance and look at the big picture: as an Employee, your main concern is if the pay check cashes. Everything else is ultimately a problem for the business owners (professionals are pragmatic, not cynic).
If your vision does not align with management and you happens to be right, it is a lot more sad for the company than for you personally. It is not your baby - wish them good luck, do your side of the deal as well as you can and don't suffer over it. You have your startup, your own baby to look after.
Set yourself small very clear goals which you write down and where you commit yourself to finishing them in a given amount of time.
However, what your mind is telling you with the feelings you experience in my opinion is something along the lines of "Don't do this, it's not great".
So when you experience this very often, you need to change something in your life, or else you'll fall into depression because you have overcome your inner hesistation one time too often.
Don't take this as a scientifically accurate account, just my personal experience.
I've been there before, and had some periods of time at a previous position where it felt like every minute of the job was a struggle. Getting things started was the most difficult for me, but once they were started, I could get them done.
If this job is just to pay the bills, and is not critical for your career, then:* Work on autopilot. Do what is required of you, and use some of your time on the job to learn things that would advance your career. For example, for each 4 hours worked, allow yourself an hour of learning something new to advance your career.* Find outside activities that you look forward to each day. Don't let the job define who you are. If you do, it could crush you.* Since they value you, ask to work reduced hours if possible. The less time you need to commit to the job, the less likely you are to burn out.
However, I can't help but recommend that you stay on the look-out for a job that brings you satisfaction and challenges you to do your best everyday.
Your problem is not really knowing if you can change things. Or whether it's worthwhile to change things. Ultimately, you can't really know whether it's better to try to change things (communicating better, focusing more on design vs writing code faster, getting a new job), so you have to accept that.
So ... whatever you choose to do, you can't really beat yourself up over making a bad choice. It's a hard decision. Whether you stick with the job and try to change people's minds, do things the way you currently are (but without stressing so much), or find a new job is a difficult decision, but no choice really stands out as a clear winner (from the little you've said), so just pick one and go with it.
If you want a new job, go hit up linked-in.
If you want to do things the way you currently are, just accept that programmers "waste time" - there's a reason why competent programmers often only write 10 lines of code a day - it's not easy work.
You can try to communicate better, but really, some people just don't listen. Or maybe the managers don't have a choice - they either have managers or customers.
Finally, work harder on documenting / presenting your progress. It never hurts to write stuff up, and explain the decisions you're making or the technical reasons why progress is slow.
The quitting part, moving on to a new job is not an option for me as I am convinced that it is the same exact situation in most businesses around my area.
I started working on some personal projects which helps a lot, but does not solve my problem.
I find myself pushing to the last minute before the task at hand is due. The extra rush of adrenaline from the looming deadline gives me the kick I need to overcome the meaningless work I am about to do...
It's a good question though.
After analyzing requests I have issues with, I will setup a meeting to discuss what I think are the issues, and propose a better solution.
If they push it off as "This is what the customer (or some other decision maker) wanted", I ask if we know if they have considered the issues and if we can propose alternatives.
If they still want to move forward, I ask or work with them to discover more detail about how it will be developed, and make sure they fully understand and explicitly acknowledge each piece I think is insane, irresponsible, or otherwise.
It usually doesn't get to that with good managers or clients. If it does, and it happens regularly, it's time to fire them and move on.
What does this mean?
Well, if they assign you a vague task, you get clearer about it, you ask them why they want to do it, what the objective is. A lot of the time, you could be wrong, and with their objective it makes sense. A lot of the time you'll be right. The best way to show it is to mock it up, and explain your thinking on why it's wrong.
The biggest killer is when you feel like a code monkey, it's usually not the work.
How do I handle it? I say my piece, I listen to the response from my boss. If he disagrees with my analysis, then I accept it, sit down and do the work to the best of my ability.
That is, if I see a project as someone else's, and my job is to help them do their best, I am happier than if I see a project as "mine" and other people are just screwing it up.
Like many important life lessons, I learned this one a day too late.
I've made about 10 cups of tea, gone to the toilet about 6 times, read every tweet tweeted in the past 24 hours. Started three arguments, considered quitting and storming out... it's horrible and I'm glad you posted this because I've been going through exactly the same thing.
I am not mocking your situation. If it's really bad for you, follow jblow's advice. But if it's a once in a while demotivation, swallow the pain and go on. You will reach greater heights and from there these menial times won't matter.
Just my two cents.
I've also found focusing on tests helps. Write as many tests as possible - focusing on getting those to pass. In theory, by the time you're done, the feature will be to.
As developers, this problem isn't going away any time soon. Our options are basically to create our own thing and be our own boss so there is no management to frustrate us, or just give in, write the code, take the check, and enjoy our lives outside of work. It's that simple, but it's also quite liberating when you allow yourself to accept it.
When I am asked to do what is not rational, I refuse and give argument. But to play this card you have to be willing to pick up your coat and leave, not as a threat but as a last resort.
You say you're stuck there, but the reasons are not yours, they are someone else's. Get over that and your options open up.
But I think all of us sometimes struggle with sitting down and getting things done. When we have a bad day, it's because we struggled making decisions and didn't end up accomplishing very much in our own eyes. We're our own harshest critics.
One thing that I've realized (actually just in the last few days) is that you simply feel 10 times better at the end of the day if you write a lot of code, knock of tasks on the to-do list, and generally "get things done".
Knowing that diving in and doing hard things will make you feel good makes a huge difference for me. It's like "Ok, this might suck a little getting started, but it's what will actually make me feel good and happy." It's really easy to sit and think, or read the internet, but it's not a good feeling at the end of the day.
As far as wasting time, whenever I'm struggling coming up with an approach or solution to a problem, I start writing it down. It usually doesn't get too far just in my head. But if I map it out, write it out, I get back to working on it much faster. An inefficient solution that works gets you much closer to the final product than struggling to find that "perfect" solution right off the bat. Make it work, then optimize.
Similar - not coding though.
>>How do you get in the zone and get it done
I treat it as an optimization problem. Specifically because I have a problem with this too:
>>I waste considerable amount of time trying to do things in the most readable, maintainable and simple way possible
So I consciously aim to force that compromise between quality & time more towards the time side. That goes against my fundamental nature, but I've come to the conclusion that I must learn this...and as a result it feels more like a learning & personal development challenge rather than me doing something I don't want.
however i feel inclined to reserve that for serious problems, like weak leadership, oppressive or immoral behaviour etc. rather than poor features or undesirable work...
doing things you don't want to do is part of work. letting your leaders make their mistakes and learn from it is part of it too. i'm strongly inclined to say you just need to grow up a bit and get on with it... and be grateful that this is a 'problem' for you because its nothing compared to what most people consider to a problem in the workplace.
That is not to say you shouldn't be proud of the workmanship of what you build (not quite the same thing as being proud of the product).
Unless you have a position where you have design authority, stop worrying about the why, and focus on the workmanship. Impress those that do have this authority with how well you do with what you're given.
If you believe that you have insights into making a better end product, then learn to communicate those insights at the appropriate time (before they've made up their mind). Try to get ahead of the curve and propose your ideas.
Listen to music.
I never found the ability to rationalize a task I dislike. Instead, I find joy elsewhere and try to preserve that feeling as I tackle the task.
I can completely identify with some of the points made, my particular frustration is working with appalling specifications that are 9 times out of 10 incorrect/incomplete quiet often leading to features being written multiple times. It's demoralizing. I have no particular solution, some will say just knuckle down but it's easier said than done, there are some tasks that just can't be made interesting. Unlike the OP I can change job and am, next week.
It's good that you are getting your job done, but it seems that you are still having issues setting aside your personal feelings and emotions. This is pretty normal for inexperienced developers. It's something you should focus on working on.
Here's how I developed that skill:
1) Remind myself that this is not my company or my project. It's someone else's. There's no reason for me to feel so personally invested in the project as a whole. If I've voiced my concerns and thoughts and been overruled, then my job is to get what is asked of me done to the best of my ability.
2) Have side projects that ARE personal and that I CAN be emotionally invested in. When you have a side project where you do call the shots and it's done 100% the way you want, you will find it is easier to not be so emotional over your day job.
3) Lastly, I have found that as I get more experienced and better at explaining myself, situations where managers overrule me and tell me to do something that is against my own recommendation become more and more rare (they'll still happen sometimes as long as someone above you can make unilateral decisions, so never expect it to fully go away.)
It's good that you've recognized your situation needs to change. Best of luck.
2) Challenge yourself to finish the project as quickly as possible. If a realistic estimate is that the work will take 1 week then try to finish it in 1-2 days. If it is awful work, try to get it over as quickly as possible. It helps if you can find an existing solution that you can use as a starting point.
3) If you're paid hourly, you might consider outsourcing the problem to someone off of elance. You should reframe the problem so that it doesn't require you to share any info (source code etc) from your employer with the person you outsource to. Ideally, ask the person to create an open source project on github.
- Eliminate ambiguous requests. Can you probe for your managers stated/unstated objections & needs?
- What's the expected outcome? Are your recommendations easily understood and compelling? Is your business case sound?
- If the managers are happy with schlock work, can you ever be OK with that?
Ultimately, the power is yours.
"Do you wrestle with dreams?Do you contend with shadows?Do you move in a kind of sleep?Time has slipped away.Your life is stolen.You tarried with trifles,victim of your folly."
Life is short. It is time to see through the trap you have woven around yourself and move along. Just do it constructively so that in the end, EVERYONES interests will be better served.
I have been doing sole crushing work for years in school. When you don't have a choice, the most useful thing for me to get started is the pomodoro method. Spend just 25 minutes of agonizing work and plan what you want to do for the 5 minute break. Usually after 1 or 2 cycles I actually get focused and motivated enough to make some progress.
I believe that most of our jobs can be divided to two parts:
-the fun part (interesting/fun/profitable work)
-the shit part (boring tasks/emails)
So, just get the shit work done when it needs to.
...anything other than the task at hand, obviously. :-)
Whatever the reason you are feeling depressed with your current situation (already lots of good suggestions in this thread), feeling guilty about wasting time or cheating your managers is basically a form of inflicting self-harm on top of everything else.
You're getting paid for whatever you do, and apparently the people that pay you are happy with the results even if you aren't, so just put that aside and focus on what makes you happy.
No, seriously. I go work somewhere where people can see my monitor. Helps me keep out of Facebook, etc.
Ultimately, I ended up at another definition of that word: "Spent".
I'm just saying...
Every time I've reached that point that you have described, I've quit. It was the best thing for me every time, too. There is no point wasting your time doing something you don't want to do, especially if it's for someone you care about. You'll just do a shitty job and you don't want to dump shitty jobs on people you care about.
Is it just that the work is boring, or are you being asked to do unethical things? I mean, either way, I would quit, but if it's anything unethical I would urge you to run as fast as possible.
However, if it's just "boring" work, perhaps recasting it in a different light might help. Look at it as a game of seeing how many you can finish in a single week. Stop worrying about doing the "best" job on it. If the project is so boring to you, then you probably shouldn't care so much about the quality of it. Just dump out some garbage, get the checkboxes filled, see how much you can get away with. Make it a learning experience, a chance to test your boundaries.
And, if you can't change jobs, then consider coming up with a side project. It doesn't have to be commercial, or even of particularly general application; even if you're just scratching an itch of your own, it'll give you scope to exercise the agency whose absence in your day job is giving you fits.
But it's in your head. Using simple tricks you can change how your mind interprets the thing, and put yourself ina more receptive state to be able to accomplish the task without it seeming like a battle of wills.
First, put yourself in a good mood. Listen to your favorite music, eat or drink something pleasant, think about the fun things you'll be doing soon. But whatever you do, don't villify the work or think "I can't wait for this to be over!"; that's just more avoidance.
Once you're in a better mood, walk through the work in your head so you understand everything you need to do, and estimate the time it will take, but shorter. Try to find something positive about it to work towards, or something good or interesting you want to see come out of it. It could be something as simple as timing how long it takes for you to write five methods. To prevent further avoidance behavior, remove your watch and hide your clock. If you can, move to a quiet place where you can focus with the least distractions possible.
At the end of the day, if you really don't enjoy your job, you probably need a different one. But it's a mistake to confuse a bad job with an unwillingness to do work you don't agree with. Consider yourself their savior, and do it in the best way possible so that it minimizes their crappy decisions and emphasizes your skills. Imagine you are a woodworker; maybe you didn't want to build a cabinet today, but you're going to build the best god damn cabinet those jerks have ever seen.
(Also: consider if you will be with this BF in five years and whether wasting this part of your life will have been worth it. Kind of a crappy thing to imagine, but you can't spend your life doing things you don't like just because it makes someone else happy)
Always think of yourself as an explorer collecting and connecting clues on a mysterious adventure!
Keep in mind, business drives programming, not the opposite. The codebase is only worthy as long as the product is selling (with the help of your managers).
There is no solution within your reach for management that is ignorant with respect to your job. Stop putting forth extra effort that will ultimately be wasted. Clearly, you have discovered serendipitously that no one can tell the difference between you doing your job well and you doing your job poorly. So stop trying. Just relax and do the first thing that could possibly work. Really build up some technical debt. Management probably does not even know what that is.
That way, you can use the ever-increasing bogosity of the code base as an argument for being resource constrained. Lobby for junior employees that report directly to you. The end goal is to set yourself up for a job hop into a better position at a better company.
The one you are working for now can be definitively marked as a dead end. So milk them for cash and emotionally disengage. Get your spiritual fulfillment by investing your creative talent elsewhere. Meanwhile, coast until you can bail out safely.
That's about what I'm doing at my crappy, soul-crushing job.
I have responded to two people from this thread and I thought I should make it publicly available to help others who might be out there.
At some point you owe money to the IRS. You've filed the tax returns, you've wrestled with the IRS about waiving penalties, and there is a number. You're looking at it, and it's big.
This is what tax lawyers call "collections work." You owe money, and the IRS is trying to collect. As I noted in my previous comment, the Internal Revenue Manual is the operating procedure manual for Revenue Agents in handling collection of taxes owed. Plus of course there are shards of wisdom here and there that are important to know. Some are published by the IRS (they have an assortment of published documents, like things called 'Revenue Procedures') but some of this wisdom is informal, learned through experience with the system.
The work is time and paper intensive. Going to a tax lawyer is probably not cost-effective, because the hourly rates are too high, and you don't have money. So you need help. Where do you go?
Well, call tax lawyers, accountants, and (most importantly) Enrolled Agents. Enrolled Agents are regular people who pass an exam administered by the IRS that enables them to represent taxpayers in tax controversies.
The particular type of human I would look for is an ex-IRS employee who has left government work and set up shop as an Enrolled Agent. You now have the best of both worlds: someone who knows the inside baseball game, and is out here in the real world, working for you. Also, the costs are likely to be more reasonable that an attorney or CPA.
Look particularly for an Enrolled Agent who specializes in collections work. Buzzwords include "offer in compromise", "Lien", etc.
In the case of the two people who contacted me directly, I pointed them to John Knight in Southern California. His website is www.knight-ea.com (don't judge him by his website) [EDIT: thanks 'dewey for pointing out that it is really www.johnknight-ea.com] and he fits the criteria I mentioned. He gets frequent referrals from the top tax lawyers here in Los Angeles. (I know, because I talk to my colleagues.) I send him 100% of my collections problems.
I am not competent to give advice on exactly what to do in this area -- if you owe a ton and need to figure out what to do. I would recommend that you stay away from any tax law firm that advertises heavily on the traditional media. There are no miracles, but the "One Day at a Time" mantra will carry you through. You will, eventually, be (tax) debt free.
Again, anyone else out there -- if you're in this boat shoot me an email. But now you know what you'll get when you email me. :-)
I will put you in touch with someone who is good at this.
Appeal to authority: I am a tax lawyer.
Knowing what I know about affiliates, it's at least possible on the outside that you might not have had the world's most businesslike records. Can you reconstruct better records, at least for the major expenses for the business? If so, you can have your CPA file amended returns. You'll still be looking at principal and interest for your taxes but it's in your interests to pay principal of $80k and interest versus principal of $100k and interest.
Where did the money go? Did you turn it into assets? If so then you may want to simply sell all or part of what you have.
If you did not turn your income into assets but it has all burned up see what you can do in terms of documenting your business related costs over that time. Conditional on the IRS agreeing with all this you could then make them a proposal on how much you'll pay month-to-month.
If you feel that that is not going to be a possibility you might end up having to declare bankruptcy. That's a real pain in the ass, but if you have no assets and no income that's probably where you're headed. If you have assets or income then likely you can make a deal. If you have assets that are somehow worth something to a bank you could possibly use these as collateral for a loan.
Best of luck!
I had one really good year as a freelancer and wound up spending the money I'd put aside for taxes because a client who had been paying me a retainer suddenly cut me loose right in November (the absolute worst time to try to pick up work as a freelancer). I was burned out and depressed about losing the gig so I didn't work for almost 8 months and wound up burning through the $30k I had set aside for taxes. I missed filing my taxes or an extension and the penalties just mounted until eventually my bill came out to about $40k.
After "negotiating" with the IRS (complete bullshit, they tell you how its going to be and you just have to deal) They decided that I could pay $2k a month on a $80k salary (how insane is that?). I lucked out and got a job that paid me almost double about 3 months later, if not for that I'd be toast.
Its easily the most stressful thing that has ever happened to me. Tax Lawyers were rude and dismissive ("Maybe get a cheaper car?" said one) once they realized I wasn't Mr Moneybags. And nobody can or will loan you that kind of money.
The only thing I can offer up apart from the Offer in compromise is that once you get the bill under $25k. You can negotiate directly with the people you talk to on the phone, once your bill is over that, everything they say/offer you has to go to some faceless manager somewhere, and it can be rejected and ridiculous alternative unilaterally offered back to you.
Typically the IRS can set you up with a payment plan that's a portion of your income. Its time to find a tax lawyer, not a CPA about this. Settlement/compromise, installment plan over a long term, and even bankruptcy are options.
Charles Markham: http://www.markhamandcompany.com/
His website is terrible and he screens his phone calls ruthlessly. Don't let either of those things put you off; he's worth it. Feel free to use my name or not; it won't get you (nor me) anything. Maybe it will get him to pick up the phone the first time...
My email is in my profile, but most of what I'm going to tell you is above: call Charles. :)
PS: Yes, you probably are a little screwed for the coming few years until you get this cleared up. It is a very good feeling once you emerge from the other side, having caught up on filing, and having cleared up the IRS debts. This is money that you owe; you lived beyond your actual means for a while. It's going to suck a while, but assuming you have your health and earning power, you'll get out of it and it's bright on the other side.
I think the last step for you is the Offer In Compromise - in simple form you'll show them how much your net worth is, and give it to them. In return they'll retire your tax debt. Obviously, it's going to depend on how much you are worth/vs owe, and if they think you operated in good faith or not.You need to not be in bankruptcy, and current on all filings to offer it. They also will come down HARD on you if you miss any filings/payments for 5 years after.
Note: be sure you file your taxes. You legally have to file, whether you can pay or not.
Once you file, after two years the debt can be part of a bankruptcy, but you have to keep filing.
As you know, this is a really sucky spot to be in. I believe the IRS has a program for people who have no chance of repaying -- not sure what the title is. It's worth looking into.
You did a brave thing coming online with this. I imagine a lot of folks would just call you names and be done with it. Speaking for other guys in the same situation, thank you.
I promise you I am not the accountant himself :) and this is not a spam comment. He can help!
- Move to a country without an extradition treaty with the US.
- Change your identity. I don't imagine they'll put that much effort into hunting you down for just $100k.
- Create a Kickstarter campaign.
- Ebay the next 2 years of life. That way you are only in hock for 2 years, not 5.
- Marry someone and don't tell them about the debt until it's too late.
Also I was pretty happy with the domain name :)
1. Look for community ie: mailing list, irc, im, github, etc, etc
2. Look at commit frequency. How often do they commit. Is the project abandoned?
3. See if the developers are friendly. Feel free to email / im / chat with the developers. Ask what you can do to help.
Keep in mind contributing does not mean code code code. It can mean triaging bugs, updating documentation, herding other community members towards the right things, etc.
Hit me up with more questions if you want: firstname.lastname@example.org
(1) Only on HN would anyone dream of referring to your list as "everything". You are actually targeting a very narrow, focused skill set: those required for a small(-ish) software or software-intensive business. Like it or not, you're proposing becoming a specialist (albeit with a somewhat broader specialty than a typical job description would call for).
(2) In the real world, "everything" includes many, many other things. To get good at all that stuff on your list, you'll need to leave other skills by the wayside. The comment by taprun mentions chess, running, and cooking. You won't be getting better at any of those.
(3) The I-do-everything approach sets a hard limit on the size of a business. An important reason for hiring & delegating is so that a business can grow.
I remember meeting someone who was fantastic at chess. He destroyed me. Repeatedly. My mental model of him was essentially "me but good at chess". It didn't occur to me until much later that he didn't know how to program a computer, couldn't run a mile without stopping and didn't know how to cook Chinese food.
I think if you stop seeing people as "you but can do X", these feelings will go away. Alternatively, read up on the concept of "comparative advantage" and realize there is a mathematically proven reason not to try to be an expert at everything.
I used to be up to date in a lot of domains. 3D modelling, app frameworks, web technologies, back end, front end. Those days, I find it's hard enough to focus on being up to date and relevant with front end web development while balancing an healthy life with friends and family.
You can do it, but remember that there is an upkeep to being relevant in a lot of domains. If you can deal with it, sure, go ahead!
However, what I would recommend you is a good team. I'm finding I connect easily with people that have complementary skill sets to mine, and it's a great experience.
That will give you an automatic prioritization of how to go about getting these skills without becoming overwhelmed.
"Unix" is an operating system that came out of Bell Labs long ago. It has had many imitators, any of which might be loosely called "Unix". The imitators include the various flavors of Linux. MacOS X has one buried inside it. Windows is something rather different.
The program that runs in a console window is called a "shell". So a "shell" is a kind of program. Modern shells include lots of fancy functionality, which varies from one shell to another. But their basic operation is the same: type the name of a program, and the program gets executed.
Most shells from the Unix tradition have names ending in "sh" (guess why). Bash is one of these. Other popular shells include zsh, ksh, and tcsh. Bash is by far the most popular these days. It is the default shell run by console.app in MacOS X. It is also the default shell in many Linux distributions.
Windows, as usual, is different.
So, typing the same commands into a shell in Linux vs. MacOS will likely get you similar results. Differences might be due to configuration that differs from one system to another, and programs that are installed on one system, but not on another. Typing these same commands on Windows will probably get you completely different results.
As for "language": we usually don't use this term when referring to directly typed console commands. Most modern shells do include a programming language whose syntax is based on the command-prompt syntax. So a shell doubles as an interpreter for its built-in language.
Your confusions are well-founded. This is a very vast topic.
"To single out one record, look it up with "xxx", where xxx is one of the of the records displayed above. If the records are the same, look them up with "=xxx" to receive a full display for each record."
Also, for a semantic search engine I was working on, we needed to add categories for various articles. We used Mechanical Turk for this.
Submissions start April 1st each year. There's a maximum ("cap") and they typically "run out" for the year in several weeks/months. See this page for dates in the past (scroll down) - http://www.h1base.com/visa/work/h1bvisacaph1bquotasystem/ref...
Please note: education and expertise matter a lot. If you do not have a masters degree your chances are much smaller. Good luck.
The tough part is just getting the H1B visa since you must have a companyhere sponsor you to get it. This is why the monthly "Who's Hiring" submissionhere on HN requests that posters declare whether H1B's are welcome.
As youtube already captured the desktop video streaming and most of the mobiles, a possibility will arise only if a new platform awaits.. like VR, or IoT.., these things would give an early bird ticket for the competition arena..
And, i am slightly eyeing on the possibilities for a Video streaming services in IoT field., Say for example, streaming vids in your fridge, roof, doors or whatever..
There will be somesite, someday that will takedown youtube.
"Reputable" is a loaded term in the infosec world. There are a lot of "reputable" incompetents.
from http://www.aftonbladet.se/nyheter/article18915221.ab via google translate)
The Digital Ocean status page  claims that "Preliminary investigation indicates that Telias Transatlantic cable are down." which would make sense, because my ISP is Telia and I can't connect to most of the internet.
Edit: Well, this outage lasted a bit over an hour. Now at 20:55 UTC I can access everything once again.
Say if you wanted to upload/download a megabyte of data to a datacenter in the US using TCP with retries, would it work eventually with high probability?
Yet once I got back in the server (behind that indirection), the server couldn't even ping google, and its DNS was totally down.
Would've done a traceroute for fun if OVH's mirrors were reachable.
Connections to our US broker failed at 10pm (dst) on different servers (based in Germany) and i had no idea why, I already wanted to blame our hosting provider.
but I see the traceroutes failing after they make it to the US.
And if only bogus reforms happen, then they would be in a good position to leak Feinstein's phone calls from last week.
Maybe it was on purpose..
On the other hand, revealing classified information will send you to prison for decades. Depending on what you do for a living, it could even result in the death penalty. Best case scenario, you will spend the rest of your life living in a country with a government worse than your own, wondering when a member of the intelligence community is going to murder you.
The comparison really doesn't hold up.
Also, think of how badly this has damaged not only the U.S. government, but also the private sector. No company in its right mind, foreign or domestic, still wants their data to traverse networks from the United States. They might not be able to avoid it, but that's besides the point. By the time all is said and done, tens of billions, if not trillions of dollars in damages will have been done to the U.S. economy. The NSA's shenanigans have been the most detrimental thing to happen to the United States in at least a decade. Unfortunately, the government doesn't blame themselves, they blame Edward Snowden. And so you can be sure that billions of dollars and tens of thousands of man-hours are being dedicated to the task of closing any holes that allowed Snowden to leave the country with large amounts of classified information.
And the original book,"Eichmann in Jerusalem: A Report on the Banality of Evil" in PDF -
If I were making the choice again today, it would be Gumroad by a country mile. Regardless of whether you end up using them, look up Ryan Delk's presentations regarding the habits of successful sellers (multi-tier products; X 2.2X 5X pricing; email marketing). They'll make you much more successful than the typical person who just throws a $FOO onto the Internet.
I like the design. I like the simplicity. People can just use their CC like normal. They take a percentage of your sales, but so far found it worth it.
I wish it had order tracking (just a box I could tick when I shipped something would be nice) but that is irrelevant for downloads.
Just sell things, enough things that it actually matters who you are using for processing. But, with 0 sales, you are doing 0 order processing so it doesn't matter.
Flat monthly fee. Their admin UI is clunky, their checkout pages are basic but functional, but they solve a number of problems* without asking for a percentage cut of sales.
I think for basic stuff they work just fine. I'm just selling one ebook and I just wasn't comfortable with having a cut of my sales taken AND my funds being withheld by a third party before some weekly or monthly remittance. With e-junkie the funds go straight to my PayPal account where I can use the money immediately (I constantly pay for things via PayPal).
*obfuscating download path, handling coupons, handling multiple downloads etc
Let's me sell a per year license with an optional reduced renewal fee at the end of the year, which most services don't seem to easily offer. Also then lets me ties into other things like support forum membership.
It's bitcoin only though but I like the preview for music and the no-bullshit easy handling.
That sounds kind of like Italy. Maybe not as much sunshine as California here up north, but it's certainly better than the UK or Belgium from that point of view.
Of course, the economy is in the tank, but maybe you can work remotely or something.
Going to the US is not easy: you'll have to find a company willing to hire you.
That said, if it's what you want, don't let the naysayers get in your way - go on a vacation there, travel around some, meet people, see what day to day life is like, and then go for it! It's not perfect, but there's a lot of good stuff there - much more than some of the haters here give it credit for.
Some people work crazy hours, many people don't. As someone who is likely to have a good job, you'll have decent health care, even if the system is a bit screwy.
Edit: a few other places to check out might be:
* Colorado (Boulder, Denver, Ft. Collins). Snowy, but still quite a bit of sun. If I ever went back to the US, this is high on my list of places to check out.
* Austin, Texas. I don't know much about it, but it's supposed to be a nice place, and definitely sunny/hot.
* Bend or Ashland in Oregon. Not as sunny as California, and cold in the winters. Not as many jobs either, but nice smallish towns.
I am a European. I lived in US for two years, I lived in Canada for 15. I also lived in Sweden and Japan. States are good because it's just one big Walmart - everything is ridiculously cheap, but what it gets in quantity it tends to lose in quality. Canada in this respect is somewhat better, but it has the same problem - it feels ... I don't know ... diluted? Too much stuff, too little substance. It is nice, it is comfortable and affordable, but - and I am dumbing it down considerably - you can't get a decent croissant, because nobody simply gives a shit about getting them right.
On the other hand, the grass is always greener on the other side. If you move, you will have at least a couple of years of excitement and novelty.
PS. And generally working too much and not enjoying life is in fact the biggest lifestyle issue in States and Canada. No better manifested by the fact that most of the restaurants are there for eating and not for socializing.
You will and you'll also have the chance to discover the difference between excess and moderation.
> lots of affordable fresh food
The food is either affordable or good.
> live in a house with garden
More like a house with a mandatory lawn in a region hit by a very serious drought. You might also want to ask about the rules imposed by the homeowners association and whoever rents you the house.
> beautiful nature close enough to actually go camping for the weekends
Yes, if you like deserts and you want to live in SoCal. Note that "close" has a different meaning on that side of the pond.
> friendly and approachable people
Maybe at first. With time you realize that the friendliness is a form of politeness that hides fear, distrust and greed.
Like others said below, a good idea would be to come live in the US for, say, a summer or so under a short-term tourist or student visa (eg maybe for a career-related summer course or unpaid internship) and see for yourself.
If you plan on being near either Bay Area or the greater Los Angeles area, you have to be ready for the housing prices. A good, safe area with good schools will cost you. A short commute on top of that will cost you double.
That said, if you do your research, you can find very solid public schools (school districts) and University is doable, unless you go private.
As far as neighbors, it's a mixed bag - there are plenty of great people and there also many fake, greedy, etc. Just like any big city. Culturally, Americans seem to be more predisposed to welcoming people than not.
Back to the finances, with the costs of housing, it's not likely that you will be able to be the sole breadwinner. I've been trying to solve this puzzle for a while, but on a single income things just don't pencil...
Now the upside - California lifestyle is something else. You have all 4 seasons at your disposal with only a drive or a short flight year round. This opens up a lot of possibilities for enjoying nature/sports. If you are more into just quiet enjoyment, the state offers magnificent areas like Big Sur, that are also surrounded by awesome hotels, camping grounds and wine country. California wine is great and very inexpensive.
You also have the beach (really cold water though) and great weather most days out of the year.
Downside of Los Angeles is traffic and lack of public transit. In SF, you trade public transit for huge cost of living increase.
Never having lived in Belgium, I can't compare. My only experience has been a very short (6 months) stint in the UK and Moscow. I would not come back to either voluntarily after California.
If you are not afraid of a little rain, I would strongly recommend you consider Seattle - reasonable weather (I like rain) and not too much cold, great nature and friendly people (by my standards of visiting and working with a few great folks), no state income tax (CA works out to an extra 10% for me), a lot lower cost of living with similar level of education offered by the local school system.
Plan a holiday to the US, look things over and then make a budget (emigration is far from cheap), save and then decide to back out or bite the bullet. Don't do anything permanent until your visa is in the bag for you, your spouse and your child. Hollywood and anecdotes are not good inputs to a life determining decision like this, consider it a huge project and devote resources accordingly.
Why is Belgium disappointing you?
The US is definitely not paradise but it may give you chances that are hard to replicate elsewhere. At the same time, I know plenty of people that are successful in the EU. It usually boils down to the people, not the place.
I would suggest checking out areas such as Redding, CA. If you make over $100k a year you could get yourself setup with a nice place such as the link below.
More properties in that area:http://sacramento.craigslist.org/search/rea?query=acre&sale_...
Note: Life can be wonderful in the USA but our healthcare and education system need work. Healthcare is fantastic if you get good insurance, but that will cost you each month. Being a programmer, it is likely your employer will provide health insurance. Our Universities are some of the best in the world (ex. MIT, Harvard, Stanford, Yale, Carnegie Mellon, etc), but our elementary and high school education system is inefficient so you may want to consider one of the many private school options in your area. This too will be costly. Basically expect to pay 10-15% of your salary towards making up for our deficiencies in these areas. Work/life balance is entirely possible here although many European countries structure their national policies around promoting such ideas while the USA pretty much leaves it up to the individual to organize their life in the way they see fit. This is why we have so many people living on the extremes, from super-star entrepreneurs to homeless individuals and everyone else in-between.
Salaries will be higher in the US but without a doubt you will lose in term of vacations and free time. Everything you wife mention, you can have in Europe. Food wise, I think you're better off in Europe if you like fresh inexpensive food.
The nature on the west coast is incredible. The national parks there are among the most impressive places I've seen. However, with 2 weeks vacations, you may not have much time to visit them. You can't really go to the grand canyon for a weekend for instance. You'll have more time to go there on vacation while you work in Europe!
1. What's the best place in the U.S. to live and work cheaply?https://news.ycombinator.com/item?id=6702111
2. What's the best place in Europe to live and work cheaply?https://news.ycombinator.com/item?id=6703058
3. Where can I move cheaply to work by myself for a year?https://news.ycombinator.com/item?id=6700531
4. A "Hacker's" Guide to the Bay Areahttp://islandofatlas.net/2013/10/04/a-hackers-guide-to-the-b...https://news.ycombinator.com/item?id=6502430
Are those 5 weeks of holiday paid? If so, that is not a common benefit in America.
Without citizenship, your healthcare coverage is likely to be either costly or limited.
Scholarships and grants exist, but a free ride through college is also rare.
If you were already a US citizen, this move would be possible (but even for the majority of Americans, what you ask for is off the table), but since you're not, I say move to Canada.
Specifically, Toronto. As metropolitan as any American city (with a sufficiently large job market), numerous strong immigrant communities, better healthcare, great food. Nice and clean, fairly safe - I'd have no qualms bringing up a kid there. The surrounding suburbs are very mellow.
Positives:- I was put into the german school system learning german almost like a 'native' and I still have it. (Massive positive)- Luckily I had 2 brothers. We'd move somewhere new, clump up as a gang, then slowly get to know people and get our own set of friends.- I still find it easy to make friends.
Negatives:- Become good friends with somebody, move on. - Making new friends all the time.- I found my memories of Germany 3-10 better than the USA (10-12) but in Germany we were thrown on to our bikes and rode off into the countryside for the day (we lived in villages). In the USA we were driven everywhere although we did have a pool (Florida).- When we finally came back to the UK I found it slightly odd. Culturally I'd missed out on a lot.
Schools were much of a muchness. Of note we were in public school and then quickly moved to private school in the USA (this was 1980).
> My wife keeps saying we should move to US, perhaps California. She thinks we'll finally have some sunshine, lots of affordable fresh food, perhaps live in a house with garden, beautiful nature close enough to actually go camping for the weekends, and friendly and approachable people
Sure, if you lived in Nor Cal, somewhere close to Marin or in the East Bay, you could probably get that. It is kind of puzzling to me that you would go all the way to America for this though. Wouldn't you prefer to live in the EU closer to a community ?
> 40h workweek 5 weeks of holiday a year free/cheap health insurance free/cheap education up to university level for our daughter.
You are not going to get a 40 hour work week in America. It might be close to 60 hours. At least 50. Again, depends on the place. If you work for a big company like Google, things will be reasonably. Early stage startup. Miserable. Vacation is 2 weeks - 4 weeks. Health insurance has always been paid for me by my employer. Schools, I can't comment. I don't have offspring.
Someone mentioned other regions. Let me give you a quick run through considering that long term, America is my home but I don't know whether I want to live in a city.
Austin, Texas. Too small, too hot. Still too Texan.
New York. I love NYC. But it is not what your wife would want. It is a Megapolis.
Colorado. I fucking love Colorado. Boulder is amazing, it is a great college town with all those beautiful girls. Great opportunities for hiking. It has a great and upcoming tech scene. Honestly, if I were ever to buy a summer home or move elsewhere in the U.S., it would be Colorado.
The cost of living, job opportunities, weather, and life style varies dramatically from San Diego, Los Angeles, Bakersfield, Sacremento, and San Francisco.
I'd recommend a trip to see. That said, California is the last place I'd move if I were a tech worker right now. You can get many of the same benefits (except possible access to VC money) in lots of other places. The Research Triangle NC and Austin TX for instance both offer much of what you are asking for at a much more affordable price.
One thing about vacations in US is that no matter how much time one gets on paper, I found the company cultures to look down on taking time off. It's almost like people are ashamed to take their vacation time.
In the end, I decided against it. At the (2-day) job interview, people who worked there pointed out that the biggest benefit over Europe was the perceived freedom, the feeling that noone would bother them about their private business (this is probably no longer the case / general feeling today). I found the poverty in urban areas most shocking (loitering people, obvious racial inequality).
In the end it boils down to whether having your "dream job" (for me it was game programming) is worth both getting ripped out of your surroundings and coping with lower standards in many areas in the US over Europe (well, depends on whether you live in a poor EU country), as well as other issues like the harsher environment (floods, earthquakes). 50-60 hours was a given in the 90's, perhaps it is no longer the case now that Google/FB set the bar higher for job quality. For me it was better to stay, although nowdays I sometimes ponder moving to Switzerland, Norway or perhaps Australia (for different reasons, none involving career perspectives).
- The most important thing for me: EU states are social states and US is not.
- You are not going to get a free health insurance or cheap but quality education for your daughter like in Europe. (Not saying she won't get quality education, just saying it won't be cheap as we are used to in Europe.)
- US is not a developer's paradise but it's a paradise of possibilities and opportunities.
- http://www.zillow.com/homes/for_sale/CA/house,condo,mobile,l... In that link there is a list of houses with a garden that you can buy to give you the idea. For the places that you would think you could afford, there is a possibility of living without a job. (Find remote work and it all works out?) But I think they are better houses than houses in most of the Europe.
- You can think of Austin, Boston or Chicago instead of California cities.
- Wait, there's another possibility: You can move to Berlin, Vienna, Istanbul, Mugla, Izmir or Aydin. You'd work remotely most of the time except for Istanbul, Berlin and Vienna.
- Food in Europe is a lot better than in the US and by food I mean real food, not the cereals, cookies or things they eat thinking they're having breakfast. :) (At least in SF)
- I tend to think that startups are not for people that are married and with children. They are demanding and consuming. Unless it's your own because only then it'd be worth to your efforts and time. We all know that.
Wish you all the luck for whatever you decide and let me tell you one more thing. You should absolutely be grateful for the wife of yours. Mine is not moving a centimetre..
You don't get sunshine everywhere in California.
I personally hated the weather in San Francisco, but a bit to the south (Mountain View) is already much nicer.
Now I'll go through your requirements:
40h workweek: Yes easy to find
5 weeks of holiday a year: That is almost impossible to find in my experience, except if you are willing to get 3 weeks out of your pocket. (meaning you are actually deducting your pay)
free/cheap health insurance: Find a company with health insurance, and then you should be able to have one for your family, and only pay an extra of 200 to 600$ / month (yes that is cheap in the US)
free/cheap education up to university level for our daughter: that's not possible, you will have to pay for college. I think you can get one cheaper if you live more than 6 months in that state, and then send your daughter to a state college. Here is an example of a university near me (starts at 4000$ / year):
It looks like the days of Google et. al. recruiting from far-afield are over, unless you're CTO of an early-stage startup someone like Google might buy, or at least have some kick-ass side projects you can point to that will make you irresistibly attractive enough for someone to deal with all of the associated immigration headache, perhaps being better / worse off from a lifestyle perspective is a bit of a moot point?
Sorry to be a downer but... cart before horse, etc. etc.
We choose between USA, Netherlands, Germany, Norway, Switzerland, Canada, Australia and New Zealand.
I'm not a well-known software engineer, not an outstanding genius (yes, I'm not very confident about my skills) - that is why it seems very difficult for me to get a job outside Russia.
But I love programming, I try to learn something new every day, improve my skills and knowledge. And I hope we will get out someday (hope dies last :) ).
I wish you good luck - don't worry, everything would be alright!
This raises a bit of red flag, because lots of people migrate with a vague idea of "the grass is greener" without knowing what they're getting into. Since Belgium is not a bad place to live, I'm wondering what it is you're running away from.
And since you put a work/life balance, cheap health insurance and cheap education top of your priorities (all things Belgium already offers) and don't seem to know very much about the US, I wonder why you're not considering the much less complicated and safer option of another EU country? (Also, of all continental European countries, Belgium is probably most like the UK with it's post-industrial similarities.)
What is it that makes you think you and your family be happy in the US?
I'm getting a strong sense you don't really have a clear picture of that, and are just looking to flee to a magical land far away from your current troubles. I live in a place with lots of expats, and that scenario usually doesn't work out well.
* 40h workweek
* 5 weeks of holiday a year
* free/cheap health insurance
* free/cheap education up to university level for our daughter.
You said you are EU citizens. It's ok for you moving around EU but moving to the US is going to create immigration problems for you.
One of you will need to get sponsored for a long-term working visa not the temporary one. Then still I think according to US laws your Wife won't be able to work until you get a Green Card. I heard that they are trying to change that law but still.
Sorry to break it down to you like that, you can still try and make it, but its not an easy thing to move to the States especially having a family with you.
I'd suggest you apply to 20 companies+ and try schedule them all within a week. So you and your family can go there for a week do your interviews and see if you can get someone to sponsor you.
It's not like you said I am just going to move there... If you say that to the officers in the airport asking you the reason for your visit they are definitely not going to let you in.
Ideally, a potential mentee:-- Wants to code her or his own small search engine. Obviously, it is difficult to recreate Yandex or Google, but it is relatively easy to make something on a smaller scale. -- Knows some C++, but wants to expand her or his knowledge -- Is in the beginning of the software development career
This is just a description of someone who I can help the most. If you don't quite match this description, send me an email anyway -- I can still help you with your own project in C++ or help you code a search engine in a some other language than C++. Or maybe I can just help pairing you with someone more relevant. :)
Email: in profile.
Reach out to me if there's any way I can help: email@example.com
I guess it would be a good fit for a competent web developer who for some reasons wants to learn maths (I am about the opposite). My email is in my profile if someone is interested.
I'm in my late 30's so I have a lot of experience. I don't mind working with people who are younger , but 30 is about the cut off limit. My goal is to seed a lifestyle business that has the potential to grow very large. I'm more interested in a good fit between myself and the mentor than the mentor being extremely successful. However, you should have a track record that reflects a degree of successes. firstname.lastname@example.org
I'm looking to get started in about 2 months.
I am a Market Research Consultant (Data Analyst) so I could offer mentoring/advice for surveys or data analysis. I also am pretty handy at programming (python) and maths (early uni.)
Shoot me an email! email@example.com
I'm looking to learn interesting or advanced iOS (low level stuff, interesting UX concepts). Also interested in server side coding with Go.
If anyone would like mentoring of any of the above, id love to help!And if anyone knows about Node.js or databases, id certainly would be glad to learn. In return id teach or help in whatever i can.
Looking for a programming mentor to help me learn Python. Have some HTML, JS, & CSS experience but no backend knowledge. Email - firstname.lastname@example.org.
Email: in profile
There is a lot to say, and I"m not sure where to begin. But I was (as I wrote in my original story) one of the editors of the MIT student newspaper. We had a lot of fun, and some great computers. And every so often, someone would come by and ask to search through our archives.
Now, our "great computers" were Atex systems for typesetting and layout, based (I think) on PDPs of some sort. So to search through the archives meant loading a "disk pack," which is a laughably large hard disk that you had to put into the machine or take off of it. Just searching through the 100+ years of the newspaper's archives was a huge task.
At some point, we figured out how to get the information from Atex onto a more modern computer. And I set up the index, for my undergrad thesis, to be accessible on the Internet (not the Web). But the interface was clunky, and while it was better than before, the search was far from perfect.
So it was really great timing when Jeremy Hylton (now of Python/Google) went to that talk. We turned off my thesis software, turned on a Web site, and set up a simple search to work on our Web site. The thing is, while this was a great feature, there was one missing component -- users. So we actually took out large "house ads" (i.e., advertisements that the newspaper takes out itself, rather than selling to advertisers) telling people how to get a browser, what a URL was, how to enter the URL into a browser... all so that they could search the newspaper archives.
This was in early 1993, and I was still living in Boston at the time. A few months later, I went to a computer show, in which someone was showing off Web authoring tools. He asked who had a Web site, and I was the only one to raise my hand. I think that it just started at that point to become known among the technological elites, but the "elite" part meant that you had ever browsed the Web, not that you created sites yourself.
Another quick anecdote: When we set up the newspaper's Web site, we wanted people to be able to contact us. HTML forms had just been invented, as had the CGI protocol. So I hacked together a little program that took the contents of a form and sent it, via e-mail, to our administrators. I called it form-mail, and it was written in Perl, and all was great... until a few years later, when someone named "Matt" took it, removed my name, added his, took out all of the security features I had put in, and then made it famous as part of "Matt's Script Archive," which was the bane of Perl programmers' existence for years.
I seem to have lost the e-mail exchange that I had with him at the time, but when I told him that you cannot just remove someone else's name from GPL'ed code, he claimed to be scared, and then never did anything about it. Which is just as well, given that he so sullied the name of my program that I'm happy to give him the credit for all subsequent versions.
One last point: There wasn't any CGI.pm, or other Perl module to do Web stuff, back then. So I wrote my own code to decode data from POST-submitted forms. If you ever see the Perl code "for $pair in @pairs", then it's almost certainly copied from the code that I wrote in that first form-mail program, oh-so-many years ago.
Fun stuff, indeed!
We ended up writing a device driver for the DOS machines that could message other Lantastic nodes with the system's current status. Once we had the status stored back at the system controller, we needed a way to allow administrators, operators and teachers to easily see the overall status ... my initial choice was to provide the data via a web server since the system controller had a TCP/IP stack and was connected to "the outside world".
In 1995, what do you use to write a web server that has no static content? Tcl/Tk was one of the first scripting languages to include the ability to open a "server socket" and it provided lots of libraries that made it easy to template text (in this case text/html). We ended up with one summary page that displayed the status of the entire system and a detail page for each classroom. There were no graphics, system status was shown via text and colored backgrounds using in-line styles, and the server automatically redirected you to the index if you asked for a non-existent page.
Sadly, the system never made it to production as we found we also needed a web-based method for scheduling classes, provisioning users, etc. This system was written in (pre-Java) ColdFusion and the monitoring functions were migrated into that system.
This was long before the web had become a popular culture phenomenon: most people outside of academia didn't know what the internet was, and search engines were in their infancy (Alta Vista was founded that year). Windows 3.1 did not have a built-in TCP/IP stack, so you had to be a geek just to figure out how to connect your home machine to an ISP via a dial-up modem (Windows 95 made it much easier) and install a browser. However, the web was starting to catch on in the business world as companies started putting useful information on the web and their intranets. It was an exciting time to be working with that technology since the potential was largely untapped.
My first real web development project was an appointment scheduler. In 2000 a potential client wanted one but we couldn't license one from the only company that offered that kind of software at the time in Germany. Thus I taught myself PHP and MySQL and within a week I had a working prototype. Users could reserve appointments and admins could manage them.
The deal with the potential client fell through, though, but I continued working on the code. It was hard going because back in the day, there were no PHP frameworks (that I knew of) and no CSS frameworks.
It's been moderately successful and I still have happy customers from that time. I only wish I had done early on what I did two years ago: offer it as a hosted service (or SaaS, as it is now called).
One class was to make a website, which I didn't know the definition of at the time (being about 8 or 9 and living in a home without a computer).
* Macintosh LCs
* Macintosh 512k
* Lynx on the classic Macs
* Netscape on the LCs
* Pico for text editing
* Pine for email
* Fetch for uploading
We learned basic HTML which was enough for me to keep pushing toward development once my family finally bought a computer.
When I realized that I wasn't going back to college to finish because my business was doing so well I thought back to ARC and hunted down one of my old teachers to try to make a donation. I couldn't find the one who taught HTML so I reached out to the lady that taught us Logo Writer, but ARC had long been shut down so no dice.
For example, instead of an email signup, Show HN is for the thing you email people about once it's ready; instead of a fundraiser, Show HN is for what you build with the funds you raise; and so on.
We're planning to feature Show HNs on the site a lot more, since most people agree they're one of the best things here.
I personally appreciate people being upfront about it being promotional, StrongLoops latest "tutorials" have been a bit of a sinner in this regard. They usually provide great content but always mention their own services (which is fine in my opinion but it should be obvious from the get-go).
Edit: Perhaps the prefix is removed to remove any bias, perhaps people are inclined to be more positive towards user contributions - Perhaps by removing Show HN you let the product live on its own merit, rather than any type of emotional bias.
I've never seen any official rules or guidelines regarding "Show HN:"submissions, but there are differences in sorting between url-basedsubmissions and text-based submissions. Since text-based submissionssink faster, I've seen some suggest using url-based submissions. On theother hand, with a text-submission, you can specifically ask for whatyou want (design help, content help, ...) and provide contact info.
From the following, it seems some changes may be afoot.
https://news.ycombinator.com/item?id=7761378> We do intend to add a few things, such as a "show" link in the topbar for Show HNs
Here's an album with some screenshots from last year: http://imgur.com/a/ekoO2
If it is a website that you are unable to add multiple users to an organization with, LastPass has a password sharing feature that doesn't directly expose the password with people you share it with. Although if someone cares enough, they will be able to find it.
Any time an employee leaves a company, all shared passwords should be reset. It doesn't matter if it was an amicable departure or not.
Secrets: In a closed office, verbally.
edit: video demo https://www.youtube.com/watch?v=CITq80gf6Hk
Currently we use ssh keys to limit access to servers and code repositories so the perfect solution would allow passwords and such to be protected by similar means.
I believe gpg has a solution but I have not implemented it myself yet.
For passwords that can absolutely not be made user-specific, we use SimpleSafe (https://www.simplesafe.net/). It allows you to make groups of passwords and assign rights to those passwords, and has decent logging. It's web based and works ok on mobile.
These few passwords are for network devices, passwords for websites where only one account can be made, or master/root/administrator passwords that we don't use but need to write down somewhere just in case.
These are the keys to the kingdom, so it should be behind VPN/SSH, ideally completely isolated from your regular infrastructure, and with tested backup procedures.
(I'm one of the developers. It's a commercial SaaS service.)
Most of the external accounts (log analysis, analytics, CDN, etc) have individual accounts, no sharing necessary, up to the individual to maintain complexity and remember the password.
For other services, certificates and multiple authentication methods (2FA) works out nicely.
Personally I use 1Password for storing passwords and it allows sharing vaults between users so as my team grows we might actually consider using these.
Pros:1. Open source tool, you can run internally in your company. https://github.com/saravanacp/secureshareme2. Very secure: it encrypts the data in the browser and the key is stored in the URL anchortag which is not sent to server at any point of time. Only the sender and the receiver has access to the keys. 3. You can also opt to send a secondary verification code to receiver's mobile for two layers of security.4. Option to self distruct message based on time or if an attack is detected.
Cheap, effective and good security track record.
That being said, we use personal accounts for all external services. All personal passwords are stored in 1Password.
Passwords are designed to be human-interface memorized authentication tokens. Sharing it any other way than via human interaction just makes it a digital key, and real digital keys are much more secure than digital passwords. So share it via human medium, or rethink why you're using a password.
Non-Windows 8 specific : Eclipse has a full-screen plugin that I use to be free from distraction when working with code.
There's an Autohotkey script for making any window full-screen + borderless, too. It's great for focusing on one task :
Autohotkey can automate various other things like having keyboard shortcuts for Volume levels, opening applications, turning off Caps Lock, etc;
Powershell is extremely awesome; it's basically a c# console.
Chocolatey and/or OneGet, Boxstarter, and myget.
Notepad++ <i>and</i> Notepad2. I use both, notepad++ for complex replacement tasks, notepad2 as my simple editor.
Puretext which strips formatting from text when pasting.
Not sure if this is what you mean by "productivity tools," but these things greatly increase my productivity and reduce the time it takes for me to complete tasks.
The laptop doesn't really matter, but I hate doing any sort of development in windows, so I'd either buy a macbook (second choice) or get a Dell or something and install ubuntu or arch on it.
Both run archlinux with i3 as window manager so I usually don't really notice perforamnce issues on the netbook.
For an editor I was always a fan of vim but I recommend using what you are comfortable with. IDEs like Eclipse are nice but if performance is at a premium I recommend jsut sticking to an editor and a shell.
Version control i would recommend git.
The web is many orders of magnitude more accessible than most small museums, and in a potentially important sense people viewing your webpage are your visitors. It is likely that a significant fraction of the physical visitors have already been webpage visitors.
Now a little personal bias. If I'm in the museum, I didnt come to surf the intertubes. I don't really want to be in an environment where using cellphones is acceptable, let alone one which encourages it. Headphones and written guides don't intrude on other people. Cellphones do.
But that's just me of course. The reason I mention it is to suggest investigating what would improve the experience of the sort of people who actually visit your museum. Will it be enhanced by the web? Would money be better spent on physical objects or building infrastructure or display fixtures and lighting or staff or literature or scholarship or educational programs?
How many guided tours does creating an In museum digital experience cost and which creates more value for a physical visitor? Digital resources are a fallback for over demand. For under capacity systems they are a lower quality solution than full service.
When I go to museums without this, I bring printed guided tours to follow (Rick Steves has a bunch, but there are others). The good ones have a them, take you to specific pieces and tell a story that puts them in a cohesive context.
The best audio guided tour I have had was at Graceland -- there, it's mandatory (too crowded) and you follow along a linear route through the house. The reason it was great was that Pricilla Presley is the tour guide and they can incorporate Elvis's voice and music.
I don't code, and mobile tech is unreliable for short-term visitors to Istanbul, so I never bothered trying to port the content to a device. Basically though, the solutions to puzzles are used to decipher new material and explore the spaces more thoroughly. For example, everyone who goes to the Hagia Sophia visits the mosaic portrait of the Empress Zoe, but not everyone knows about the Viking runes carved into a stone banister, so the idea was to link things and challenge people to explore, and then to use what they had found to unlock other puzzles.
It was clunky as shit on paper, and sometimes friends would give up or call to ask for clues, but they said they enjoyed it (or they were really, really polite). On a device, I'm sure that sort of interaction would be simple, and it's something I still toy with learning to build, but Istanbul keeps happening to me and getting in the way.
The problem with a straight QR code are that non technical people just have no idea what they are or how to use them (just ask your parents or friends).
NFC etc again have the same kind of issue. Non-technical people just dont know how it works (also the fact that only the higher end devices support it).
Personally I would go for one of the two following options after working on something similar.
You could look into an app for the museum. The app will have a QR code reader built in, but you can also offer geolocation. The important thing in this case is to advertise the app everywhere. Also give the museum free wifi so people can download the app.
Or look at an internal WiFi network which only servers your website. If you wanted to get a little more technical you could get the website to allow location (really only works on single floor buildings) to server items close to where you are.
Other people seem to feel the same way. The majority of the time I see people glance at a sign, read one or two lines, then keep walking.
Imagine people only have an hour to go through the museum. How can you organize and display the most interesting data for them? Pick out the best facts, and design some eye catching infographics that make them stop in their tracks.
And why not make things more interactive? I'll learn more that way. Quiz me, give me a few multiple choices on a touch screen, and let me guess what period this artifact is from, or how much this particular ship anchor weighs. What about the number of people on the Titanic, or how many were crew, how many were passengers? How many survived? Things like this make people stop. They're walking and they see a question with a few answers. It makes them think, talk about it with the people they're with. You could show the average votes for each answer based on past visitors, etc.
The day-to-day realities of managing and growing a startup are very challenging, especially if you are the sole founder. I've been there in the early days for numerous startups and for myself, and found that most difficult parts are not necessarily related to the business, product, or customers themselves, but rather they are usually emotional in nature, and center around how to stay motivated, continue to get things done and move forward when there's no end in sight. The hardest part is feeling like you're alone, there's no one else who gets it to talk to.
I'm not an investor or startup advisor, but I'd be happy to help you out if you want to work together. My contact is in my handle.
Your list of interests sounds like that of a computer scientist, but I'm allocating a little space to "Maybe your only exposure to computer programming so far has been undergrad CS and you're describing it in the only language anyone has ever taught you."
The best way to skill up as a programmer, if you're interested in that, is to ship more software. There is deep, mythical knowledge in programming, and it is acquired with sweat on your brow and a pickaxe in your hand chipping away at a coal face made out of Why Doesn't This Freaking Work.
You will note that most programs you work on build on things you have heard about in CS classes but do not implicate most of them directly. Compilers are very nice to understand. If you want to be a programmer, absent you making the goal of working on compilers your life's work for the next 10 years, you will probably not work on compilers. Most coal faces sound like something rather more like "A business has some fairly straightforward transformations to be made on two sets of data. There's plenty of opportunity for smart implementation choices and cleverness, but that mostly informs the small rather than the large of this project." (Cleverness in the large in programming is good selection of which coal faces to attack at all. After you get there people often stop calling you a programmer no matter how much programming you do.)
However: it sounds like your interests are actually more in the realm of Computer Science than Programming, though: type theory, theory of computation, compilers, AI, etc. are less in the realm of programming and much more in the realm of computer science. You don't really need to know how an NFA or DFA works in most day to day programming, frankly. For learning Computer Science, I would suggest finding an advanced course with all of its material online (MIT OpenCourseware is a good place to start, or any of the other free online courses places), and working through a course on the topic. If it has prerequisites that you don't know any/most of the material from, then find a course on those. In my opinion, the other common options (reading through a textbook, reading papers, working on a project related and just learning what you need for that) all have flaws: textbooks are usually designed to accompany a course, which means they usually have much more than you need to learn a lot about the subject (and, in my experience, many are unbelievably boring and poorly written; if you want to go that route, make sure you find ones that are appropriate for self study). Reading papers is really interesting (and a lot more fun than reading textbooks), but without context or knowledge about the area, it's hard to evaluate the paper's meaningfulness/claims/etc., and hard to decide which papers are important to read. Working on just a project (e.x. just writing a compiler) leads to learning just enough to make that project, and not more.If you want to improve at programming: follow the advice about either making a personal project or working on an open source project. The fastest way to get better at programming is to program more.
Frankly: it sounds like you are decidedly not as much of an 'expert beginner' as you think you are. Familiarity with basic data structures+complexity, an understanding of theory, and an understanding of math through linear, ODEs, and discrete already puts you on a very firm grounding. (Outside of certain very specific parts of CS, you /do not/ need more math than that. If you're going into graphics research, knowing differential topology+geometry might be handy. I'm having a hard time thinking of things other than that, though.) From your description, you have more or less finished the 'beginner' stage, moved well beyond the 'novice' stage, and are moving towards becoming someone with a lot of advanced knowledge. Just knowing that you're interested in things like type theory+compilers/machine learning+expert systems+AI already puts you /way/ beyond being a beginner.
Shameless plug of someone else's stuff: if you're not sure where to start on the courses front, and want to start on the programming languages side of things (compilers, etc.), this course might be a good place to start: https://www.udacity.com/course/cs262I haven't worked through this course in particular, and I don't know its exact difficulty, but I took undergraduate programming languages from this professor and he's an /amazing/ teacher.
Edit: don't know why I had two copies of that written, but now there should only be one. Also, cryptography is another part of CS that you need more math (in this case, abstract algebra). (More multiple copies? I seem to be pretty bad at this "say things once" thing, and need to make some preference changes.)
Also you don't sound line an expert beginner, you sound like a beginning expert, I'm programming for 10 years for a living, built a couple of money making startups, and doing my MSc at the moment, I can't say I know half of all that at an expert level ;)
Finally, accept that you don't really have to know everything, and more so, you can't really be an expert in everything, it's really hard but CS is a very wide field. You can't help but being a beginner expert on a wide area of topics, and only a "real" expert in a very narrow subject. Not all CS Phds are expert in everything, actually they are most likely expert in a very narrow set of topics relevant for their research.
Bottom line, either learn for learning and do it in a place that honors it (academy or independent / commercial research) Or build something that makes money, and the subset of human knowledge needed to make it work will be defining itself (you'll have to fight the urge to learn things that "you'll probably need later", and make it more "on demand" learning)
Download the code, figure out how to build/install it, and start to find your way around the codebase to try and figure out which bit of code is at fault/needs extending. When you get stuck, ask on the dev mailing list or IRC or whatever comms channels the core dev(s) have.
A lot of programming is not about designing something elegant and new. It's maintenance work, fixing bugs, extending functionality, adding new features. Sometimes adding exciting new features is a chance to design something elegant and new, but other times it's a bunch of repurposing and refactoring some features that are mostly-there under the hood, but need a couple of tweaks, and a small amount of really new stuff (but in the same idiom as the rest of the system) and exposing in a new way.
You'll really find out how to properly spelunk into a codebase (which is a complementary skill to just reading code), how code is used, and how it solves real-world problems.
If another dev solves the bug before you do, that's not a problem. The real purpose of the exercise was for you to learn, and only perhipherally to help the project. As a bonus, you can see how the other dev solved the problem, and how their solution differs from yours. Did they solve the bug at the "same level" as you? Was their fix a bigger or smaller change than yours?
If you get there first, great! Submit a patch to their mailing list, or a pull request to their git page, or whatever they use. Do not take their criticisms of your work as a personal insult. (If they do insult you personally - which almost certainly won't happen, but very occasionally does - that's another matter. Drop it and find another project. Life's too short to waste on asshats.) Rather, listen to exactly what they don't like about the way you solved the problem, use that to fix the problem in a way they will like, and re-submit.
Do your own thing. Build something you want to see built and you will learn oh so much. Programming isn't about how you implement something so much as it is for what reason. Think of something you want to see built and figure it out from there.
For example, I learned Python by trying to write an app that would take my Shazam tags and convert them to a Google Music playlist so I could more easily remember songs to listen to later.
Notice that I didn't write anything about SQLite or how slow Python's HTTP was when making the queries, because in learning Python, that wasn't important; those things were just implementation details that I only started thinking about after my application was demonstrably "slow." And more than that, I really didn't consider anything about lambda calculus and I don't know a single thing about NFAs or DFAs. I just wrote an app.
And I learned something, enough to get the job done. If you really want to learn about how to apply functional programming, learn Haskell. If you want to learn about compilers, write a compiler. You'll learn enough, because there's no way you can learn "everything" on a topic in Computer Science.
The field is much too broad, and you'll be way better off lazy-evaluating it than calculating it wholesale.
Tl;dr: If you want to be a better programmer (as opposed to being a better computer scientist) build and the knowledge will follow.
My advise would be to look at your own network (friends, family, etc) and find those who are in business and ask them about their pain; and there is always some pain that a business has. Then figure out a solution to their problem and program that.This serves 3 purposes:1) It has a definable goal and purpose (solving the pain) as it's a real-life project.2) You will learn tons about yourself, programming, and the business.3) It could lead to either employment or a program you could sell to others and start a business.
As always, make sure you write-up a contract which states that the IP is yours. Hope for the best; plan for the worst.
Also, there's a disconnect between academia and the workforce. You might invent a fancy new data structure that blows up in real use because it ignores caches. Or you might invent something that's cache-aware, but everybody's using scripting languages or the JVM and doesn't have that level of access to the hardware. And so on. If you're strictly speaking about becoming better at the work of programming (rather than CS), that stuff isn't that important. You will spend way more time, especially as you move up in seniority, interacting with people - whether it's designing your system to be understandable by humans, persuading others of your ideas, getting funding, etc.
+ There's a traditional sequence in skilled trades of apprentice -> journeyman -> master. A contemporary trade probably throws student on the front end and perhaps renames apprentice to 'intern'.
What separates a student from an apprentice/intern is the type of problems they work on. The same idea distinguishes the journeyman from the apprentice except that the journeyman is expected to successfully solve the problems they work on. Etc for the master.
What I am getting at is that there is a range of expertise and that what marks someone as an expert is the sort of problems they solve. But it's critical to realize that the context in which they solve those problems matters. This week thousands of students will be writing quicksort code. In 1960 it was the stuff of ...well CA Hoare probably was an expert programmer in an absolute sense, and perhaps a new journeyman among those who were programmers. Here again, context matters when talking about expertise...the one-eyed man in the kingdom of the blind and all that.
+ It's not really clear what you mean by 'expertise'. An expert AI programmer is someone who has solved expert level problems - one in an academic setting earns a credential. In a vocational setting it's going to take several.
But in both settings the context is years, not hours per day.
+ Sure you're free to define what it means to be an expert. Regardless of what definition you choose, the question remains, what does an expert do that you aren't doing? This isn't a question of research. It's not a question of methodology. It's a question of personal opinion - that is, what activities would you have to do to meet your definition of an expert. Maybe that's working at Google. Maybe it's earning a phd. Maybe it's writing a replacement for HotSpot.
+ Once you know what sort of problems you need to solve to move toward being an expert, perhaps just trying to solve some of those problems is the place to start. I.e. what sort of problems does an apprentice or journeyman tackle?
Honestly though that set of interests doesn't seem like the sort of thing that lends itself to real problems; it sounds to me like you've already got more than enough CS theory. If you're looking to learn the kind of programming that will make you better at doing it professionally, you need to start making practical things. Find a hobby that could do with a website/app or something else in your life that can be automated.
You can easily spend the rest of your life shaving these mythical yaks and when you are old and surrounded by mountains of yak hair, you'll feel exactly the same as you do now.
There is more to learn than you can ever hope to. Just learn what you need as you go. It's the key to all existential crisis: Try not to think so much.
Lose your first 50 games of Go as FAST as possible!Don't worry about winning or losing or finding the "right" move, just put some stones down, get used to looking at the shapes that come up, and get a good feeling for how the rules work. Of course, a consequence of that attitude is that you will lose most of those games, but it doesn't matter. Once you have a bit of experience under your belt, then you are ready to begin
Take a break from focusing on the strategies and tactics of programming. No single algorithm, framework or language is going to unlock the panacea of potential inside of you. Most problems simply aren't that complex in the beginning.
Having the mindset of an innocent beginner always is the toughest thing to maintain to remain a problem-based thinker instead of a solution-based thinker.
The best way I've found is simply to solve problems the best I can, and when I learn what I could have done better, if the need is there, go and refactor it. No matter how great you are, or aren't today, what you write may look bad in 5 years because you have more experience.
Most things we build as developers become obsolete. It's a separate discussion but I'm not sure what you're trying to optimize, your skills, or a result in a project?
No developer is a a factory of churning out code or results at the same speed. Be less focused on the practice of programming alone and look at the results you're creating.
Software is as much a craft, an art, as much as a technical skill, and maybe it's something for you to explore the other fronts.
Forget about trying to learn EVERYTHING. Pick one thing, learn it well, repeat with the next thing.
As mentioned, the more you can do this within the confines of projects you feel passionately about, the easier it will be.
One of my favorite sayings goes: "What's the difference between theory and practice?" "In theory, there is no difference".
It sounds like you have the theory covered pretty well.
(1) Start committing to Github daily. Make your own project and just go with it until you it's finished and learn what you need too.
My example project: http://austingwalters.com/openbkz/
(2) You can go through online courses in an attempt to learn more and become an expert, many courses are online. You could also start following blogs, read papers and replicate results.
If you are interested in maximizing learning: http://www.scotthyoung.com/blog/
(3) The past month I have been writing a blog a day, it increased my productivity and forced me to really master topics:
My explanation on blogging: http://austingwalters.com/learning-through-blogging/
I recommend blogging, videos, or writing stuff down for "teaching" others because it really helps you master a subject and helps you think of ways to use those concepts.
Do you really think your average HNer knows how to do that? Or even know what that means and how you define it? I really don't think so :)
In my opinion you know plenty about computer science, certainly much more than your average programmer, but I understand how you feel. I think of myself as not knowledgeable enough and below average all the time.
You haven't mentioned your goal. Do you want to eventually work in any of the areas you mentioned? Or rather you want to learn this for your own intellectual curiosity?
Also, I see a pattern that more you are used to studying more quickly you tend to understand something new. I believe its something do with reading habits. So don't leave theory completely, but keep a balance b/w theory and practical.
> mythical stuff before it's too late.
Too late for what? What is the hurry?
I mean, there are books on this stuff? Read them, do their exercises, and you will be fine.
I will say, most of this stuff now functions mostly as mind training. The specifics about low level computer systems, Big (O), parsing and compilers is the only part I see repeated use in my day to day.
>So knowing this, how would I best use say 8-12 hours a day, every day, to learn this stuff?
You should audit courses at a CS program taught near you. This stuff is chunky and the books are designed mostly for a classroom setting
2. Books and papers are great, but you should also try to find a mentor / guide / teacher / expert to talk about the issues you're facing and what you're thinking about. Schools are organized the way they are for a reason, even if they often fail at their intended purpose.
Unlike for athletes or musicians, practice in a knowledge field (like CS), seems a little ill defined..
2 build, then rebuild, your own systems
After 10,000 hours of this, assuming you keep climbing rather than just doing the same thing over and over, you will be competent.
Whatever you do, as long as there is a minimum amount of fun in it, you'll get better.And the more you know, the better you can identify what areas you have and/or want to improve in.
Above all, always have fun!
A couple books that are worthwhile: "Refactoring" and "Rapid Development". That will teach you a lot of basic skills in terms of development process and how to improve the design of real systems (warts and all). Also, take a look at the Architecture of Open Source Systems, it'll acquaint you with how applications fit together.
Also, take on some projects. Pick something interesting and work on it. Pick some small stuff then move up from there. I'd suggest in your case eventually building a compiler. If you're interested in AI, build some simple games and work on building AI for them. There is nothing more important than actually writing code.