Posts

Showing posts with the label DEVELOPMENT

no code development

No-code development is a revolutionary approach that empowers individuals and businesses to create applications without writing traditional code. It leverages visual interfaces, drag-and-drop components, and pre-built templates to streamline the development process. This paradigm shift democratizes software development, making it accessible to a wider audience beyond professional programmers. The benefits of no-code development are manifold. It accelerates development timelines, as applications can be built in days or weeks instead of months or years. This agility is crucial in today's fast-paced business environment. Additionally, no-code platforms reduce costs by eliminating the need for large development teams and expensive coding resources. This cost-effectiveness makes it an attractive option for businesses of all sizes. Furthermore, no-code development fosters innovation and collaboration. Non-technical users, such as business analysts and domain experts, can actively partici...

Don’t criticize – Be a Mentor

I tweeted this concept recently and got a very positive response. As developers, business owners, partners, and gurus of various breeds, we are constantly exposed to situations where things other people do just don’t seem to fit our personal paradigm. Sometimes, a natural reaction may be to put somebody down or make a sarcastic comment. Don’t do it. Environments like this create a situation where we can excel as developers, or we can turn them into a situation where we turn out to be a complete and total ass because of our behavior towards others. No matter what the situation is, you can catch more flies with honey than with vinegar. There is NEVER a situation where putting somebody down will further the effort – not in development, not in personal interactions, not in a group. Never . What you need to do is step back, hold your breath, and think. Then, hopefully, you can find the resources in your inner being to respond in a positive manner. The results, if you work on...

Visual Studio: Enable / Disable IE Script Debugging Tool

Image
Rocky: There has already been two attempts on your life. Bullwinkle: Don't worry, we'll be renewed. If you are like me, you are always keeping your eye out for shortcuts and ways to make your life easier. One of the little annoyances of working with Visual Studio .NET is that it has no option to turn Client Script Debugging on or off – you have to open up Internet Explorer, go to Tools/Internet Options/Advanced and either check or uncheck the checkbox option. All this checkbox does is control a Registry entry, so why not just make a little .vbs script and register it as an External Tool in Visual Studio? The steps to do this are very simple. But first, you need to find out what Registry Key has your value. The key is located at HKEY_USERS\XXXXXX\Software\Microsoft\Internet Explorer\Main\ where “XXXXXX'” could either be “.default” or one of the machine user identities such as “S-1-5-19”. Once you have identified where your actual ...

Silverlight 2.0 Goodness - and IE 8.0 too!

Image
May the Flying Spaghetti Monster touch you with his noodly appendage! -- Pastafarian saying ** Silverlight 2.0 Beta 1 Plug in Runtime ** Silverlight 2.0 Beta 1 Tools for Visual Studio 2008 (Includes SDK - installs everything except Blend) ** Expression Blend 2.5 March Preview (handles Silverlight 2.0 projects) ** Expression Studio 2.0 Beta (includes Expression Web, Expression Blend, Expression Design, Expression Media and Expression Encoder.)  This release continues to enable building rich client applications with WPF and also helps designers target Silverlight 2.0 for delivering stunning web applications. ** Silverlight 2.0 documentation and links to Quickstarts, etc. All this stuff was just put out from MIX. Have fun! With version 2.0, now that I can use real .NET libraries in the browser, this is where I start getting seriously interested in Sillverlight . Once you get the bits installed, there is a very nice series of Hands On Lab s that you can download for the f...

.NET Framework Source Code Debugging is Live

Illegal aliens have always been a problem in the United States. Ask any Indian. - Robert Orben This was trumpeted several months ago mostly by Scott Guthrie, and now it is live (although not all sources and symbol files are available at present). None of this is rocket science, it's already built into Visual Studio. However, up until now there were no symbol files and sources for the BCL and related assemblies. Now there are. This is, in my opinion, not only a great debugging tool for any developer who is interested in "getting under the hood", but it is also a great learning tool. If you are not sure you understand what I'm talking about, just go ahead and "do it". The easiest way to get started with this is to follow the instructions on Shawn Burke's blog post here . Be sure to follow the instructions exactly - they are not difficult. It requires the download of a QFE to set up the debugger properly, the url is specified in Burke's post. There is...

Are You Listening, Developer? and Vista Performance

One of the biggest impediments to successful software development is communications, and the biggest part of that, in my opinion, is the ability to listen effectively . I write this not only as an instructional piece, but to remind myself that I too suffer from Listening Dysfunction (LD). I am glad to say that I'm getting better at it all the time, but sometimes I just can't seem to keep it up (the listening, that is). Your doctor generally cannot prescribe some "blue pill" for this, however - you have to fix it yourself. Have you ever been in a situation where you are conveying a concept or explaining something, and the other person constantly interrupts or "talks over" you? They're not listening. They are involved in some other agenda. Perhaps they hear what you are saying, but the comprehension is not there. Or, have you ever sent an email to somebody with several points in it, but you get a response that only addresses one point? The respondent didn...