Jackie Goldstein's Weblog - All Comments

re: How Clients Negotiate with Software Vendors

Mitchell — Wed, 01 Jul 2009 20:55:43 GMT

Priceless

I???m a VB ! | rapid-DEV.net

I???m a VB ! | rapid-DEV.net — Tue, 30 Jun 2009 19:30:56 GMT

Pingback from I???m a VB ! | rapid-DEV.net

I???m a VB ! | Nexo IT - Information Technology News

I???m a VB ! | Nexo IT - Information Technology News — Tue, 30 Jun 2009 18:05:29 GMT

Pingback from I???m a VB ! | Nexo IT - Information Technology News

I???m a VB ! | I love .NET!

I???m a VB ! | I love .NET! — Tue, 30 Jun 2009 10:16:13 GMT

Pingback from I???m a VB ! | I love .NET!

I???m a VB ! - Jackie Goldstein's Weblog

I???m a VB ! - Jackie Goldstein's Weblog — Tue, 30 Jun 2009 09:36:12 GMT

Pingback from I???m a VB ! - Jackie Goldstein's Weblog

re: Using Speech Recognition to Program in Microsoft Visual Studio

Rohit — Mon, 29 Jun 2009 06:35:56 GMT

This is sweet! I would definitely buy it once it had a little polishing!

??????????????????, ??????????????????, ?????? ?????????????? ????????? | Coded Style

Wed, 10 Jun 2009 10:47:18 GMT

Pingback from ??????????????????, ??????????????????, ?????? ?????????????? ????????? | Coded Style

re: Using Speech Recognition to Program in Microsoft Visual Studio

Bjarki — Tue, 09 Jun 2009 10:02:48 GMT

Nice job.

When the user will be fluent with this he can just "wirte" a program by talking in to a dictaphone (recording tool) and play it fast back to the computer, and there you go a program made on the Beach or anywhere else :)

and yes Build command wood be nice (with sound conformation) and undo command also :)

keep up the good work.

re: Using Speech Recognition to Program in Microsoft Visual Studio

Dave Langford — Tue, 09 Jun 2009 06:51:52 GMT

Cool idea!

Although could get annoying in an open plan office...

re: Using Speech Recognition to Program in Microsoft Visual Studio

jnhill — Mon, 08 Jun 2009 19:32:55 GMT

Yes, interesting. Definitely much slower than typing, but I've sometimes wondered what I would do if I were injured and could no longer keyboard efficiently.

I could see this being helpful to someone who is, say, on an hours-long drive and wanting to get some work done, maybe if stricken with a coding bug. That got me thinking about a feedback mechanism so you'd know that the input was accepted, which in turn made me realize that this would also be essential for the visually impaired.

Perhaps the machine could immediately read back added code (optionally, of course), read out intellisense options, narrowed by spoken letters, etc. Allowing completely screen-free editing would also allow more battery life from notebooks, and it would allow me to code even as a vehicle passenger, whereas reading always makes me carsick.

Additionally, it would be great to be able to say "repeat" instead of repeating the same sometimes-lengthy command two or more times, to "begin[/end] recording" to create small temporary macros.