4 ms·

You just stated why you are a terrible CEO. If you want to succeed doing a startup, unlearn everything and try to be more like him. At the least don't make thin

by jarsj 16y ago

You just stated why you are a terrible CEO. If you want to succeed doing a startup, unlearn everything and try to be more like him. At the least don't make things worse for him. If he is your 50% partner, he has as much right to decide the office timings as you are. In my last job, I used to crash in the office most of the time (9 AM to 3 PM), skip most weekdays, work all night and all sunday. I never had any complaints and was considered quite good at what I do. My last job was at Google.

rick888 16y ago
"In my last job, I used to crash in the office most of the time (9 AM to 3 PM), skip most weekdays, work all night and all sunday. I never had any complaints and was considered quite good at what I do. My last job was at Google." In a company like Google, there are enough people in the office during normal business hours to compensate for the time you aren't there. I can sympathize with the poster. If he (his co-founder) is the only person working on the technical side of the project, he should be there in the office during normal working hours. When they do need to meet a client at 9am (because most businesses in the US are 9-5), will the developer be able to be there without falling asleep at the meeting? It also shows me that the developer lacks discipline. The poster made a mistake in making him a co-founder. He probably should really be an employee. I also get a sense that the developer wants to just hack away at the code on his own time and not have to talk to anyone about it. This is a recipe for failure. I've worked on many projects like this and what usually ends up happening is that the project gets finished with little or no input from customers/other people besides the developer and it fails.
- jarsj 16y ago
  "In a company like Google, there are enough people in the office during normal business hours to compensate for the time you aren't there." Not really, there are several projects and average size of a team is quite small. In my case we were five people working on a quite large project and no one could compensate for my time. I knew I had to get something done in a week time and I will figure out how to do it. If needed, I had be there 24 hours, but otherwise I am my own boss.
  - rick888 16y ago
    "Not really, there are several projects and average size of a team is quite small. In my case we were five people working on a quite large project and no one could compensate for my time. I knew I had to get something done in a week time and I will figure out how to do it. If needed, I had be there 24 hours, but otherwise I am my own boss." Somebody needs to meet with the higher ups at the company during regular working hours. It just wasn't you. It also depends on what your project entails. If it was all internal, you can easily get away with working on code all day without having to discuss it with customers. The situation with a startup is different.
    - jarsj 16y ago
      I had happily come to office at 7-8-9 AM to meet an higher up or attend an important meeting or whatever. That doesn't happen everyday. In an startup, quite contrarily, I had want my co-founder to schedule meetings taking my timings into account. When not possible, I had come happily.
      - rick888 16y ago
        "I had happily come to office at 7-8-9 AM to meet an higher up or attend an important meeting or whatever. That doesn't happen everyday. In an startup, quite contrarily, I had want my co-founder to schedule meetings taking my timings into account. When not possible, I had come happily." I think coming in late is fine, as long as you can handle the early meetings when needed and the work is getting done. It doesn't seem like this is happening with the co-founder here.
- rick888 16y ago
  I gave some very good reasons why the developer should be coming in at a reasonable time. It seem this hit too close to home with many of the developers here.
  - rick888 16y ago
    It seem this hit too close to home with many of the developers here. (I don't care about my karma)

by jarsj 16y ago

rick888 16y ago

"In my last job, I used to crash in the office most of the time (9 AM to 3 PM), skip most weekdays, work all night and all sunday. I never had any complaints and was considered quite good at what I do. My last job was at Google." In a company like Google, there are enough people in the office during normal business hours to compensate for the time you aren't there. I can sympathize with the poster. If he (his co-founder) is the only person working on the technical side of the project, he should be there in the office during normal working hours. When they do need to meet a client at 9am (because most businesses in the US are 9-5), will the developer be able to be there without falling asleep at the meeting? It also shows me that the developer lacks discipline. The poster made a mistake in making him a co-founder. He probably should really be an employee. I also get a sense that the developer wants to just hack away at the code on his own time and not have to talk to anyone about it. This is a recipe for failure. I've worked on many projects like this and what usually ends up happening is that the project gets finished with little or no input from customers/other people besides the developer and it fails.

jarsj 16y ago
"In a company like Google, there are enough people in the office during normal business hours to compensate for the time you aren't there." Not really, there are several projects and average size of a team is quite small. In my case we were five people working on a quite large project and no one could compensate for my time. I knew I had to get something done in a week time and I will figure out how to do it. If needed, I had be there 24 hours, but otherwise I am my own boss.
- rick888 16y ago
  "Not really, there are several projects and average size of a team is quite small. In my case we were five people working on a quite large project and no one could compensate for my time. I knew I had to get something done in a week time and I will figure out how to do it. If needed, I had be there 24 hours, but otherwise I am my own boss." Somebody needs to meet with the higher ups at the company during regular working hours. It just wasn't you. It also depends on what your project entails. If it was all internal, you can easily get away with working on code all day without having to discuss it with customers. The situation with a startup is different.
  - jarsj 16y ago
    I had happily come to office at 7-8-9 AM to meet an higher up or attend an important meeting or whatever. That doesn't happen everyday. In an startup, quite contrarily, I had want my co-founder to schedule meetings taking my timings into account. When not possible, I had come happily.
    - rick888 16y ago
      "I had happily come to office at 7-8-9 AM to meet an higher up or attend an important meeting or whatever. That doesn't happen everyday. In an startup, quite contrarily, I had want my co-founder to schedule meetings taking my timings into account. When not possible, I had come happily." I think coming in late is fine, as long as you can handle the early meetings when needed and the work is getting done. It doesn't seem like this is happening with the co-founder here.
rick888 16y ago
I gave some very good reasons why the developer should be coming in at a reasonable time. It seem this hit too close to home with many of the developers here.
- rick888 16y ago
  It seem this hit too close to home with many of the developers here. (I don't care about my karma)