Slashdot Mirror


Hire a Developer, Watch Them Work In Real-Time

New submitter alphamore writes: Live Coding, which is like Twitch for developers, has added a service that allows viewers to actually hire someone they've been watching. The aptly named 'Hire a streamer' service works exactly as it sounds. Via the profile of a developer you've seen coding on the site, a 'hire me' button lets you request their time. The service is completely opt-in for developers, so not everyone will be for-hire. When you click on the 'hire me' button, you'll be met with a list of disciplines that developer is familiar with, and their hourly rate. Once you've booked a session, the money is held in escrow (transactions happen via the site) until the developer has completed the work.

100 comments

  1. Sounds stupid by Psychotria · · Score: 4, Insightful

    When I'm coding I might spend 30 minutes thinking about something or scribbling on paper and then spend maybe 2 minutes actually typing the code. Those are just fictitious numbers of course, but really both of those numbers could be much higher or much lower depending on the problem.

    How does this service account for thinking time?

    1. Re:Sounds stupid by Psychotria · · Score: 4, Interesting

      I should say that I am no longer working as a software developer because I needed a change and got another degree and now work in a science field, but the same thing still applies and programming is still part of my job.

      I could spend 8 hours writing crappy code, iterating over it, changing it, tweaking it, etc, etc, throughout a typical work day. But, and I'm pretty confident in this, I can (and do) instead spend maybe 25-75% of my day (or more) thinking about things -- designing things -- before implementing them and end up with a better result. I've had jobs where lines of code, or in some cases, words per minute typed, were a metric and left them as soon as I found a job based on reality instead of fiction.

    2. Re:Sounds stupid by Hognoxious · · Score: 2

      Like this, probably. http://dilbert.com/strip/1995-...

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:Sounds stupid by Anonymous Coward · · Score: 0

      HAHAHAHAHAHAHAHAHAHAHAHA!!!!!!1!!!11! That is the FUNNIEST thing I have ever seen in my ENTIRE LIFE!!! I have NEVER laughed so hard before!!!!

      Truly Scott Adams is a comedic GOD and you, my friend, are his most humorous herald!!!!!

    4. Re:Sounds stupid by Karganeth · · Score: 1

      Meh, you'll just have to scribble on software paper now instead. Or if it records your voice too, talking through the problem would be neat. Audio proof you're working.

    5. Re:Sounds stupid by Anonymous Coward · · Score: 4, Insightful

      Those aren't developer jobs, they're programmer jobs. You know, the kind of jobs that are often hidden behind "implementation left as an exercise to the reader". The kind of problem that you have to think about does not concern programmers. Their job is to apply the tools to translate a specification into a program.

      And fuck these people for giving employers the idea that "computer people" should be watched and paid piece-rate like a factory worker. To the employers: If you pay be LOC and hours worked on a problem, then that's what you get: Lots of code that takes a long time to write.

    6. Re:Sounds stupid by Anonymous Coward · · Score: 0

      No kidding. I remember when I needed a highly optimized quad tree, as in it sat dead center of a ultra high frequency code region and needed to use as few resources as possible. Think I worked on the math side of it for a good month evaluating a variety of approaches before I settled on an approach that took maybe a day or two to actually write the code for and test. To a watcher it might have seemed like diving too deep or taking too long on a single part of the problem. To a programmer that looks at what it's used for, it's the most crucial key to achieving good performance in that program and pretty amazing considering the entire thing fits inside a typical x86 cpu cache while being able to generate gigs of data at the drop of a hat.

    7. Re:Sounds stupid by fatgraham · · Score: 1

      If 10% of your time is actually spent interacting with the computer, then just charge 900% of your normal hourly fee. "Thinking" is now just an expense covered by your rates :)

    8. Re:Sounds stupid by Anonymous Coward · · Score: 3, Interesting

      Awwwwwwwww, it's always cute when kids discover sarcasm for the first time.

    9. Re:Sounds stupid by Anonymous Coward · · Score: 0

      If you only get paid for 10% of your time, you need to charge 1000% to make the same as if all of your time was paid at the normal rate.

    10. Re: Sounds stupid by Anonymous Coward · · Score: 0

      "Their job is to apply the tools to translate a specification into a program."

      In the real world, there is no such thing as a predefined specification. Analysis, detailed design, and problem solving is the main part of a developer/programmer's daily work.

    11. Re: Sounds stupid by Anonymous Coward · · Score: 0

      developer/programmer

      Those words are not interchangeable. In the real world, architects don't pour concrete. You couldn't afford a house if all people working on it were architects. But if the architect is never on site, you won't get a good house. The people who let you watch as they type code into Visual Studio are not the architects in this analogy. How often do you see construction workers actually analyze the owner's needs and refine or revise the plans (instead of just ignoring the plans)?

    12. Re:Sounds stupid by jellomizer · · Score: 1

      I prefer the whiteboard myself. Even with a pencil, there are too many eraser marks marks, I rather just rub it off with my finger and do the correction.
      I normally go to the whiteboard when I realize I am stuck with just coding it from my head so I use it to visualize the information I need to work with.
      Sometimes I flow chart it, other times it is just to chart it out. Tools like Visio and excel, are too clumsy for such work as they try to make assumptions that I want something, that I myself isn't sure if I want it or not.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    13. Re:Sounds stupid by mysidia · · Score: 1

      If 10% of your time is actually spent interacting with the computer, then just charge 900% of your normal hourly fee.

      This makes sense.... you are actually getting paid for everything you do. The number of hours you are actually coding is just being used as a benchmark; it should only be a proportion of the time, if your work is high quality ---- BUT it should still be a proportion of your time.

      If you're spending 1 hour of thinking for every 1 hour of coding, then the hourly rate should be triple what it would be if you were just spending 0 hours of thinking for every 1 hour of coding.

      Also, people want to pay for something they can see.

      So you could do "live thinking" where you jot some notes, and you create some 'draft' text files and do a couple rough sketches.

    14. Re: Sounds stupid by jellomizer · · Score: 1

      I got my MBA, and I took an MBA course in Software Application Development. I was constantly butting heads with the professor because the concepts where based on unrealistic assumptions. I did learn UML so I can toss that on my Resume, however starting with the first assumption.
      Figure out all the people who will be interacting with your software at some level. Aka the Actors. Because as the product gains footing more people jump in and some jump out. Which makes the second phase of gathering required information that each person needs, impossible as well, because they really don't know what they need, they think they do, until they see the project in action, then they will need other stuff.

      For an application of any real scale the UML based design cannot be done in one pass, but will need to be iterative over time. So you will have the programmers going back and redoing their work over and over again.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    15. Re: Sounds stupid by Anonymous Coward · · Score: 0

      I don't have time to explain in detail, but your comoarisons between construction work and software development is nowadays considered ourdated and a fallacy.

      Also remember that most programmers/developers usually have bachelor or master of science degrees. They are not unskilled workers.

    16. Re:Sounds stupid by shadwdrak · · Score: 2

      It's really not "Hire a worker" to do "work". The service is more geared around a private tutor model.
      You can hire a streamer to get a private one on one stream with them; for whatever reason the streamer wants to hire out for.
      Sure, people can do work for hire that way but I don't think it will see much use in that regard.

    17. Re: Sounds stupid by Anonymous Coward · · Score: 0

      They are not unskilled workers.

      I take a look at the general quality of code and have to disagree. Sure, it takes some experience to learn the tools, but only in the same sense that construction workers are not "unskilled workers" either. It is difficult to see who can do what, but that doesn't mean that there are no differences. You will not find a developer on one of those "watch me work" sites who can solve problems that don't already have a "best practice" solution awaiting implementation. As is the topic of this thread, who would pay for seeing someone think? The jobs which still need thought are unsuitable for these sites, and developers who have those skills don't have to whore themselves out like that. That leaves straight-forward implementation, and there are people who do that and just that, whether you like it or not.

    18. Re:Sounds stupid by Anonymous Coward · · Score: 0

      Cute it is, but sorrowful when they spend a quarter century milking the same jokes out of it.

    19. Re:Sounds stupid by Anonymous Coward · · Score: 0

      Says the butthurt tween who finds Scott Adams funny. That automatically invalidates your opinion on anything that even remotely has to do with comedy.

    20. Re:Sounds stupid by Anonymous Coward · · Score: 0

      What's not so cute is when smarmy, condescending, useless little pukes like yourself are given access to the Internet.

    21. Re: Sounds stupid by RabidReindeer · · Score: 1

      They are not unskilled workers.

      I take a look at the general quality of code and have to disagree. Sure, it takes some experience to learn the tools, but only in the same sense that construction workers are not "unskilled workers" either. It is difficult to see who can do what, but that doesn't mean that there are no differences. You will not find a developer on one of those "watch me work" sites who can solve problems that don't already have a "best practice" solution awaiting implementation. As is the topic of this thread, who would pay for seeing someone think? The jobs which still need thought are unsuitable for these sites, and developers who have those skills don't have to whore themselves out like that. That leaves straight-forward implementation, and there are people who do that and just that, whether you like it or not.

      This just plays into the old movie trope where some nerd sits in a dark room with a bunch of friends, types at a high rate of speed, and "presto!", he's hacked the Pentagon. And don't forget that you can see letters from the screen projected on the wall behind him. It's no more realistic than the "zing" sound when someone draws a sword, the "pfhut!" that's all that comes from a silencer or that every car wreck results in an explosion and fire.

      Real development doesn't take place at the keyboard, any more than real architecture takes places where the blocks are being laid and the concrete is being poured. The important stuff was done elsewhere. Even if you wanted to posit that the architectural work was done at the drafting table, a lot of the work consists of drawing things and then throwing them away.

      One of the problems with software is that there's immense pressure to "Git 'R Dun!" and NOT to throw away work even if it was a false start. It's not that developers are all unskilled workers, it's that the demands of the day actively punish skilled workers in favor of the "productive" ones. Productive as defined by "make pretty web pages quickly", not by performance, security, robustness, or even the quality of the code.

      As long as the buyers want fast and cheap over value and quality, expect that to continue.

    22. Re: Sounds stupid by Anonymous Coward · · Score: 0

      Construction workers aren't unskilled either. I doubt you'd be able to find a software developer who was capable of adding a room on to their house, let alone building a skyscraper.

      A degree is nothing but a piece of paper that says you successfully sat through several years of lectures and practices in controlled environments. It says nothing about the ability of the person who possesses it.

    23. Re:Sounds stupid by Anonymous Coward · · Score: 0

      People act like developers and programmers are two different jobs. They're not. A programmer is really just a developer job without the benefits, with lower expectations, and lower compensation. With such a structure you get worse code, but odds are that 95% of the people paying can't tell the difference.

      What they can notice is how their money doesn't translate into stuff at an acceptable rate. Of course to fix this, they estimate they'll need more work, leading to a need for lower costs, and the hiring of people who haven't considered design beyond the "what do I have to do to fix this bug".

    24. Re:Sounds stupid by Anonymous Coward · · Score: 0

      People act like developers and programmers are two different jobs.

      Are you trying to tell me that you really never had to work with someone who could use all the tools and write code but not develop his way out of a wet paper bag? Do you really believe everyone who can write code that passes some tests is capable of designing an application which fulfills a non-trivial purpose and that anyone would want to use? If you're calling people like that developers or software engineers, you're muddying the water. Don't pretend that programming and developing are the same.

    25. Re: Sounds stupid by Anonymous Coward · · Score: 1

      In software development the source code is the blue print. The "pouring concrete" and building part is actually the build system and compiler's job. So the costruction workers and factory workers doesn't really exist in software development.

    26. Re:Sounds stupid by Anonymous Coward · · Score: 0

      you can always think outloud... its called speaking you autist

    27. Re: Sounds stupid by Anonymous Coward · · Score: 0

      We agree on this:

      "The jobs which still need thought are unsuitable for these sites, and developers who have those skills don't have to whore themselves out like that."

      The reason why i mentioned that most developers (and architects) have a college or university degree, is to point out that development is not just toying around. It's real work, and requires just as much knowledge as any other science or engineering field. Why would grown up people like that be part of something stupid as that. The ones left are probably some students, amateurs, script kiddies, or wannabes, but I doubt that many real developers would participate.

    28. Re: Sounds stupid by Anonymous Coward · · Score: 0

      I don't know which country you are from, but where I live I haven't ever seen any employer making a distict difference between a developer or a programmer position. To get hired you would at least be what you seem to call developer. I don't know any companies where I'm from that would hire what you define as a "programmer" - a person that can't develop, just mechanically type in code based on some finished specification that someone else developed. Why would anyone hire such a person? I just haven't seen that in my 15 years in the software industry. But maybe it's more common in other countries, or in the offshoring industry. I don't know.

    29. Re: Sounds stupid by Anonymous Coward · · Score: 0

      Lol construction is hard work. I worked for a friend who owned a company building houses. Worked there for 1 day and quit. Hard work. They still call me one day Mike to this day.

        Lol one day was enough for me. I told him these hands and fingers were meant for typing.

    30. Re: Sounds stupid by Anonymous Coward · · Score: 0

      Should make them code naked.

    31. Re:Sounds stupid by Fnord666 · · Score: 3, Insightful

      I could spend 8 hours writing crappy code, iterating over it, changing it, tweaking it, etc, etc, throughout a typical work day. But, and I'm pretty confident in this, I can (and do) instead spend maybe 25-75% of my day (or more) thinking about things -- designing things -- before implementing them and end up with a better result.

      But in the former case at least you would be "Agile".

      --
      'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
    32. Re: Sounds stupid by Hognoxious · · Score: 1

      So the costruction workers and factory workers doesn't really exist in software development.

      I thought their equivalent was the users. Hitting a nail through a pipe, sticking a part in upside down, putting the number of employees in the NAICS code ...

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    33. Re: Sounds stupid by HornWumpus · · Score: 1

      It's a big business thing. Old big business.

      System analysts was the old pigeon hole. They were supposed to build tight and complete specs (which made them instant 'database experts'), coders never met the users. Never worked, always took forever, cost a fortune and couldn't hit a moving target.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    34. Re: Sounds stupid by Anonymous Coward · · Score: 0

      You'll only do that once.

    35. Re: Sounds stupid by Anonymous Coward · · Score: 0

      No they're not, but any good programmer that is not a code monkey, wears many hats. If you don't know why your code works, are you really programming? There tends to be a "it compiled" mentality, that if it works, then it's perfect. Everything works, until it breaks. Some things break earlier than others. When I program, my goal is my program only breaks in very specific circumstances for very specific reasons and has very specific ways to immediately fix it.

    36. Re: Sounds stupid by Anonymous Coward · · Score: 0

      Which makes the second phase of gathering required information that each person needs, impossible as well, because they really don't know what they need, they think they do, until they see the project in action, then they will need other stuff.

      I had a class in Systems Design and Architecture. One thing my teacher constantly reminded us all is the end user does not know what they need, only what they want, and it's your job to design the system to handle their needs. In the real world, I get specs all the time from consultants and I pick apart all of the flaws, so they can let the customer decide to go forward or to take my advise in changes.

      Theory is only useful if you realize that humans make mistakes and designing your projects to minimize mistakes is incredibly important.

    37. Re:Sounds stupid by Anonymous Coward · · Score: 0

      I don't think they're saying the responsibilities are the same, just that developing without thought of how to program is a mistake as much as programming without thought of the design is a mistake. They are two sets of responsibilities that should NOT be separated. Being technically correct is not good enough. The code needs to work in harmony with the rest of the system. Implementation details are important, and by the time you're done documenting the details, you may as well just have programmed it yourself.

    38. Re:Sounds stupid by tlhIngan · · Score: 1

      When I'm coding I might spend 30 minutes thinking about something or scribbling on paper and then spend maybe 2 minutes actually typing the code. Those are just fictitious numbers of course, but really both of those numbers could be much higher or much lower depending on the problem.

      How does this service account for thinking time?

      You're not the only one. I hate sitting at the computer and typing up code. Instead, I want to understand it, ponder it, think, and then write a succinct amount of code that does it cleanly, properly and correctly, is easy to maintain, and is pretty clear.

      I'm sorry, but I can't just be given a task to write some code and write it (I can, but it's a waste of skill and time (and thus your money), and I will say so, but it is, in the end, your dime, which will buy less if you ask me to do it than a cheaper code monkey). I will try to architect the code, figure out what is needed and then proceed the write the least amount of code. I will also stop and think if I see myself copying and pasting code to see if the situations are such that it really warrants the duplication (too many small changes) or if there's something more general about it.

      Yes, I like to think before I type.

    39. Re:Sounds stupid by sg_oneill · · Score: 1

      Yeah im the same. I'm often working in fits and starts. Often I'll get into the office, smash down a coffee and blast a couple pages of code out, then hit a snag, lose steam and not really achieve much for half an hour, then blast back into it for another 10 minutes, then completely zone out for an hour before hitting the groove again for an hour straight. Some bosses see this and whilst they might note I *always* hit my deadlines want me to spend less time non productive. The problem is, programming is brain work, and brains dont work well by constant pumping. They are muscles that need to relax and turn off to recharge for more work. And sometimes the best ideas happen during that zone out. I'll be idly reading some wikipedia page on a particular algorithm, and then it strikes me that its the solution to a problem that I've been wrestling with. Or I'll be out the back having a cigarette with the boss talking over the job and we'll stumble over a great way to move forward.

      Productivity isnt just a constant flow of key strokes. Thats just makework metrics. Productivity is the whole ugly process, and as much as we try and structure it with various time management techniques, at the end of the day, creativity is chaotic.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    40. Re:Sounds stupid by slashdotwannabe · · Score: 1

      Give me six hours to chop down a tree and I will spend the first four sharpening the axe.

      -- Abraham Lincoln

      --
      This comment is my opinion and does not represent an official position of Donald Trump or others I do not work for
  2. Low rates by cerberusss · · Score: 3, Informative

    I'm a freelance iOS developer and from what I've seen, the rates for remote work are always significantly lower than when I report for duty at the client's office. Right now I'm billing a minimum of 70 euros per hour. I won't get that remotely.

    This will be no different. The kind of client that hires remote workers, doesn't want to pay a good rate.

    --
    8 of 13 people found this answer helpful. Did you?
    1. Re:Low rates by Billly+Gates · · Score: 3, Interesting

      You know out of curiosity I clicked on one of these sites a half decade ago expecting to laugh at H1B1 company applicants with 5 years experience in Rust and Node.js etc.

      Instead found a white guy in Mexico. In Mexico?? Turns out he lives on a tropical beach and living the life :-)

      No boss, sucky city, corporate stuff. Just living and soing what he wants.

      My exwife got a job in Alaska during this time. OMG LOOVED it!! Ok maybe not by March after 7 months of winter :_)

      But money is not everything. If I could be whatever I wanted I would happily live in Alaska for the summer and be in hiking, fishing, boating heaven and Hawaii for 45 Euro and do my own thing with less pressure then sign me up. Everyone I know who chases money becomes misserable after 3 months

    2. Re:Low rates by DNS-and-BIND · · Score: 1

      This just in: markets have several levels! It's today's unwelcome education in economics. You, being in the middle, do not wish to work in the low end of the market? Well, great for you! You understand more than you let on. If you only had more self-awareness...

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    3. Re:Low rates by cerberusss · · Score: 1

      I totally agree, and the cost of living in a city offsets the decent rate I mentioned.

      My best time in the last couple of years was when I took a $300/month internship at a small startup on Bali, with housing included. Office hours between 11 AM and 4 PM, swimming pool at the back of the office, and the office basically consisted of two large tables under a giant gazebo, with two fibers coming in.

      I actually had to cry when I got on the plane back to Europe, but my SO was pregnant and did not (still does not) want to move.

      --
      8 of 13 people found this answer helpful. Did you?
    4. Re:Low rates by Anonymous Coward · · Score: 0

      I work remotely in a small town by the beach in Japan. It's a very lovely place. It's cheap too. What I lose in pay, I make up for in cost of living. My wife runs the consulting company and I write code. I do enough business to keep us both paid a comfortable wage for the area.

      The downside is actually that remote work is hard and lonely. Don't get me wrong, I like this lifestyle, but it definitely wouldn't be for everyone. You have to be happy being alone for most of the day and never making friends at work. You have to be happy not having much of an input into overall decisions in the business because everything happens on the other side of the world in another time zone. If you are *lucky* someone will remember to fire off an email to you to tell you what's going on. You have to be committed to doing those other things in your life, because if you let it slide (and put in overtime at work instead, for instance) it's going to be all downside with no upside.

    5. Re:Low rates by Anonymous Coward · · Score: 0

      I actually had to cry when I got on the plane back to Europe, but my SO was pregnant and did not (still does not) want to move.

      Wait, how long did you say you were at this job before your SO got pregnant?

  3. First time submitter? Hope it's the last time too. by Hognoxious · · Score: 2

    Looks like another excuse for low-balling rates. Hey, you stopped typing for 30 seconds, I want 10% off!

    P.S. Don't you think you should have included a link to Live Coding itself?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  4. I couldn't go for this by cyber-vandal · · Score: 1

    I'd have to use much less profanity in my comments and variable names.

  5. Good luck by Anonymous Coward · · Score: 0

    with that.

  6. inb4... by Anonymous Coward · · Score: 0

    "wtb: video of screen of professional programmer working. prefer 4+ hour productive sessions no breaks"

  7. This is like... by DevYogi · · Score: 1

    Uber-ification of software development. This trend should catch on...IMHO.

  8. ... A gimmick by Reibisch · · Score: 1

    Hourly contract is/was the 'Uber-ification' of software development. This is nothing more than a gimmick.

    Anyone who has enough knowledge to observe someone code and understand what's the developer is doing has better things they could be spending their time on. Anyone who doesn't have that knowledge won't be able to tell the difference between the developer toiling on the work they were contracted for or on a personal pet project.

    1. Re:... A gimmick by DevYogi · · Score: 1

      Hourly contract is just like renting the car and the driver. Hourly contract has no transparency. Whether someone understands what the developer does, is not of relevance. Humans and businesses want control, transparency and dynamic developer environment. Something like a start-up with no clue on what they want to do, but would like to develop software for their business as the developer "types out the code". They travel from Point A to Point B with one developer and can go to Point C with another developer. Hailing a developer to do something is a good way to figure out things at lower cost. I do not think, till now, remote software development allows "hailing" a developer.

    2. Re:... A gimmick by Reibisch · · Score: 1

      Humans and businesses want control, transparency and dynamic developer environment.

      Buzzword bingo started: you have 3 squares so far. Are you a fresh MBA grad? WTF does 'dynamic developer environment' even mean in this context? Fuck that, what does it mean period?

      Something like a start-up with no clue on what they want to do

      Just... what? A start-up with no clue on what they want to do? Why did they form a 'start-up'?

      ... would like to develop software for their business as the developer "types out the code". They travel from Point A to Point B with one developer and can go to Point C with another developer.

      You've described a situation where salary-, hourly-, task-based contracts already provide a solution. Adding the ability to 'watch a developer code' add nothing to shops that need to go from A to B to C.

      Hailing a developer to do something is a good way to figure out things at lower cost.

      Again... What? If you need someone to 'figure out things' and watching someone code as your 'lower cost' option is your 'best' option, you're fucked. Full stop. When a task is so difficult that you need to find someone to teach you how to solve a problem while watching them type, congratulations: you've just spent their fee *and* at least one person's salary/time to watch them type. And you may not even have a solution. 'Hard problems' of this sort are not something that can be solved in discrete 'code watching' sessions.

      I do not think, till now, remote software development allows "hailing" a developer.

      There are eleven million task-based software development websites. Go find one of them. They'll be cheaper than a task-based service that also requires a developer to surrender a view of their screen.

    3. Re:... A gimmick by Anonymous Coward · · Score: 0

      Anyone who has enough knowledge to observe someone code and understand what's the developer is doing has better things they could be spending their time on

      You don't watch them working on your problem 100% of the time. You watch them solve another problem or do their hobby for a short while to determine if they have a reasonable mindset and skillset to match who you are looking for, and you can easily ask questions. It is basically a remote interview process. You could also use it to check in on their progress from time to time.

  9. er, task-based! by Reibisch · · Score: 1

    Gah, I meant task-based contract is the 'uber-ification' -- not hourly.

  10. My opinion about all this by CustomSolvers2 · · Score: 5, Interesting

    This is the second article about Live Coding here; in fact, I wrote a comment to the previous article. Back then, I said that the idea seemed interesting and was about to test it for self-promotional purposes. Finally, the experience turned to be HORRIBLE.

    I was expecting it to be a business run by/addressed to programmers, genuinely interested in promoting programming; an assumption which was quickly proven wrong. Although I never felt any kind of interest in watching someone writing code, I believed ideas on the lines of "newbies find it very helpful".

    This experiment didn’t last for too long and that's why I am not completely sure about the target audience. In any case, I met quite a few completely-clueless people not knowing anything about the given programming language, even about programming in general; asking random things and pointing out irrelevant problems. There were also cheerleaders, trying to trigger participation in the less-appealing-to-me way possible (e.g., talking about random things without caring about the code being written at all). There were also some people interested in knowing what was going on, but they were a minority.

    As far as my intention was just taking this as an excuse to have videos where I was coding (like a picture of mine: a complement to my online references), I didn't mind too much the aforementioned issues. The worst part was the site itself (and their staff). They are certainly not programmers, but want to manage the whole thing their way. The result? I found the overall service/site very unappealing at different level (support, features, control on your videos, etc.). Imagine that Slashdot is being completely managed by Dice people (including moderation)!

    My recommendation to any programmer planning to go down that road (mainly with Live Coding): this is not a site/concept managed by programmers. Accept this point and you might even enjoy the experience (so many people, so many minds).

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
    1. Re:My opinion about all this by vix86 · · Score: 1

      I never liked LiveCoding. I found out about this whole "watch people code live" thing from the article sometime back about /r/watchpeoplecode and the people on Twitch that were doing it. It was interesting way to see what people were doing and even landed me a part time job doing some freelance coding with someone on the side.

      Somewhere around the time that /r/WatchPeopleCode was gaining some traction, LiveCoding seemed to pop up out of no where and started to aggressively try and recruit people that were streaming on twitch. They, or rather the primary founder it would seem, would "stalk" people (looking for their primary email contact, or hitting them up on social media) and constantly email them trying to get them to switch to LiveCoding. Some of the people that actually did try it out found themselves trying to be forced to stream on schedules. Apparently there was/is a spreadsheet that had time blocks that specified when they should be streaming. They weren't even asked if they wanted to participate in something like this.

      LiveCoding has never been particularly user friendly for either the streamer or the viewers. I'm not sure if they've changed it now, but months ago, you still had to register in order to be able to see streams. This just drives away any one thats interested. The founder gave the excuse that this was due to bandwidth concerns or whatever. In addition, they set up focused advertising which would appear on /r/watchpeoplecode to draw people to their site. I always figured they were in this for the money, but I never saw the angle until now. I guess its try and get in on the freelance market or something.

  11. Coder all day long? I wish. by vmfedor · · Score: 4, Insightful

    Okay, sure, you can watch a coder in real time, but most of the time people don't need a coder, they need a developer. A developer has project management and other "soft" skills. Coding is the hammer and the nails... you have to know what you're creating before you start to build it. Most of the time you would see the developer typing up emails, creating diagrams and flow charts, writing executive summaries, managing their agile tracker, consulting on a conference call, researching documentation, etc.

    I'm so tired of people thinking that software engineering is about coding. It isn't about coding, it's about developing real-world technical solutions of which coding is a relatively small part.

    --

    I like my women how I like my sugar.. granulated.

  12. Crappiest idea ever. by AchilleTalon · · Score: 1

    Most stupid idea I ever seen. I can't believe decent programmers are going this path. Just another way after the 'coding for pizza' idea to devaluate developers' skills and hold them in contempt.

    --
    Achille Talon
    Hop!
    1. Re:Crappiest idea ever. by Anonymous Coward · · Score: 0

      We already on this path, and to be honest, accelerating it would only be a good thing.
      Every trend has a peak and after we reach it, things will stabilize.

      Until then ... we'll have massive security holes, shoddy apps and a "booming" tech industry.

  13. So much for keeping your IP by Anonymous Coward · · Score: 0

    So the guy you hired is working on your code while someone else can look at it?
    Can't think of any client that would ever want nor allow that!

  14. It is Stupid. by jellomizer · · Score: 1

    Software Development is a professional trade, and Software Developers should be treated like professionals.
    I am sick of these methods to try to monitor our work like a fast food employee.
    I have a reputation for being having quick turnaround in my code, and I get called in when others say it cannot be done. this sometimes bites me back when someone is harder than normal so it will take me a week to do something, but Software Development is a skill, and sometimes you need to take extra time and though into a solution, The solution is often just 2 or 3 lines of code, perhaps just a change in parameter, or fixing of a math formula, or fixing a parenthesis. But still it take a long time to look at it, see why it failed, figure out how it passed in the first place. Evaluate what downstream effect the fix will have... A lot of work for something I can type in 3 seconds.
    I have never worked in a place where there was rampant goofing off, or just people not doing work. They were always professionals about the work, with the same amount of goofing off and idle time, that other units have such as finance and accounting. You know those other professional level positions.

    The issue is the demand for coders in job sectors that have limited use of professional employees, so Mr. Boss man thinks he can treat them like any other minimum wage employee, and have easy/real-time measurements on results. While for professional software developments the metrics are harder to calculate and take time to show their results.
    The product may be 2 month late, but it works perfectly vs on time and has a lot of issues that takes 10 months to fix.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  15. Lose-lose situation by Anonymous Coward · · Score: 1

    So, the coder only gets paid at the end once the project is complete, but the client has to pay hourly rates with no guarantee how long it will take at first? Without a decent contract written up front, I can see a lot of projects getting scrapped part way through, shafting the coder, and others costing way too much for the client.

    1. Re:Lose-lose situation by oakgrove · · Score: 1

      I'm guessing some kind of rating or feedback system like how ebay does it might be in order.

      +++_-_WOULD CODE FOR AGAIN!!1-_-+++

      Or some shit.

      --
      The soylentnews experiment has been a dismal failure.
  16. Re:Coder all day long? I wish. by Anonymous Coward · · Score: 0

    Yeah, I can't believe how many places these days will give you these stupid online code questions where they ask you to write something and watch you live and then use that as the sole piece of information as to whether they want you to come for an in person interview. And then they complain about how everyone they hire is just "not quite the architect they were hoping for" and let them go after a few months. I see it all the time. So stupid.

  17. advertisement by Gravis+Zero · · Score: 1

    i'm just going to go out on a limb and say this is an advertisement because the first thing "alphamore" aka Alphamore Media Solutions did after creating an account was submit this story. despite their address being created on 2015-06-23, they claim to have completed 1,412 projects and written 712,094 lines of code.

    seems legit, right? -_-

    --
    Anons need not reply. Questions end with a question mark.
    1. Re: advertisement by alphamore · · Score: 1

      Hello, No affiliation with any parties whatsoever. The numbers you speak of are actually modest, there is life before domain registration so says the white hair growing out of my ears.

    2. Re: advertisement by esmithsta2 · · Score: 1

      Hello, No affiliation with any parties whatsoever. The numbers you speak of are actually modest, there is life before domain registration so says the white hair growing out of my ears.

      hee hee.i likee you

      --
      im a fixture at stack overflow
  18. No, if you don't suck at your job by Samhain138 · · Score: 1

    The kind of client that hires iOS developers is an Apple zealot too stupid to hire remote employees and pay them well (or understand anything about software engineering for that matter).
    The kind of horrible freelance you are can't get normal clients.
    iOS developers are a dime-a-dozen so people don't get stuck w/o devs and even consider hiring remotely.

    I don't know, you're stating these "facts", so so can I!
    Have you seen sites like WeWorkRemotely? Remotive?
    FULL of remote jobs at awesome companies offering really, really competitive salaries and benefits.
    Yes, even for iOS developers, knock yourself out. Glad to prove you wrong.

    I am a freelance, work remotely, charge more than twice what you do, been doing it for 9 years or so.
    Not even once, not a single potential client, has asked me for a discount or expected me to earn less because I work remotely.
    It's usually "oh, we don't work that way", and even that's really uncommon these days.

    Now, you're on slashdot so I don't expect you to understand human beings but...
    We don't work just for the money. And we want that money so we can use it for stuff that's not related to work.
    Personally, I travel all over the world all year round, and if that meant getting paid a few percents less per hour compared to being stuck in the same city and having to go to an office (read: prison with a coffee machine) and spend time in traffic or public transport, then...
    I really, really, really, realllllly couldn't care less.

    1. Re:No, if you don't suck at your job by Shados · · Score: 1

      It seems to me like it would be purely a supply and demand thing.

      If you only look at the pool of devs in a locality, you have, at most, the population within a couple of miles range of that locality. If you accept remotes, you have the entire world. And you only need 1 (or 10, or 100, or 1000, doesn't matter). Your demand is fixed, but your supply changes depending on if you want on site vs remote.

      Then you have the fact that the guy who's paying for his million dollar condo in SF/NYC/Cambridge will negotiate a lot harder than the guy who's living in upstate NY.

      Obviously, if you made a name for yourself, since highly qualified engineers are hard to find, you basically can bill whatever the fuck you want.

    2. Re:No, if you don't suck at your job by cerberusss · · Score: 1

      I have to say, it sounds extremely appealing to me. It's just that I haven't succeeded with these sites so far. They'd say stuff like: "amazing opportunity, huge budget", and the budget would actually be 5 or 10 K. I'm looking for the 30-60 K range, at the very least.

      And yes, it's not all about the money. Especially being able to pick up my daughter somewhat earlier from daycare would be a huge boon. In any case, you're saying that WeWorkRemotely and Remotive are the places to find good clients?

      --
      8 of 13 people found this answer helpful. Did you?
    3. Re:No, if you don't suck at your job by Samhain138 · · Score: 1

      When have you last checked? It's getting more and more popular, really.
      And aren't they giving away free money where you live, anyway??? ;-)

      I go over these websites mostly out of my interest in remote jobs (seeing what companies are in the game, what kind of jobs, what do they offer, etc.).
      The jobs/pay seem way more legit than what you're thinking about...
      See for yourself, and learn how to negotiate, you're a freelancer!

      The best place to find good clients is your inbox. Word-of-mouth is still the best tool.
      This kinda requires you to be great at what you do, impressing your clients and coworkers.
      You shouldn't be looking for clients, that sucks because no one's paying you for it, and it's not exactly free-time either.

      If you're not amazing at what you do (say, you prefer being a great dad than the best iOS dev on the planet?), keep in mind that $potential_remote_employer is exposed to way more devs from way more places in the world.
      Chances are, some of them are better than you and charge less than you, simply because you live in a pretty damn expensive country.
      So it's not necessarily the clients being cheap or expecting you to earn less *because* it's a remote job.
      It's probably because they're not looking at the same market as you are (which, in your city, is t-i-n-y, and the salaries are relatively high to begin with, because they just rape people out of their money with taxes over in Holland).

    4. Re:No, if you don't suck at your job by cerberusss · · Score: 1

      Thanks for some great pointers! I'm confident in my skills as a developer but I have to admit I can do better than this.

      Really appreciate your replies.

      --
      8 of 13 people found this answer helpful. Did you?
  19. The management mindset has won by Anonymous Coward · · Score: 0

    This is nothing except micromanagement to the extreme.

    If you want something built, you hire someone and ask them to deliver it. That's a contractor. Want it done a certain way, write that into the contract.

    If you're too lazy to actually write down what you want, you make a vague statement and then correct, correct, correct as the arrow flies further away from the target.

    If you're too fearful to believe in your abilities to hire a person, or your abilities to manage them, you watch them. It's not like you could recognize the difference between a person that's busy and a person that's looking busy, but you'll convince yourself that you have done your diligence.

    Our managers are sloppy. There are few milestones between start and delivery, and those milestones are rarely structured or ordered in ways that remotely make sense. For example, the first milestone will ask for 80% of the work to be done in a three tier application, and the second milestone will be styling the client with CSS.

    You mention books like the Mythical Man Month to them, and they haven't heard of it. (I don't expect them to read it, but they should at least have a synopsis of what was learned from it)

    With such an environment, every project becomes a death march, where management alternates between micromanagement and being too busy micromanaging other projects to provide direction when needed.

    This website is brilliant, but it sucks. It gives the managers everything they've been asking for, which keeps getting further from the actual delivered product.

  20. watch them to see what they need by raymorris · · Score: 2

    > they really don't know what they need, they think they do, until they see the project in action, then they will need other stuff.

    This part jumped out at me. Absolutely users rarely know what they need. Very often they'll tell you they need A. When pressed further, they'll explain that they need A in order to get to B. Which they need in order to get to C. Of course, it's much easier and more correct to just give them C, skipping A and B altogether.

      However, in my experience, if you walk over to their desk and watch them work, you can normally see what they need. That's been incredibly valuable, watching users work and seeing what they do, so I can actually see the whole process and also take note of the problems they run into.

    1. Re:watch them to see what they need by Anonymous Coward · · Score: 0

      Stakeholders commonly fall into the trap of trying to design the system themselves so they look/feel smart. Of course, said designs are usually terrible and fail to meet their underlying needs, because the stakeholders rarely if ever have any expertise in designing systems.

  21. Micromanager's wet dream by Anonymous Coward · · Score: 0

    I'm shocked my boss hasn't replaced our whole team with such people

  22. Hunt and peck. by Trax3001BBS · · Score: 1

    My luck I'd get a great programmer with no typing skills.

  23. Have fun trying to code in a goldfish bowl by Applehu+Akbar · · Score: 1

    With someone tapping the glass every few minutes to see if you react.

  24. What are you doing? by presidenteloco · · Score: 1

    Thinking.

    Can't you do that on your own time?

    --

    Where are we going and why are we in a handbasket?
    1. Re:What are you doing? by Bill+Dog · · Score: 1

      Some of my best thinking is done in the shower in the morning. Would not be pretty to watch that.

      --
      Attention zealots and haters: 00100 00100
  25. The most boring reality show ever by Anonymous Coward · · Score: 0

    Maybe with a catchy title?

  26. booo by Anonymous Coward · · Score: 0

    This is a horrible idea, I don't know how many employees think that when you are typing is the only time work as a developer is getting done. I type very fast and tend to have to sit around to figure out what I need to program to get it done. This is just going to marginalize the creative process, the intellectual portion and force developers to become robots rather than writing tapestries in digital context.

  27. Jiffy Lube? by Fnord666 · · Score: 1

    So is this an attempt to build the Jiffy Lube of coding?

    --
    'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
  28. Six Sygma Synergy by Anonymous Coward · · Score: 0

    The six sygma synergy of agile programming is undeniable.

  29. Re:Coder all day long? I wish. by Shados · · Score: 1

    It's the pendulum issue. Once upon a time, people thought all they needed was coders. They would hire anyone that could code, or even outsource the job.

    They didn't work so hot, because you actually need someone with critical thinking, business knowledge, experience, and the ability to actually engineer a system, not just code it, to keep it ticking.

    So then they go the other way. Coders are useless, I just want the tip top 1% of the 10x devs. Now, even forgetting how hard it is to find these folks, there's another problem: When you're trying to do something stupid, the engineer you just hired will actually tell you. And that hurts your ego, as a product manager, CEO, whatever. Its your job to tell how the product should be built! The fact that the guy or girl you just hired has already done the same damn thing you thought was your brilliant idea before, and will tell you better ways of doing it...that just causes friction.

    So then you realize what you really want is someone to acts on your marching orders...a coder!

    And the cycle repeats.

  30. Re:First time submitter? Hope it's the last time t by alphamore · · Score: 1

    Hello, during the posting process, had the field called for "Link to Original Source of Original Source(s)" rather than simply "Link to Original Source" of the story, i'd've obliged. I myself am not fond of the idea, but to each his own. Just a story I read moments before. Delete it, edit it, either way is fine by me. No biggie.

  31. Smell my vagina by Anonymous Coward · · Score: 0

    inhale my funky zuckersnatch, fuck yessssss

  32. Hands up by Anonymous Coward · · Score: 0

    ... a developer you've seen coding on the site ...

    So who's going to watch 'Beowulf' or 'Grendel' based on a page of the original old-English text? Or marry a woman based on a picture of her cooking? They think they're being clever; they're not. Obviously, this is aimed towards contractors but I don't want prospective employers to see me in my mum's basement wearing torn underwear, staring at a screen for 15 minutes straight. So this idea will require a lot of PR management where I only appear when dressed for work, ready to type and surrounded by privacy screens.

  33. Great idea! by Anonymous Coward · · Score: 0

    ...assuming that your task is completely mundane and similar to the worker's previous projects. Generic CRUD application? Great. Wordpress skin-and-deploy? Awesome. Something that needs actual research, thought, etc.? Prepare to be bored.

    It's the same thing with stuff like watching Notch code. He did coding competitions regularly, but they were all variations on the same theme: make a game in X hours. It's probably the same at other programming competitions, like the web-oriented ones where the winners almost certainly had planned and prototyped their idea for weeks beforehand.

  34. Just what we need by BubbaJonBoy · · Score: 1

    Add performing code monkey to my list of skills...

  35. Re:Coder all day long? I wish. by BubbaJonBoy · · Score: 1

    I never have points to mod up when I need them.
    You definitely used that hammer to hit the nail square on bro.

  36. Not coder but!.. Time. by eionmac · · Score: 1

    1 I am not a coder or programmer or computer logic problem solver but I recognize the problem immediately.
    2 I write 'words' for a living. These define consequences of compliance with {get paid!] or non compliance with [get lawsuit!] providing a 'machine to do a job'.
    3 I work in two ways, as Case A) a 'per diem fee on site' OR at same rates hours offsite where I and only I say how many hours apply. Thus offsite work often thinking time 48 hours and 30 minutes writing a single paragraph gets billed as 48.5 hours devide by 7.5 hrs/day multiplied by per diem fee; and Case B) a fixed fee for job.My guess if this will pay or not estimated at estimated hours by a per diem of 180% of billed normal per diem (attendance) fee (allows for the unknowns that come up). If fixed fee not suitable to client I refuse job.
    4 All professional jobs have as before described , thinking times, research time, learning time, solution development in the mind and then 'tool handling time' (the writing in my case). Folk get what they pay for. I get more work than I can handle so I guess my reputation for job and fees is OK. (A point I can never prove!)

    --
    Regards Eion MacDonald
  37. Kids today... by Hognoxious · · Score: 1

    Are you incapable of adding the markup for links manually? It uses those pointy lefty-righty things, they're usually down near the bottom.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    1. Re:Kids today... by alphamore · · Score: 1

      Hello, sure I can explain further. From your original comment I gather you read the Story: http://thenextweb.com/insider/... . Notice the first 2 words are "Live" and "Coding", combined together in the form of a Hyperlink. When clicked, said Hyperlink takes the reader directly to another document, in this particular case, Live Coding. Hope that helps.