bug; alvorlighet, hyppighet, omfang, risiko

kanskje noko å få inn i bug-rapport, dvs alle desse sidene ved ein bug. 
dvs, truleg berre risiko som manglar hjå oss.

My life as a Code Economist

Should we fix this bug or not?
There are four questions to ask yourself about every bug:

Question One
When this bug happens, how bad is the impact?  Severity

Question Two
How often does this bug happen?   Frequency

Question Three
How much effort would be required to fix this bug?   Cost

Question Four
What is the risk of fixing this bug?    Risk

Two of them are "customer questions", and the other two are "developer questions".

i tillegg såg eg i ein kommentar:

"But the most important question of all is missing:
Question 0. Do you know exactly what is causing the bug, and how?"

Lint4j

er dette verdt å vurdera å ta i bruk?

Lint4j Overview - Lint4j: "Lint4j ('Lint for Java') is a static Java source and byte code analyzer that detects locking and threading issues, performance and scalability problems, and checks complex contracts such as Java serialization by performing type, data flow, and lock graph analysis.

Lint4j was created to help software developers detect defects and security vulnerabilities before writing the first test case. Lint4j saves time during code reviews as well, so developers can focus on getting business logic right. The Ant and Maven plugins enable easy integration into continuous builds with Cruise Control, AntHill and others."

elles:

• Eclipse is the perfect environment for using Lint4j. Problems can be reported as soon as the source is saved, and the Eclipse problem marker system allows for easy navigation to the offending line in the source file.


• lint4j i eclipse - getting started
  

site optimization - inkl tabell vs css

ein del anna interessant der også - noko visste eg og anna hadde eg ikkje tenkt så mykje på...

Site Optimization Tutorial

".... table-based layouts are the de facto Web standard, and foremost because table-heavy designs have a nasty reputation for poor performance.

And CSS layout? It's faster, better, and smarter.
....
Even though pure CSS positioning is the ideal way to lay out a page, it can make your site look funny (if not ugly) for Internet Explorer 4 and Netscape 4.x users. That's still a fair enough shake of the Web audience. And while you can design CSS that degrades nicely in older browsers, it still tends to look, well, degraded. If what you want is the most cross-browser, cross-platform, business-friendly design solution, you still have to lay things out on the table.
...
CSS is cooler. And smaller. And in the long run, its better.
....
[But] Let's face it, sometimes right-now compatability trumps future-compatability.
....
Unfortunately, tables also increase the time it takes to display a Web page, and some times by a substantial amount.
....
[next page]
As tables get bigger, and nested into one another, the amount of info that needs processing increases exponentially.
....
Basically, you still need to do whatever you can to optimize table code. Or, better yet, avoid it altogether.
....
Accelerating fixed-width tables .... a CSS-1 style of {table layout: fixed} to a fixed-width table speeds up the display process in Netscape 6+ and IE5+.
....
[code example: ] table style="table-layout: fixed;" width="600"
....
Now, don't go abusing the browser's trust! If you apply the {table layout:fixed} style incorrectly, with WIDTHS that don't quite add up, the browser will catch the error during the rendering process and start things over from scratch.
....
[next page]
One old-school trick works, though — remembering that lots of little tables appear to render faster than one big, many-rowed table.
....
HTML editors ... produce amazingly inefficient code.
....
One notorious culprit associated with slow-to-the-screen Web pages has always been the nested table.
....
browsers have to work doubletime on tables. Unlike most page elements, tables absolutely require two passes of browser "reflow" (layout code-crunching)
....
A single-nested table requires two passes, plus one more, because the inner table must be partially re-rendered during outer table's rendering process. Nest three tables inside one another, and that makes for five passes of reflow. Nest five levels deep, and the browser loops through reflow routines nine times.
....
So avoid using nested tables whenever possible, even if it means making minor alterations or simplifications to page layout.
....
Even though table rendering speed issues are less problematic on modern PC hardware, table layouts still hamper screen readers and other accessibility-enhanced browsers. Nested tables doubly so. We're building Web pages here, not those little Russian dolls."

Coding Horror: Code Smells

Eit utvalg av "code smells"...

Coding Horror: Code Smells: "the most important guideline is to watch for warning signs in your own code-- so called 'code smells'"
....

• Comments: There's a fine line between comments that illuminate and comments that obscure. .... Do they explain "why" and not "what"?
  
  
• Long Method
  Sometimes length is justified, but all things being equal, a shorter method is easier to read, easier to understand, and easier to troubleshoot. ....
  
  
• Long Parameter List
  The more parameters a method has, the more complex it is. Limit the number of parameters you need in a given method, or use an object to combine the parameters.
  
  
• Duplicated code
  Duplicated code is the bane of software development ....
  
  
• Large Class
  Large classes, like long methods, are difficult to read, understand, and troubleshoot. Does the class contain too many responsibilities? ....
  
  
• Type Embedded in Name
  Avoid placing types in method names ....
  
  
• Uncommunicative Name
  Does the name of the method succinctly describe exactly what that method does? If not, rename it or rewrite it. ....
  
  
• Dead Code
  Ruthlessly delete code that isn't being used. That's why we have source control systems.
  
  
• Speculative Generality
  Write code to solve today's problems, and worry about tomorrow's problems when they actually materialize. Everyone loses in the "what if.." school of design. You (Probably) Aren't Gonna Need It.
  
  
• Temporary Field
  Watch out for objects that contain a lot of optional or unnecessary fields. If you're passing an object as a parameter to a method, make sure that you're using all of it and not cherry-picking single fields. ....
  
  
• Shotgun Surgery
  A change in one class requires cascading changes in several related classes. Consider revamping your design so that the change is limited to a single class.

