sparks wrote:
You can see those painstaking days where one tiny thing has to be changed in a hundred files and the visualisation just explodes with the list of edited file names!
Although CTRL+F does exist
Offline
sparks wrote:
This is a really cool visualisation! It's amazing at the end too, when there's just an explosion of new files. You can see those painstaking days where one tiny thing has to be changed in a hundred files and the visualisation just explodes with the list of edited file names!
It looks really cool when that happens. It seems like the work goes really slowly for aaages... and then there's suddenly a flurry of activity as they make progress again. I wonder why — is software development in general like this? Maybe the pauses are where they were making design decisions...
Offline
Yes!
As I said on the Vimeo page, I love the part at the end where a new branch literally unfolds out of nowhere!
Offline
ProgrammingFreak wrote:
stevetheipad wrote:
Wow, awesome! I like it, but was hoping for some more actual screenshots.
Yeah, I was thinking that's what it would be too.
Me too. But this is also cool!
Offline
Wow, beautiful. I was thinking that to make collaboration easier, you could have a general project which members of the collab could edit and create together! It would be the Scratch program, but with voice chat and it could even show other people's cursors!
Offline
blob8108 wrote:
sparks wrote:
This is a really cool visualisation! It's amazing at the end too, when there's just an explosion of new files. You can see those painstaking days where one tiny thing has to be changed in a hundred files and the visualisation just explodes with the list of edited file names!
It looks really cool when that happens. It seems like the work goes really slowly for aaages... and then there's suddenly a flurry of activity as they make progress again. I wonder why — is software development in general like this? Maybe the pauses are where they were making design decisions...
The visualization is cool, but the changes shown don't always correspond to the work. For example, the big explosion at the end was caused by the addition of code imported from the open-source forum project we're planning on using in Scratch 2.0. At that time all we did was copy and import some stuff, but the viz. makes it look like we did nothing but drink coffee and hammer out code for like 3 days straight.
A long time ago they used to pay coders per line of code, but then they realized that was a bad idea. You just get a lot of code that could be made shorter.
So even a subtle small change could reflect a lot of time, energy, and thought. But the viz doesn't show that.
Offline
blob8108 wrote:
Magnie wrote:
I see Python!
Maybe I'll be able to understand it and maybe code something!
The video was cool, only problem was I couldn't see all the file names very well. I saw 'views.py' most often. Out of curiosity, what is that?I think they're using the Django web framework. In Django, views.py is where you put all your views! Views handle HTTP requests and return a response (a web page, for example). You usually have a specific view for each kind of request. Basically, they're where most of the application logic goes.
Yep, quite right!
Offline
Lightnin wrote:
blob8108 wrote:
Magnie wrote:
I see Python!
Maybe I'll be able to understand it and maybe code something!
The video was cool, only problem was I couldn't see all the file names very well. I saw 'views.py' most often. Out of curiosity, what is that?I think they're using the Django web framework. In Django, views.py is where you put all your views! Views handle HTTP requests and return a response (a web page, for example). You usually have a specific view for each kind of request. Basically, they're where most of the application logic goes.
Yep, quite right!
That's what I thought.
Offline
Lightnin wrote:
blob8108 wrote:
Magnie wrote:
I see Python!
Maybe I'll be able to understand it and maybe code something!
The video was cool, only problem was I couldn't see all the file names very well. I saw 'views.py' most often. Out of curiosity, what is that?I think they're using the Django web framework. In Django, views.py is where you put all your views! Views handle HTTP requests and return a response (a web page, for example). You usually have a specific view for each kind of request. Basically, they're where most of the application logic goes.
Yep, quite right!
Makes sense! Cool!
Offline
That Fernando guy looks like he's been working real hard!
Also looks like a lot of the base of the website is written in Python?
Offline
What is the visualization representing? I know it's the Scratch Website, but how is the visualization supposed to tell us anything about the development of the website besides showing dots of files?
Last edited by TorbyFork234 (2012-04-24 22:26:39)
Offline
blob8108 wrote:
It seems like the work goes really slowly for aaages... and then there's suddenly a flurry of activity as they make progress again. I wonder why — is software development in general like this?
Have you ever watched a building being built? It's the same thing -- nothing seems to happens for a month, and then one day the whole frame is up, then another month of nothing, then the walls appear, etc. Probably all engineering projects are like that.
Offline
Lightnin wrote:
A long time ago they used to pay coders per line of code,
Are you sure about this? I got my first job (at IBM) in the summer of 1965, and I certainly wasn't paid by the line. (We had a time clock; I punched in at 8:30am and punched out at 5:12pm, and no, not because it's a power of two. A long story for some other thread.)
A few really ancient computers used a rotating magnetic drum as their main memory, and people programmed them in machine language, and part of every instruction said where on the drum to find the next instruction, because the programmer was supposed to work out exactly how long each instruction would take (they weren't all the same!) and exactly how far the drum would have rotated by then, so the next instruction would just be coming up when needed. I can imagine that maybe those programmers might reasonably be paid by the line, but I think even they had a fixed salary.
Offline
Lightnin wrote:
blob8108 wrote:
sparks wrote:
This is a really cool visualisation! It's amazing at the end too, when there's just an explosion of new files. You can see those painstaking days where one tiny thing has to be changed in a hundred files and the visualisation just explodes with the list of edited file names!
It looks really cool when that happens. It seems like the work goes really slowly for aaages... and then there's suddenly a flurry of activity as they make progress again. I wonder why — is software development in general like this? Maybe the pauses are where they were making design decisions...
The visualization is cool, but the changes shown don't always correspond to the work. For example, the big explosion at the end was caused by the addition of code imported from the open-source forum project we're planning on using in Scratch 2.0. At that time all we did was copy and import some stuff, but the viz. makes it look like we did nothing but drink coffee and hammer out code for like 3 days straight.
So even a subtle small change could reflect a lot of time, energy, and thought. But the viz doesn't show that.
Ah, I see! I should've guessed it didn't match with actual progress...
A long time ago they used to pay coders per line of code, but then they realized that was a bad idea. You just get a lot of code that could be made shorter.
I've heard of this. It seems very silly. There was a story where some coder optimised a function, reducing it by about a hundred of code; so had to write "-100" as the number of lines of code he'd written that day.
Offline
bharvey wrote:
blob8108 wrote:
It seems like the work goes really slowly for aaages... and then there's suddenly a flurry of activity as they make progress again. I wonder why — is software development in general like this?
Have you ever watched a building being built? It's the same thing -- nothing seems to happens for a month, and then one day the whole frame is up, then another month of nothing, then the walls appear, etc. Probably all engineering projects are like that.
Ah, but is software development really engineering?
Cool video! I see what you mean — it all happens very suddenly...
Offline
jji7skyline wrote:
That Fernando guy looks like he's been working real hard!
Also looks like a lot of the base of the website is written in Python?
That's Champika - lead developer of the Scratch website. And yes, *she* has been working real hard.
bharvey wrote:
Lightnin wrote:
A long time ago they used to pay coders per line of code,
Are you sure about this? I got my first job (at IBM) in the summer of 1965, and I certainly wasn't paid by the line. (We had a time clock; I punched in at 8:30am and punched out at 5:12pm, and no, not because it's a power of two. A long story for some other thread.)
Now that you mention it, I'm not sure about this at all - only sure I've heard it mentioned, but only in passing. Come to think of it, it could certainly be a kind of urban legend.
Last edited by Lightnin (2012-04-27 21:28:50)
Offline
Lightnin wrote:
bharvey wrote:
Lightnin wrote:
A long time ago they used to pay coders per line of code,
Are you sure about this? I got my first job (at IBM) in the summer of 1965, and I certainly wasn't paid by the line. (We had a time clock; I punched in at 8:30am and punched out at 5:12pm, and no, not because it's a power of two. A long story for some other thread.)
Now that you mention it, I'm not sure about this at all - only sure I've heard it mentioned, but only in passing. Come to think of it, it could certainly be a kind of urban legend.
I read a question and answer topic on another forum (which isn't approved here, so I won't link to it) but, it quotes Steve Ballmer, an IBM programmer:
".... if we have - a developer's got a good idea and he can get something done in 4K-LOCs instead of 20K-LOCs, should we make less money? Because he's made something smaller and faster, less K-LOC. K-LOCs....." which makes us assume he was paid per line of code.
Offline
jji7skyline wrote:
That Fernando guy looks like he's been working real hard!
Also looks like a lot of the base of the website is written in Python?
The entire website's gonna be written in Django, an implementation of Python.
Last edited by SJRCS_011 (2012-04-28 07:14:05)
Offline
blob8108 wrote:
Magnie wrote:
I see Python!
Maybe I'll be able to understand it and maybe code something!
The video was cool, only problem was I couldn't see all the file names very well. I saw 'views.py' most often. Out of curiosity, what is that?I think they're using the Django web framework. In Django, views.py is where you put all your views! Views handle HTTP requests and return a response (a web page, for example). You usually have a specific view for each kind of request. Basically, they're where most of the application logic goes.
So they're doing it again... from scratch?
(geddit?)
Bad pun, I know.
Last edited by Dinoclor (2012-04-30 20:54:58)
Offline
Don't use Internet!!!
Offline
Pikapika12 wrote:
Don't use Internet!!!
And what exactly is your reason for using the Internet to tell us not to use the Internet?
Offline
videogame9 wrote:
Pikapika12 wrote:
Don't use Internet!!!
And what exactly is your reason for using the Internet to tell us not to use the Internet?
Loool XD
Hypocrisy these days -_-
Offline
Dinoclor wrote:
So they're doing it again... from scratch?
(geddit?)
Bad pun, I know.
...
I think they're rewriting the whole site, yes...
Offline
videogame9 wrote:
Pikapika12 wrote:
Don't use Internet!!!
And what exactly is your reason for using the Internet to tell us not to use the Internet?
They might put the programmer online!!!!
Offline