The FPU is pretty much deprecated in favour of SSE (it won't disappear though), but SSE also implements IEEE754: it has all the rounding modes, it has the sticky flags, it has the exactly-rounded operations, implements at least one of the required formats (two, even), and can trap for certain kinds of illegal operation (but usually is configured not to).
Here are some Link With book name
(1)Head First design pattern:
Design Patterns CD: Elements of Reusable Object-Oriented Software:
Agile Principles, Patterns, and Practices in C#: http://www.amazon.com/Agile-Principles-Patterns-Practices-C/dp/0131857258
Professional Asp.net Design Patterns:
Patterns of Enterprise Application Architecture:
I read professional_asp.net_design_patterns that contains real example that is much necessary for any developer. Also I read some topics of Head First Design pattern also fantastic book. If you are in .net framework I will suggest you to read professional_asp.net_design_patterns and Agile software development: principles, patterns and Practice in C#. Both of them are awesome for read. Both of them contains huge real example that will be helpful for you. professional_asp.net_design_patterns contains some most used GOF design patterns with examples and PER (Patterns of Enterprise Architecture) patterns example with SOLID Principles. I think this will be much better for you.
I want to create a virtual printer which will be visible under "Devices and Printers" say "ABC Print Driver"
User can select this "ABC Print Driver" as default printer.
When some one gives any print by selecting "ABC Print Driver", it should first authenticate the user with the windows User name and Password against the Active Directory by popping up a dialog and then capture the details (document type, size, time etc) and then, instead of sending it to actual printer, it should upload the printed document to some FTP server.
I am also thinking of catching the prints issued using spooler.
First I will register for spooler notification.
Whenever I get a notification from the spooler that a document is spooled/printed, I will try to get the details such as, "printed by", "submitted date", "job id", "job size" etc. Then I will cancel the job and I will store the print job at some FTP location.
I am doing this so that users can store their prints and get them printed at a later stage.
Please let me know which approach is appropriate.
Also point me to some examples if you know any.
i am working on Project called Inventory Management System for Hardware shop and i play developer role.
Now The database has category table which is consist of many categories such as Motherboard , Ram , Processor and so on.
Now the question is what is best way to store specification in database
because every category has its own specification ,
I Have Two Way :-
either by creating different table for each specification of Category
or create single table for all specification of Every Category.
i am confuse between this two.which one is best and faster.
Thanks in advance..
"value_type" could be "TEXT", "INT", "DOUBLE", "FLOAT", etc. And the application handles the value type as necessary. So if the value type is "FLOAT", the user must input a valid 'float' value. And so on.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
Personally I started studying Project Management when I got fed up of being asked to code and build the wrong thing. I doesn't mean I can stop people making those decisions to change but at least it helps me deal with them.
One of the first things I learnt to do was design by interface and decouple program elements after inheriting one mammoth all-in-one program on my first job. I then taught others in the team how to do this.
Another approach is to design the functional system first agree on that and then start building/coding it. Don't sit down and start coding, as a programmer most want to but its the wrong thing to do.
Produce a plan and make people aware of the various points times where, if they want to change, its a lot cheaper to do so before that point than after it.
I was curious what methodologies people think work well in environments where priorities change extremely frequently.
"Run". Seriously, if someone asks to build a castle, next day a it becomes a boat, next day a plane, next day an iBot, and I will be dropping everything until someone makes up his mind. The needs of the customer do not change "every minute".
Member 8824288 wrote:
So what's a good methodology for taking that first baby step out of chaos?
Stop promising things that aren't built yet.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
“The Only Thing That Is Constant Is Change -” By Heraclitu
I found his is so true for Software Development.
In my Software Engineering training, I took a course titled "Managing Evolving System and Software maintenance". This course demonstrates that most software are not build for change.
The best Methodology embraces the change from start and allows iterative development. Agile Software Development is an example that methodology;Rational Unified Process (RUP) is another one. Agile allows incremental delivery of Business value to the project.
Therefore, the change is good as it adds clarity to the development. For one reason, in large scale project, the requirement can only became clear in an unspecified time in develoemnt life cycle. The problem is lack of a Change Management System and iterative development process.
So what's a good methodology for taking that first baby step out of chaos?
That won't work. If I remember correctly there is even a study that shows it won't work (ACM OR IEEE years ago.) If management, not you, does not agree to a change in how they work, not you, then it doesn't matter what methodology you use.
Other than that the methodology that I would use is documentation. When they tell you to do something insist on email. And take a copy home with you. When they tell you to stop and do something else, get an email, and take it home with you.
If someone insists on meetings then follow the meeting up with an email where you ask them to confirm what is supposed to be done.
If different people are insisting on different priorities then make it their problem not yours to sort it out. Email all of them and ask which task you should work on first. If one tries to send response only to you then resend to ask that the others agree with the responders direction.
If you feel up to it the copying the boss of all of them can lead to interesting results. Although to be fair not necessarily positive ones.
But regardless always remember to be polite. Myself I like to compose an email, then let it sit for a bit, then re-read to be sure that it does not sound accusatory. As one possible way to do this always phrase it in such a way that you are asking for assistance.
Thanks to all of you for the replies. They have been very interesting so far.
First off, I'm probably touched in the head but I actually like working here. These people do acknowledge they are shifting us around and what it does to schedules and deliveries. So I'm not planning to run - just looking for things to make small improvements.
I'd settle for starters to even get a to-do list together that we are all seeing and is always accessible. And maybe I've answered my own question on the first step
Also, we have extremely short project schedules most projects are done within a couple weeks, many are a couple days and the "huge" ones take 2-3 months.
I was considering SCRUM but it requires an agreed upon list that doesn't get changed until delivery. I mentioned it to my boss and he said he thought trying to do SCRUM here would be like going to Disneyland and getting driven around in a golf cart but not being able to get out and ride the rides. LOL
I have worked on projects that were very formal with documents at each step of the waterfall and mandatory code reviews of all code (which had a DOD B-1 rating) to places where the only process is the one I follow myself
While I can't change the culture here single-handedly and I believe the study you mentioned, I'm still thinking there must be something I can do to start making at least a small step towards a more structured process.
My current hat is web developer for a marketing organization - front and back end - html, css, CMS add-ons in asp.net, integration with back end CRM and web service between the CRM and another server. In the past I've done real-time concurrent, automated equipment, drivers and desktop apps and managed Quality Assurance.
I've been in this business longer than I want to admit LOL but I'm still searching for what's out there that I might not have heard of yet. This is a business full of very bright people, I keep thinking someone has come up with a way to start the change at the grass-roots level.
Last Visit: 31-Dec-99 18:00 Last Update: 17-Jun-18 22:04