Coding Horror: Recommended reading for developers

Coding Horror: Recommended reading for developers: "Recommended reading for developers"

nokon av desse har me snakka om før, men det er vel berre eit bra teikn...

digi.no - Gratis virtualiserings-klient fra VMware

digi.no - Gratis virtualiserings-klient fra VMware: "VMware annonserte i forrige uke en betautgave av VMware Player, et gratisprogram som gjør det mulig for brukeren å kjøre virtuelle maskiner laget med VWware Workstation, GSX Server eller ESX Server på en hvilken som helst PC med Linux eller Windows som operativsystem."

relaterte lenker:

• Virtual Appliances
  
• VMTN Blog
  
• Skal dele ut gratis virtuell serverplattform
  
• Why you should try VMWare's free virtual machine runtime
  
• VMWare har også gratisprodukt for å lage VMs
  
• VMWare er OK, men...
  
• FrozenTech's LiveCD List
  
• EasyVMX! is the simple and failsafe way to create complete virtual machines for VMware Player on the web
  
• Slik kan du bruke Linux i Windows
  

AJAX Magazine: Collection of 100 AJAX Tutorials

AJAX Magazine: Collection of 100 AJAX Tutorials: "Collection of 100 AJAX Tutorials

... including AJAX Activity Indicator, AJAX Bookmarklets, AJAX Chat, Client-Server Communication, AJAX Drag and Drop, Dynamically Content Loading, Forms and Autocomplete, Framework and Toolkit Tutorials, Getting Started with AJAX, AJAX Image and Gallery , Sortable List, AJAX Shopping Cart Tutorials, Sorting, Trees ..."

publicity

me gjer allereie noko av dette...

The Business of Software - Where have you been advertising for free?: "We've done a couple of segments on a local radio station.
....
Contact your local paper. .... Generated quite a few leads and a couple of contracts from a free article on the front page of the business section of the local paper.

We had another writup in a local publication that virtually everyone in business in our area receives and reads ... How did we get this? We called 'em up and said 'what does it take to get an article written' [?]
....
We try to obtain permission from our clients, in whatever we do for them, to prominently display our name and contact info. On a public web site, your name gets out. We even do it on private apps -- desktop type apps. We've gotten a large contract from a vendor of one of our clients because they used the app at our client's site and saw our name on the splash screen, and wanted a similar app of their own.

For several years (I no longer have the time) I was involved in a number of local programmers groups and would try to do a presentation at least once a quarter to the local techies. I haven't been active in these groups for at least the last 3 years, but I still get calls for work to this day (well, at least up through last week ). The contacts I made there will never dry up.

Pass out your business cards like there's no tomorrow.

Actually *ask* current clients/customers for referrals. If they're happy with your work/product, most will gladly recommend you.

I was quite amazed at what we got from simply putting a sign up in front of our office. .... have lead to some long-term client relationships.
....
Publicity is free. The most effective "advertising" is publicity: other people talking about your product or service with no compensation. Press releases are a start. Product reviews, being featured in articles, etc. are also publicity.

... what you are looking for is publicity.

historikk med svn (cvs-alternativ)

jf historikk...

Configuration Management Using Subversion: "Relational databases and the relational data modeling concentrate on efficient data storage and retrieval. The history tables do not model naturally with relational databases.
There is no support for versioning from the database. The application has to carefully store the entries into the history tables either through triggers or some other custom techniques.
It's up to the application to determine what changed between versions. The retrieval of historical information from the history tables is also specific to the history table storing the data.
The relational databases should still be the repository for storing and retrieving transactional data. They excel in managing these critical data assets. The shortcomings listed above are confined to storing multiple versions of data entities within the relational data store and tracking such entities over time."

frå opprinneleg artikkel:

"Today's enterprise applications are often required to not just store data, but also keep track of all the changes that are made. This expectation also permeates into an associated set of requirements, such as tracking the reason for each change, the time of the change etc.
....
Applications can use a combination of relational databases and Subversion to satisfy data management and data tracking requirements. .... Subversion would be the primary data source for use-cases for tracking"

Guide to Using AJAX and XMLHttpRequest from WebPasties

dette er ein tutorial på det som vel er kjernen av ajax.

Guide to Using AJAX and XMLHttpRequest from WebPasties: "The purpose of this article is to demonstrate through a series of baby steps just how easy it is to use the XMLHttpRequest object."

Continuous Integration

ikkje heilt ferdig med artikkelen, men i fylgjande avsnitt jobbar me heilt oppskriftsmessig, heilt til siste biten (det som kjem etter "my commit"), jf sitat nedanfor.
kort sagt: anbefalt med jamnleg automatisk bygging/ deploying for ulike kundar...

Continuous Integration: "However my commit doesn't finish my work. At this point we build again, but this time on an integration machine based on the mainline code. Only when this build succeeds can we say that my changes are done. There is always a chance that I missed something on my machine and the repository wasn't properly updated. Only when my committed changes build successfully on the integration is my job done. This integration build can be executed manually by me, or done automatically by CruiseControl."
....
"Less time is spent trying to find bugs because they show up quickly."

om java... (humor)

:)

The Joel on Software Discussion Group - Why do I need to know UNIX?:
....
"Java is write-once, debug-everywhere..."

30 second AJAX Tutorial

han som starta php, med litt under ein skjerm med js-kode for å ha noko ajax oppe og køyra...

'[PHP] Rasmus' 30 second AJAX Tutorial - [was Re: [PHP] AJAX & PHP]' - MARC: "I find a lot of this AJAX stuff a bit of a hype. Lots of people have been using similar things long before it became 'AJAX'. And it really isn't as complicated as a lot of people make it out to be. Here is a simple example"
....