Survey Results

FirstPrevNext

Re: First things first. Nemanja Trifunovic16-Jun-04 3:10 Nemanja Trifunovic 16-Jun-04 3:10  diilbert wrote: C++ - Pure, Simple, Makes Sense. C# - Microsoft's idea of Pure and Simple I like your signature, but in all fairness, C++ is not exactly pure, and is anything but simple. Re: First things first. Gary Wheeler16-Jun-04 3:46 Gary Wheeler 16-Jun-04 3:46  Nemanja Trifunovic wrote: C++ is not exactly pure class C { C operator++(int) = 0; }; How about now? Software Zen: delete this; Re: First things first. Alvaro Mendez16-Jun-04 10:52 Alvaro Mendez 16-Jun-04 10:52  Definitely not simple. Regards, Alvaro Give a man a fish, he owes you one fish. Teach a man to fish, you give up your monopoly on fisheries. Re: First things first. diilbert16-Jun-04 14:37 diilbert 16-Jun-04 14:37  Pure: free from what vitiates, weakens, or pollutes Simple: free of secondary complications Sense: implies a reliable ability to judge and decide with soundness, prudence, and intelligence Makes sense to me anyway C++ - Pure, Simple, Makes Sense. C# - Microsoft's idea of Pure and Simple Re: First things first. diilbert16-Jun-04 14:43 diilbert 16-Jun-04 14:43  It all comes down to the fact that I hate writing C#, and do only when I have to. C++ - Pure, Simple, Makes Sense. C# - Microsoft's idea of Pure and Simple Re: First things first. Alvaro Mendez17-Jun-04 8:29 Alvaro Mendez 17-Jun-04 8:29  Why do you hate writing C#? If it's because you still love C++, I have to tell you that I don't miss it much. I don't miss the pointer/reference notation (->, *, **, &, &*), or dealing with character strings, or double-wide character strings, or BSTRs, or header files, or _tcslen, or push_back, or memory leaks, or not being able to initialize member variables where they're declared, or not being able to invoke a constructor from another constructor of the same class. What I do miss are templates (a lot), multiple implementation inheritance (a little), and default parameters (sometimes). But templates (known as generics) are coming in .NET 2.0 and they'll fill in the void for most cases. Regards, Alvaro Give a man a fish, he owes you one fish. Teach a man to fish, you give up your monopoly on fisheries. Re: First things first. Nemanja Trifunovic17-Jun-04 9:59 Nemanja Trifunovic 17-Jun-04 9:59  Alvaro Mendez wrote: What I do miss are templates (a lot), multiple implementation inheritance (a little), and default parameters (sometimes). I miss all of these, but most of all I miss RAII[^]. And keyword using is not filling the void. Re: First things first. Alvaro Mendez17-Jun-04 12:08 Alvaro Mendez 17-Jun-04 12:08  Nemanja Trifunovic wrote: And keyword using is not filling the void. Really? It fills the void quite nicely for me. You implement IDisposable, put your cleanup code inside the Dispose method, and let using write all the try/finally code for you. It's probably as close as you can get to RAII in a garbage collected language. I use it extensively, especially for things like showing a wait cursor: using (Cursor.Current = Cursors.WaitCursor) { // do some processing } Regards, Alvaro Give a man a fish, he owes you one fish. Teach a man to fish, you give up your monopoly on fisheries. It depends... Anonymous15-Jun-04 11:17 Anonymous 15-Jun-04 11:17  The answer depends on the "mission-criticalness" of the project. MS can get by with still having bugs when the software is released. NASA, Boeing, or some place like that can not because someone's lives could depend on the successful execution of the code. They do not get to release "service packs" that make everything ok. Re: It depends... TheEdgeRocks16-Jun-04 18:42 TheEdgeRocks 16-Jun-04 18:42  Couldn't a jet receive an update whilst in the air? Re: It depends... Trickster17-Jun-04 2:49 Trickster 17-Jun-04 2:49  don't think so, it would probably need a restart :p Clean Programming Under Difficult Circumstances Writing less of it for more $$$ Marc Clifton15-Jun-04 10:48 Marc Clifton 15-Jun-04 10:48  Marc Microsoft MVP, Visual C# MyXaml MyXaml Blog Re: Writing less of it for more $$$ WillemM15-Jun-04 22:06 WillemM 15-Jun-04 22:06  hmmmmmmm "Every rule in a world of bits and bytes can be bend or eventually be broken" Re: Writing less of it for more $$$ Michael P Butler16-Jun-04 1:28 Michael P Butler 16-Jun-04 1:28  Marc Clifton wrote: Writing less of it for more $$$ Absolutely. My overall aim in my life is to develop software without having to write one new line of code. We are still a million miles off that, but maybe one day. Michael CP Blog [^] It is the kind of code we write Paul Watson17-Jun-04 11:19 Paul Watson 17-Jun-04 11:19  Bloody hell Butler, you sound like an advert for the next Visual Studio .NET... :P I don't think the future is whether we write more or less code, it is the kind of code we write. I am fed up with having to write SqlConnection sqlconMain = new SqlConnection(ConnectionString); everytime rather than Get Customers With Debt from Main Database or some such. Why are we still writing structs and namevaluepairs and pointers and byte arrays? As an example; Right now I can use Dreamweaver to visually whip up XHTML compliant web-pages without writing a single line of code. They are as good as my hand coded ones, but I am quicker at hand-coding those pages than I am at dragging fiddly floating DIVs in Dreamweaver. Even with practice I won't drag right-floating DIVs faster than I can type div#News {float: right;}. regards, Paul Watson Bluegrass South Africa Ian Darling wrote: "and our loonies usually end up doing things like Monty Python." Crikey! ain't life grand? Re: It is the kind of code we write Michael P Butler17-Jun-04 12:18 Michael P Butler 17-Jun-04 12:18  Paul Watson wrote: Bloody hell Butler, you sound like an advert for the next Visual Studio .NET... It was more of a subtle plug for the work Marc is doing with MyXaml... well that was my intention. Paul Watson wrote: I don't think the future is whether we write more or less code, it is the kind of code we write. I am fed up with having to write SqlConnection sqlconMain = new SqlConnection(ConnectionString); everytime rather than Get Customers With Debt from Main Database or some such. Actually, I'm fed up with having to write a customer database. I'd much rather be able to use the database that comes with Outlook or with Sage Accounts than having to build me own. Why is it so hard for use to be able to integrate with each others applications. Why isn't there a standard component that can be bought that provides the basic customer information that I can plug into my own app and just add my custom fields. Why can't I easily hook the Make Call functionality of Outlook and redirect it to call my telephony code. Why can't I easily add a Dial button into the Sage Account screens and have it call my code. Why should I have to write something that somebody else has already done, that my customer is already using but wants to make it do something just slightly different to fit in with their business methods. We need to stop thinking of computer software as seperate applications and start writing software as platforms for others to build on. Hardware is component based, so why isn't the software built the same way. I want sofware plug and play. Michael CP Blog [^] Re: It is the kind of code we write Paul Watson17-Jun-04 21:04 Paul Watson 17-Jun-04 21:04  Completely agree, Michael. I just don't want people thinking the future is not to write a single line of code. When you use MyXAML you are writing lines of code, nice code but still code IMO. The way MS and others make "no code" out to be is drag and drop visual wizardry which makes re-use and system-wide consistency difficult. regards, Paul Watson Bluegrass South Africa Ian Darling wrote: "and our loonies usually end up doing things like Monty Python." Crikey! ain't life grand? Re: It is the kind of code we write Michael P Butler17-Jun-04 21:29 Michael P Butler 17-Jun-04 21:29  Paul Watson wrote: When you use MyXAML you are writing lines of code, nice code but still code IMO. I don't really see MyXaml as 'code' in the traditional sense. Just like I don't consider HTML as code either. Declarative Programming is certainly the future as far as I'm concerned. Paul Watson wrote: The way MS and others make "no code" out to be is drag and drop visual wizardry which makes re-use and system-wide consistency difficult. There are certainly problems with the current wizards and code generation tools, but I think a lot of these can be overcome. And they must be overcome because 'typing' the same code over and over like your SqlConnection example is a waste of development time. In my attempts to retool my business to be aimed at supplying software solutions to smaller businesses instead of (the now crapped out market) for larger firms, where I can no longer 'afford' to charge by the hour for development time, I have realised that only way forward is to completely rethink my traditional development methods. I've always had a dislike for auto-generating of code and drag and drop programming but I now thing that tools that reduce the development time and development costs are the only way forward. MyXaml (another plug ) has started to help me achieve my goals. I now have a base CTI package that can be customised by altering the markup and the code-behind file without having to write lots of new code to achieve customers goals. (.NET has helped a lot too) And now if I can get my MxCRUD stuff finished, I'll have the data input/access cracked too. This is the first place that I need to create a code generation tool, because it is a pain in the ass and time consuming to create the necessary StoredProcedure parameters markup. (Not as bad as having to write the actual code but still a waste of valuable development time) And I've now got a few ideas on how to get towards the goal of 'Get Customers With Debt from Main Database' rather than having to write the archaic data-access code that we all hate doing but still find ourselves writing for each project we do. Michael CP Blog [^] Re: Writing less of it for more $$$ Aaron Eldreth16-Jun-04 5:29 Aaron Eldreth 16-Jun-04 5:29  What genious. Why didn't I think of that! Aaron Eldreth TheCollective4.com My Articles While much is too strange to be believed, Nothing is too strange to have happened. - T. Hardy Re: Writing less of it for more $$$ Jörgen Sigvardsson16-Jun-04 6:36 Jörgen Sigvardsson 16-Jun-04 6:36  And then retire early. -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter Re: Writing less of it for more $$$ Paul Watson17-Jun-04 11:12 Paul Watson 17-Jun-04 11:12  Wait till kids start retiring before they even start work... regards, Paul Watson Bluegrass South Africa Ian Darling wrote: "and our loonies usually end up doing things like Monty Python." Crikey! ain't life grand? Re: Writing less of it for more $$$ Jörgen Sigvardsson17-Jun-04 20:06 Jörgen Sigvardsson 17-Jun-04 20:06  The wait is over... some are born with money, some just don't give a f about anything, and some marry young and rich. I('ve) know(n) the 2 first stereotypes. I'm trying really hard to fulfull the last to 50%. -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter Re: Writing less of it for more $$$ Monty216-Jun-04 19:32 Monty2 16-Jun-04 19:32  Yup and CP helps me achieve that (tons of fine code here) so CP helps me make more money its more powerfull than i thought C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg wtf! stupid question... Ellery_Familia15-Jun-04 7:41 Ellery_Familia 15-Jun-04 7:41  is like asking, who would you rather loose, your mom or your dad? ...but, if i had to answer the question, the OBVIOUS answer is bug-free code. The single most important thing about code is, whether or not it works. Yes, we can all appriciate a well-designed, well-coded Types... but if the mofo doesn't do what it's suppose to, then who the hell cares?! Re: wtf! stupid question... Bamaco215-Jun-04 8:48 Bamaco2 15-Jun-04 8:48  I disagree. Take this case: You have a good application, "that does the job". Almost. As a matter of fact, measurement would show that the top 95% features are working perfectly, but that there might be a bug in some of the bottom 5% of the feature set. (This, by the way, IMHO, almost an industry standard. Do you thing that MS Word ships when there is 0% bug ? Haha. I think not!;P) Given a program that is easy to maintain, its easy to fix the bug. As a matter of fact, for a small shop like where I work, its the only way to know of the bug! I test my stuff all the time, but some of the features are not used or almost never used. Its cheaper to have me work on newer features that will generate sales and bring money in that spending eons looking for bugs in features that we almost never use. Don't get me wrong, those feature that are no longer being used a lot were tested a long time ago, when they were written. But sometimes, well, I like to say that, like our in our universe, where a pair of electron and positron gets created simultaneously, a feature and a bug gets created simultaneously by me, from time to time. That is not to say that I make a lot of bugs. Its just for the sake of argument: I'd rather be able to fix it because its so well written and obvious that it makes one happy to be happy to see and fix a bug than spending 1,000,000,000 years testing an application. (Note that a large application may end up with a lot of features)

Last Visit: 31-Dec-99 18:00     Last Update: 25-May-24 18:01 Refresh ᐊ Prev1234567 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.