I was using a factory like this
$factory = new Object_Factory();
$curr_object = $factory->create('brand');
to generate instances of objects I needed and wondered why Eclipse could not auto-complete e.g. getters and setters in my code for me later on for the
$curr_object. My productivity and my motivation to type all that stuff were seriously suffering…
So I found a very nice solution: Hippie Completion!
Instead of listing possible completion solutions like with Strg-Space the
key-combo “Alt-/” (/ on the number block!)
just completes what you started typing. You can also press Alt-/ as many times you like to page through all terms you could have meant like with the Strg-r on the console.
In case you try and wonder why it is not working like expected right away: Precondition for the hippie completion in Eclipse is, you typed the term to be completed once before!
Why didn’t anyone tell me this cool one before!
I just found this handy little tool:
You need to do the following:
- have your OPML ready (e.g. export it from GoogleReader),
- upload it to SuggestRss and
- see other feeds that might interest you.
Happy feed digestion!
Case: I was building a CLI script to aggregate data from one MySql database and write results to another MySql database using 2 open db-connections. This way the script’s execution time was in the some-minutes-range… not good! I tried a more effective attempt: I let the CLI script output all necessary statements to drop and create all needed tables and fill them with insert-statements. I called it like this from the command line and diverted output to a file:
$ php aggregatData.php > all_sql_i_need.sql
I could then import the whole thing in one go into my target database like this:
$ mysql the_dbname -h localhost -uMarco -pPass < all_sql_i_need.sql
Insight: The execution-time was way better than my first attempt and took only seconds. I could also have combined the two lines in a shell-script.
The problem with the generated SQL statements was, that the data also contained relations between primary and foreign keys of records and that these IDs were generated at import-time by auto_increment fields. I solved this issue by using MySql variables which can be set and use d again like this:
INSERT INTO gruppen (name) VALUES ('Gruppe 1');
SET @temp_gruppe_id = LAST_INSERT_ID();
INSERT INTO gruppe_eigenschaften (id_gruppe, name, wert) VALUES
(@temp_gruppe_id, 'email1', 'firstname.lastname@example.org');
The variable @temp_gruppe_id is set and can be used in the subsequent SQL statements. It also worked in MySql4.
Here is an example of SQL statements illustrating this mechanism in the above mentioned script. You can cut-and-paste it into your PhpMyAdmin.
There are many essays and articles on ‘Planning Poker’ out there. So I do not need to repeat the principles here. By checking out the recommended links (and folloups and others from your own research) you need to understand the following:
- What a story point of a project looks like and how you generate those story points in advance. Remember, your estimation should include design, coding, testing and delivery. In Planning Poker it is your goal to come up with estimates to those those story points with your team.
- The process of how one story point is estimated using the Planning Poker card deck and how to narrow down your team members’ estimates through discussion of the ‘played’ estimates.
- The background of the card deck used and why there are such odd numers in it.
- The effect all this will have to your project and the team.
The important thing is not the single estimate as such, but rather the open discussion among the the team members in advance, the mix of different perspectives and the collection of confidence in the team’s estimates. If the team is not able to get confident for an estimate you better recheck the user story in question and clarify it – possibly again with the customer. The more confident the team in one estimate is (=no big spread in single estimates of the team members), the less unclear ‘assumptions’ have been made in the estimate itself. This, in the end, reduces the overall risk (friction and interruptions) during the actual project and most importantly makes your customer happy.
Recommended articles and links:
I’m proud to announce the release of some new features in our LSIS Life Science Search Engine – ‘Save Queries‘, ‘Browse Channels‘ and ‘ORed terms‘.
Saving queries to channels works like this:
- Perform a search on our frontend. Then the button ‘Save Query‘ appears:
- Propose a title for your query and chose whether the resulting channel should be public or only private to you. If you select public the admin categorizes your query into the topic tree and approves it. As a result (a) a daily RSS feed is generated which can be used from your feed reader and (b) people subscribing to the email alert will be sent teasers by email if there are new hits added to our search index, fitting the query. The purpose is to make important news come to you without having to check what happened every day in your fields of interest.Public channels can be browsed on the channel page:
Another new feature is that you can OR search terms by entering them comma-separated as one search ‘term’. This makes searching and saving queries more accurate.
Feedback very welcome!
And if you find LSIS useful, please tell your friends.