The Scorpion remains tenacious. Still no sign, so I used three new seeds. Unfortunately it looks like the seeds are bad or the Scorpion wants it even hotter, but I doubt that. I also sowed two new Cayennes since only one of the original seeds sprouted.
The new leaderboard:
- 3x Jolokia
- 3x Habanero
- 2x Fatalii
- 1x Cayenne
- 0x Trinidad Scorpion
Nine plants should be a good start. I originally had 12 last year and gave four away once they bared fruit.
While the Cayenne and Scorpions take their time (they got 30 days!) the first of the Jolokias is growing the first real leaf. The middle one in the picture above.
The little greenhouse has artificial lighting, because at about 16:30 it's already dark outside. It is a ~2W LED light that did the job just fine last year. It might be a better idea to have a light source that also emits UV. Last year the poor plants were kind of shocked when I moved them from inside behind the window to the balcony into the direct sunlight. That's not a pretty sight if you leave them in the direct sun for too long. Luckily they all adapted after a while and around August all of them could be left standing in the brutal midday sun and they seemed to enjoy that. ;) (As long as enough water was supplied)
The first chilis have already sprouted. The Jolokias took the lead. I planted three of each type, so that would be 15 chili plants if everyone of them grows. Last year only 2 of 16 did not sprout.
The leaderboard is now as follows:
- 3x Jolokia
- 1x Fatalii
- 1x Habanero
- 0x Cayenne
- 0x Trinidad Scorpion
Hopefully the rest of them will follow soon. They are all kept inside a little greenhouse with a heating mat below on the window sill. It's (kind of) winter outside and this will keep them at a nice 25-30°C.
This year's chili season just started with:
- the (not any more) record holder Trinidad Scorpion Butch T
- the snack-sized Cayenne Yellow
- Fatalii (my favourite)
- the classic Habanero
- and the lovely Ghost Pepper (or Bih Jolokia)
The scorpion is new this year, everything else I cultivated already last year. Unfortunately last year the habaneros didn't turn out to be very hot. Interestingly some of the Fataliis smelled almost dangerous so it couldn't have been lack of sun. Let's see if the Trinidad Scorpion can live up to its reputation. :)
When you think you know all… most… well, a lot of Mysql's strange ways to fuck up your day. There is always something new to learn.
A regular SQL dump that has been generated with mysqldump on a totally ordinary Linux system. And when mysqldump just works on a database of several gigabytes something must be strange.
# mysql --one-database DB < db.sql ERROR 1054 (42S22) at line 1199: Unknown column 'NUDL' in 'field list'
What the noodle? Inspecting the SQL dump reveals the following INSERT:
Apparently the value should be NULL, but somehow mysqldump managed to mangle that into NUDL.
It took less than a week, if not only three days, for spammers to discover the new wolfpaper greeting cards I added to the archive. One day I noticed spam being posted and after a couple of days another one with very meaningful URLs like http://rghhrfpygded.com (not an actual URL, I hope) and completely invalid email. I added a protection from the pattern that was used.
And then there was silence.
A legitimate card was created some time later so I was reminded that everything actually works. Out of curiosity I checked the server's log to see how many junk I had (not) missed. My guess was one maybe two every other day. Well, not quite.
In the last week's access log there were about one hundred post actions. Every access from the spam script (it's too stupid to be human but you never know!) consists of two posts. So about 50 attempts in one week. That may not sound very much, but at the time this started the feature was live merely a week and nobody mentioned it on any site, board or weblog.
I would really like to know how the spammers, or better "spam script" as I still pretend they cannot be human, discovered it so quickly.
Comma separated XML – or also known as “parse this!”
<data> funny;column;description;goes into this field oh;and;here;is;some;other; column description dataset;1;2;3 <moredata> some id;123;43;653;314;fubar some id;325;31;434;143;blah some id;343;fu;---;;bar </moredata> <evenmoredata> interesting;description;for;some;columns;below or above blah;fasel;kek;blubb;10;432441 foo;bar;baz;<3;2352;23 </evenmoredata> </data>
- Find the dataset lines matching the definitions.
- Parse a single document containing 68000 such datasets.
- Write all of the data into an SQL database using sensible data types (text for each column does not count!) succeeding on the first try.
If you have come here in search of knowledge regarding JIT concepts as in “conecepts of the Just in Time principle” you have, quite non-obviously I admit, come to the wrong place. This article presents a whole new (business point-of-)view of the Just in Time Concept… as in “a concept just in time”.
The Just in Time Project – project manager point view
The problem with detailed and overly complicated project plans is… well they take their time. And we all know, time is money! And if the time you spend on your project plan is as little as possible, you can save a lot of money, right? Right?
Right! It'll all come “just in time”.
Well, ok there are some side effects. It generally goes like this: the project plan is a one-liner “make it work, make it look good and make it ASAP”. Not having any big picture the staff makes it work and look decent. And then the management (read: not project management) takes a look at it and, well, decides that a concept is needed!
But if all of this works in the first try, then you indeed saved a lot of money. Worth a shot, isn't it?
The developers' point of view
Before we begin, imagine for a moment the following development environment: a project devided in 3 principle parts with one developer responsible for one of each. Now the just in time concept's main dogma is again to save money. And so everyone starts right away, diving into their work like there is no tomorrow.
As the project evolves into a somewhat bigger gibberish mass from whence it started, person A needs to touch areas of person B, but since there is no conecpt for the whole thing (remember, we're saving time and money), person A goes ahead and changed stuff person B is working on. Which in turn
pisses of confuses person B since in his little world of project part B things might probably work a little bit different. But never mind, B can change it back the way he wants it to work and break a part A was working on, after all he doesn't need to care for part A since there is no concept. ;)
To be continued…
Hm, it's been snowing for the last couple of days, this could start to be interesting if all the white stuff melts.
Here's a picture from right out of the window at our work place. Must be about 15-20cm already. :)
Index: 1 - 2 - 3 - 4 - 5