|
Hehehe... My decorating skills are all home grown, not acquired from any school other than the one with the hard knocks.
Will Rogers never met me.
|
|
|
|
|
I shoot fireworks. I'm a licensed pyrotechnician and have recently moved into fireworks choreography. I've been licensed for 13 years and have worked on the Red, White, and Boom show in Columbus, OH for the last 11.
I'd say it is a blast but that would be a silly play on words.
|
|
|
|
|
Jason Gleim wrote: fireworks choreography
Oh, that's definitely going in the book.
|
|
|
|
|
If you are interested, you can see the simulation of a show I designed for a contest in May that was part of Pyrofest outside of Pittsburgh, PA. It had to be 8 to 10 minutes, our original work, and the budget under $10K. It was actually pretty challenging. http://www.finalefireworks.com/node/1219417[^]
I didn't win... came in 2nd... but still had a great time. It takes a lot of creativity to develop a soundtrack and then design the looks that you are going to put into the sky. I don't see it as much different than other creative outlets... just a lot more transient and probably louder. Still, it is a pretty big rush to work on a show and then hear 500K people cheer for your work when the last of the finale goes off.
|
|
|
|
|
That's incredibly cool, man. Although it makes sense, it never occurred to me that thee would be visualization software for pyrotechnics. I particularly liked the shift when California Girls hit, and the report punches on How You Like Me Now.
I'm in the process of putting together a new band with a computerized light show, and what you're doing is very much like designing lighting. Except yours goes bang.
|
|
|
|
|
|
S u n s h i n e wrote: They thought they could stop the train by standing on the tracks Just pile enough people on the track and eventually it'll work
|
|
|
|
|
|
Because less stupidity is not a tragedy
|
|
|
|
|
Or neither,
I am guessing that these kind of "silly" and grave mob attacks are a sign of the rise of Anarchism [^]as a global "power".
It is a paradox that paradoxes would actually exist in reality.
That means of course that they don't exist.
However, they do!
∫(Edo )dx = Tzumer
∑k( this.Kid) k = this. ♥
|
|
|
|
|
The accident was tragic, but perhaps the stupidity of the response was more so.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Neither. Their aim was to stop the train and that Train looks stopped to me. I think the word to describe it is 'Success'.
|
|
|
|
|
|
Both
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
S u n s h i n e wrote: Unbelievable. They thought they could stop the train by standing on the tracks? Looks like they've been watching too many movies.
It's not like we don't have our share of elephanting morons who get their cars smashed trying to cross before a train because they delude themselves into thinking it can break as fast as their car.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: they delude themselves into thinking it can break as fast as their car. I wouldn't even go that far.
I doubt anything resembling common sense even occurs to them.
It was broke, so I fixed it.
|
|
|
|
|
Whatever the stupidity is loosing human lives are always big tragedies.
.AK.
|
|
|
|
|
I just signed up to write the e-book "From Imperative to Functional Programming" for SyncFusion (same folks I wrote the unit testing e-book for, they provide these e-books free to the community), and while I've already written an article on the subject[^], I'd like some input on what you all might want to see in such a book.
Given the e-book is to be about 100 pages in length, I'd like to actually develop some sort of application or API. While I have some ideas like an orm-less SQL generator that explores computation types[^] (but without weird reflection, etc), I'd like ideas on what you'd like to see as a good working example of F#.
So here's your chance to alter the course of history, hahaha.
Marc
|
|
|
|
|
First I will be really happy to read it. I always thought Functional programming is fun Please keep us informed about the book.
Second i really like algorithms with graphs. Seeing some of them written in F# with the power of Functional programming is going to be very interesting.
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Argonia wrote: Second i really like algorithms with graphs.
Interesting - I'll give that some thought. Thanks for the feedback!
Marc
|
|
|
|
|
It's probably going to take you a hundred pages to explain the title.
Toss in a few comics, a cute story about the kids, and a few industry experience stories and you'll be cranking out a 500 page Wrox text in no time.
|
|
|
|
|
And LolCatz.
Don't forget the LolCatz!
This message is manufactured from fully recyclable noughts and ones. To recycle this message, please separate into two tidy piles, and take them to your nearest local recycling centre.
Please note that in some areas noughts are always replaced with zeros by law, and many facilities cannot recycle zeroes - in this case, please bury them in your back garden and water frequently.
|
|
|
|
|
I can haz function?
|
|
|
|
|
Dude, I didn't know you were writing books these days. Awesome! Man, I need to get out more often.
Do you prefer writing the shorter eBooks or do you want to start getting into the traditional tech books? I'm back to writing for Apress, be happy to ask my editor who the right person to point you to would be if that's something you want to do.
|
|
|
|
|
Since your book will only be about 100 pages, you have to be concise on what you're including, but there are a couple of important things that books on functional programming for non-functional programmers are always missing.
1. A brief history of why functional programming was created and what problems it was originally meant to solve.
2. A highlight of real-world coding problems that functional-style programming expresses a lot better than imperative-style programming. Authors like to show both ways of solving insignificant problems but then leave out an answer to the question "Which real tasks are best done with functional programming and why?"
|
|
|
|