relative/resident expert (questionable on wine and c++):
beekeeping
sausage making
beer brewing
C++/C#
Actionscript 2 and 3
Criterion Collection
Sonoma and French wines?
-Ben
> --
> You received this message because you are subscribed to the Google Groups
> "Stir-fry Start-ups" group.
> To post to this group, send email to stir-fry-...@googlegroups.com.
> To unsubscribe from this group, send email to
> stir-fry-start-...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/stir-fry-start-ups?hl=en.
>
You've been a lot more of it recently...
I have a reservoir of knowledge, of
unknown depth!
Don't even *think* about it with c.
We should compare notes.
BTW, the hard thing about all this
web2 application programming is you
need a lot of tools to test effectively,
and that they're scripted instead of
compiled.
-d
--
Web Zero to Web Hero in 1 Weekend
http://website-in-a-weekend.net/
http://twitter.com/websiteweekend
http://www.linkedin.com/in/davidmdoolin
--
You received this message because you are subscribed to the Google Groups "Stir-fry Start-ups" group.
To post to this group, send email to stir-fry-...@googlegroups.com.
To unsubscribe from this group, send email to stir-fry-start-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/stir-fry-start-ups?hl=en.
I used Boost, DirectFB and C++ compiled for MIPS. We didn't have a
reliable gdb or gdbserver, so printf was our only debugging tool.
Debugging multi-threaded apps with printf alone makes you design
better.
I agree about the Web2 stuff. I've been dealing a lot lately with
.NET and wondering why it's so easy to read, but so hard to
write...because it takes great searching skills to find the function
they already wrote for you that slows down your app by 2% per call.
Testing is not what it used to be, but automated tests make things a
lot easier. Especially for massive online or Facebook apps.
-Ben
(For the casual reader, a good, well-integrated
test harness compensates for lack of documentation,
and has the side benefit of ensuring your API is
usable. These are reasons alone to write test
code, never mind the actual tests.)
I could segue into a rant. I'll pass. For now.
There's also nothing like forcing developers into your management
paradigm. By this, I mean Agile.
-Ben
-B