|
Size: 909
Comment: bash guide question.
|
← Revision 6 as of 2014-12-05 20:49:46 ⇥
Size: 2925
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| = @Todd Partridge@ = Hello, my name is Todd Partridge. I've been a Linux enthusiast, documentor, and programmer since 2007. I contribute my time on the [[https://wiki.archlinux.org/|Arch Linux Wiki]] and I like to blog (Linux-Tidbits). Please be free to leave any questions or comments that you would like to. |
|
| Line 10: | Line 8: |
| ##Email: <<MailTo(you AT SPAMFREE example DOT com)>> ## You can even more obfuscate your email address by adding more uppercase letters followed by a leading and trailing blank. ... |
== About me == Hello, my name is Todd Partridge. I've been a Linux enthusiast, documenter, and programmer since 2007. I contribute my time on the [[https://wiki.archlinux.org/|Arch Linux wiki]] and I like to blog (linuxtidbits). Please be free to leave any questions or comments. == Comments/Questions == |
| Line 16: | Line 16: |
| Just read this, so sorry if replay is late. If you don't mind me asking, why was a new guide started? — [[Todd Partridge]]. The new guide is part of the Bash Academy, an initiative I started a while back to make a central location for a much more guided / academic approach to learning bash. The guide is pure HTML which sets is free from a bunch of constraints imposed by the wiki. I'm also planning an interactive mode and a "bash game" to learn all the ways in which bash can go wrong in an interactive sandboxed session. You'll notice the approach/language of the new guide is also very different from that of the old - it wouldn't be possible to do that with the current guide without essentially rewriting it. I think if you give the new guide a read, it should become quickly obvious how it's different and that this is not something the current guide could simply have "evolved into". - [[Lhunath]] I got a chance to look over your site and am very impressed with the detail and dedication that has been put into it... it is something that has much promise. However, I must say... I think our methodologies may be a good deal different. If a minute could be given for me to explain... I've written before articles, tips... at a website, over a number of years, that eventually got lost when an ISP folded. Not to get into details but the owner was diligent to try and recover... anyhow, from then on I just decided to do writing on sites I felt pretty good would be around for awhile. If it could be understood, this caution for me may not have anything to do with this situation whatsoever; however, I must mention, that conviction of otherwise would probably be unlikely. Additionally, of concern, that while I see tremendous potential in trying to create a custom instructional website, I am a bit leery of operating outside an established documentation format. The formatting and writing standards such as wiki has helps me keep focused and within my capabilities. I know these are large differences in opinions on creativity, if they are not taken in the best light, then I apologize. The effort is noble and I wish the best with it. [[Todd Partridge]] |
About me
Hello, my name is Todd Partridge. I've been a Linux enthusiast, documenter, and programmer since 2007. I contribute my time on the Arch Linux wiki and I like to blog (linuxtidbits). Please be free to leave any questions or comments.
Comments/Questions
- Hey Todd, I've noticed your interest in improving the bash guide. Are you interested in going through the guide at <http://guide.bash.academy>? Lhunath
Just read this, so sorry if replay is late. If you don't mind me asking, why was a new guide started? — Todd Partridge.
The new guide is part of the Bash Academy, an initiative I started a while back to make a central location for a much more guided / academic approach to learning bash. The guide is pure HTML which sets is free from a bunch of constraints imposed by the wiki. I'm also planning an interactive mode and a "bash game" to learn all the ways in which bash can go wrong in an interactive sandboxed session. You'll notice the approach/language of the new guide is also very different from that of the old - it wouldn't be possible to do that with the current guide without essentially rewriting it. I think if you give the new guide a read, it should become quickly obvious how it's different and that this is not something the current guide could simply have "evolved into". - Lhunath
I got a chance to look over your site and am very impressed with the detail and dedication that has been put into it... it is something that has much promise. However, I must say... I think our methodologies may be a good deal different. If a minute could be given for me to explain...
I've written before articles, tips... at a website, over a number of years, that eventually got lost when an ISP folded. Not to get into details but the owner was diligent to try and recover... anyhow, from then on I just decided to do writing on sites I felt pretty good would be around for awhile. If it could be understood, this caution for me may not have anything to do with this situation whatsoever; however, I must mention, that conviction of otherwise would probably be unlikely.
Additionally, of concern, that while I see tremendous potential in trying to create a custom instructional website, I am a bit leery of operating outside an established documentation format. The formatting and writing standards such as wiki has helps me keep focused and within my capabilities.
I know these are large differences in opinions on creativity, if they are not taken in the best light, then I apologize. The effort is noble and I wish the best with it. Todd Partridge