- No more IDEs to figure out or decide on (every CS instructor and developer has an opinion on IDEs. Great flamewars have started this way.)
- No more complex workflows like requiring source file names must follow a certain pattern, save into a specific folder, etc.
- No more projects submitted via a USB drive; If you're still doing this as a CS instructor now, change careers because you suck
- No more SDK installations or copying binaries for specific programming languages
- No more fighting a version control system; Let's face it teaching programming to freshmen or sophomores is hard enough and you still want to muddy the waters with a VCS?
- (some) Fiddles are collaborative; 2 or more students working on the same source file which makes for some interesting group project options.
- Fiddles can be shared via social networking; we already share too much of our personal life online why not your code?
- Fiddles are bookmark-able so they can be submitted as is and you can quickly see if it can run or not
- Fiddles are available for every language (some examples)
- http://www.dotnetfiddle.net/ - C# and VB.net
- http://pythonfiddle.com/
- http://jsfiddle.net/
- http://phpfiddle.org/ - complete LAMP
- http://ideone.com/ - everything else
- And yes all of them are free
Blog. Repository of ideas/solutions. Web Developer. Data Labandero. Python. Java. TypeScript. C#. Flutter apps. VB6 free since 2003!
Friday, November 22, 2013
Why use Fiddles to teaching programming
Labels:
education,
fiddles,
programming
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment