Bad (or, my unfortunately unfavorable review of Bob Martin’s Ruby Midwest keynote)
Critical thoughts on an Uncle Bob speech
If I were an Architect Thoughts on agile architecture
Give it five minutes Don’t be a hothead
Bad (or, my unfortunately unfavorable review of Bob Martin’s Ruby Midwest keynote)
Critical thoughts on an Uncle Bob speech
If I were an Architect Thoughts on agile architecture
Give it five minutes Don’t be a hothead
In the current beta version of Ext GWT 3 (beta4), a ComboBox does not fire a ValueChangeEvent immediately after a value is selected. The event is only fired when the ComboBox loses its focus or the return key is pressed inside the ComboBox.
To fire the ValueChangeEvent immediately upon selection, you can add a CollapseHandler as a workaround:
1 2 3 4 5 6 | |
CoverMe is a code coverage tool for Ruby 1.9.
Using Jenkins for CI, you can display the coverage results in your project overview even though Jenkins does not support the original output format of CoverMe.
lib/tasks/cover_me.rake and make the :report task look like this:1 2 3 4 5 6 | |
coverage/coverage.xml.On Programming Deadlines
Guidelines for coping with deadlines
Egoless Programming - Developing Without the
Attitude
A little older article for those of us with a magnificent ego.
You’re Pricing It Wrong: Software Pricing
Demystified
Basic economics for developers.
I’ve recently used Oracle’s SQL Loader with a control file like this:
1 2 3 4 5 6 7 8 9 10 11 12 | |
SQL Loader gave me the error message ORA-01722: invalid number.
The definition of the TEMP_DELETE table is
1 2 3 4 5 | |
And the input file looks like
1 2 3 4 5 6 | |
Although the files look perfectly fine, I finally figured out the problem. SQL Loader tries to interpret the line breaks in the input file along with the preceding number, i.e. 87364 becomes 87364\n which obviously isn’t a valid number.
To fix this, I modified the control file and added TERMINATED BY WHITESPACE after the last column definition.
1 2 3 4 5 6 7 8 9 10 11 12 | |