Watching People Code Is Becoming an (Even Bigger) Thing
itwbennett writes: Faithful Slashdot readers may recall the story of Adam Wulf, who spent two weeks live-streaming himself writing a mobile app. The phenomenon has quickly become thing, by which we mean a business. Twitch.TV, Watch People Code (which is an offshoot of the subreddit by the same name), Ludum Dare, and, of course, YouTube, are bursting with live or archived streams of lots of people writing lots of code for lots of different things. And just this week, Y Combinator-backed startup Livecoding.TV launched. The site has signed up 40,000 users since its beta went live in February, but unlike the other sites in this space what it doesn't have (and doesn't have plans for) is advertising. As co-founder Jamie Green told ITworld: 'We have some different ideas around monetisation in the pipeline, but for now we are just focussed on building a community around live education.'
This is even worse than a stream watching someone play a game. Who wastes their time with these things?
If you want to improve your coding skill you're better off practicing and reviewing code written by those more experienced than you, not watching someone "in the act" of doing it.
Soon you'll be able to pay to view people using the toilet.
>> We have some different ideas around monetisation in the pipeline, but for now we are just focussed on building a community around live education
Translation: we are going to be ad-free to grab as many users as possible until we finalize the sale of the company to an appropriate advertiser. (That's pretty much how these start-ups work.)
Nothing more to say. Ain't no one watching me code.
Sounds like this could be the new standard for the CIA interrogation rules. Much more humane than water boarding. Just as brutal.
Interesting idea. I actually like the concept.
Why is this even a thing?
an thing.....AN thing....AN THING
As the OP said - if you want to learn to code then review and practice. Watching is pointless.
Now you can watch some fat ass eating Cheetos and drinking Mt. Dew with some occasional key punching!
Chrunch, chrunch, chrunch, slurp, nom, nom, nom,"See this is how you create a C# class", BELCH. Chrunch, chrunch, "when you look at this browser tab, it...oops", (closes pron tab), " we'll edit that out right?", chrunch, chrunch, "see how this is so much better than Java or Objective C!", FART.
People who enjoy watching paint dry might be interested in this.
Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
watching fuckboys
I recently had my first experience with a form of pair-coding, with another engineer looking over my shoulder while I explained an API he would be working with. It was unnerving at first but after a while I almost found a flow. I gained something by using my left brain to verbalize what I was doing with the very right-brain task of visualizing algorithms and data structures. I will probably be repeating this.
As a viewer, it's about learning technique and thought processes. Identifying issues, attempting a particular thought process, only those that provide a strong narrative to the work they are doing will be likely "stars". Watching how good programmers (assumption) deal with their environment and the typical problems they face. Seeing how people top down or bottom up write code is very interesting (within limits).
As a broadcasting coder, it takes a fair amount of personal confidence to do it, particular in this field. Having to verbalize what you are thinking and how you are considering the problems in front of you is actually quite challenging. Those that do well in the broadcasting scene will most likely be strong professionally as well.
That said, I personally don't understand the fandom about broadcast games to the level that it has taken. I get the benefits, but I don't get the market.
Isn't all the code you see in these videos effectively open source? How do you even convey license terms to some who is looking over your shoulder remotely? I hate to scream "lawyer", but I get the feeling there will be all kinds of legal issues popping up.
Arrive at office. Read email. Get coffee. Figure out what I need to code today. Start a for loop. Change CDs. More coffee. Flesh out for loop. Look up String API, find a method better than what I was after. Scrap everything. Lunchtime!
/.. Go home.
Collaborate with a colleague. Get a Mountain Dew. Change CDs. Write glue code to make shiney new String API do what's required. Waste an hour explaining something basic to some marketing dude in a different state. Get code to compile. Scratch butt. Test/debug. Change CDs. Check working code into git. Figure out what needs to be coded next. Manager enters office, informs me requirements have changed and what I just checked into git is now wrong. Read
Just wait until I launch my "live streaming people entering usernames and passwords" site launches!
SJW's don't eliminate discrimination. They just expropriate it for themselves.
There will be a channel to watch people watching other people code. I mean, just look at them, the way they watch the coder with such intensity!
Pretending this is my office full of bitter coworkers..
I've actually done something similar to this in the workplace before and found it to be very effective. Basically I scheduled a meeting for the last hour or so of the workday Friday and invited the other developers to come jump on with me. I shared my screen, we had an open mic, but basically I talked through what I was doing and they had a chance to see how my thought process works and also to make suggestions or ask questions. It turned out to be a good chance for the more junior folks to learn from me and some of the other experienced developers and at the same time it made us think about what we were doing at a deeper level, which is something you can get complacent in after you've been doing it a while.
This is something I did for several weeks in a row, but the last time was at least two years ago -- and yet as recently as last month I've had some of the folks that participated bring it up and comment how much they learned from it. If you think about it, it's basically pair programming on steroids.
Someone will always fill a specific slot.
I had a college roommate who kept his keyboard on the floor and typed out term papers with his long toes.
Set up a screen share and let a few hundred people kibitz while you're trying to work. Imagine all the helpful advice you would get.
"Work is fascinating; I could watch it all day." Or the Kyle Kinane bit about Ice Road Truckers.
If you are broadcasting your code live to millions (or hundreds) of people, can you still claim copyright? If you performed it in public it would seem anyone could use it.
I would assume you wouldn't use this service to flesh out your world changing video encryption code (you know, that 'middle out' idea you had)...
Comment removed based on user account deletion
Comment removed based on user account deletion
the clueless PHB who is looking for the small bits of down time so they can dock the coders pay.
I haven't seen much problem solving and thought process on the few I watched. It was mostly "google: how to get current mouse position in Unity"
Start one of the Editor only streams on one of your monitors in full screen where the boss can see. Surf Slashdot on the other.
Suborbital [spaceflight] is the special olympics of spaceflight. - Rei
Give me the fixed cell VT102 (yes, I need a printer) font any day.
Also it is much better for code.
I spent 4 weeks thinking, and then I coded 22,000 lines of C++ in about two weeks.
Ended up in wrist braces.
The code was worth it.
I'm going to make a website with nothing more than a blank white screen and call it - Watching Paint Dry
I'll follow up that up with a sequel site with a still image of a pot filled with cold water titled: Watch a pot of water come to a boil
Side Comment: why slashdot.org is the only site not allowing to edit your posts?
Errors are less of a problem than revisionist history.
And your code directly from your head just compiles and does what you expect with every permutation of inputs the first time around?
For my 22K of code...
Yes. 3 bugs.
I'm not going to knock it till I try it. I have watched people at work before and learned little things.
Did the flue fall on you and hit you in the head?
Or did you get stuck in it trying to climb out of your life?
Yeah, a lot of experienced coders will say this is not where coding really happens. Say that you want to see someone's work flow in Emacs or how to make a python/django (web framework) website for the first time. This bridges a lot of gaps in knowledge and experience. If I could have simply seen which editors people were using and how they switched between coding and testing and revising, it would have saved me many hours of trial and error. Now, of course, actual "coding" meaning the design and the implementation happen in your mind, but that doesn't mean this isn't a wonderful learning tool. Although, I do find it really funny that they stream the music people are listening to. Sure, maybe it boils down to watching other people google the same stuff I would, but I still think that in the field of coal you'll find a few diamonds in the rough. This might even be a good tool for psychologists because we can clearly see the ability to concentrate on a given task with the omnipresence of the web.