Yes, I am a partial Web Designer, better yet, let’s call me a Front-End Developer. But also and even more: I am a Back-End Developer, not shown on this design-scale…
Tag: consultant
The Joel Test
bron: click here.
The Joel Test: 12 Steps to Better Code
Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a software team is. No, wait! Don’t follow that link! It will take you about six years just to understand that stuff. So I’ve come up with my own, highly irresponsible, sloppy test to rate the quality of a software team. The great part about it is that it takes about 3 minutes. With all the time you save, you can go to medical school.
The Joel Test
- Do you use source control?
- Can you make a build in one step?
- Do you make daily builds?
- Do you have a bug database?
- Do you fix bugs before writing new code?
- Do you have an up-to-date schedule?
- Do you have a spec?
- Do programmers have quiet working conditions?
- Do you use the best tools money can buy?
- Do you have testers?
- Do new candidates write code during their interview?
- Do you do hallway usability testing?
Onderhandelen
Onderhandelen: “We can be fast, good and cheap. Choose any two.”
Onderhandelen. We houden er niet van, maar doen het dagelijks. Wij vinden het moeilijk als onderhandelen onszelf betreft, als wij onszelf waarde moeten toekennen.
Onderhandelen is niets meer dan een transactie tussen twee partijen waarbij elk op voordeel uit is. Daar hoeft geen vijandschap aan te pas te komen. Redelijkheid en een ontspannen houding zijn genoeg. Zie de ander niet als tegenstander. Probeer elkaars doelen te doorgronden. In wezen zijn die hetzelfde: het beste product voor de beste prijs. Continue reading Onderhandelen
Error Creating Window Handle
It starts with “Can not create Window Handle”… and continuous random crashes. You find out your app reaches the max of 10000 user objects. (Just check the task manager, you’ll see I’m right.)
So, you’ve been using your own usercontrols on a flowlayoutpanel; you add, you remove, you clear… however the user objects count keeps growing and something is leaking somewhere…
You find that .controls.clear() does not work, you have to dispose() of all the objects first. Okay, do that, but it still doesn’t work.
So what’s the trick?
Simply remove first, before the dispose, and do this one at a time.
Just use the following routine:
ClearFlowLayoutPanel(myFlowLayoutPanel)
instead of
myFlowLayoutPanel.Controls.Clear()
Public Sub ClearFlowLayoutPanel(cFlowLayoutPanel As FlowLayoutPanel) Do While (cFlowLayoutPanel.Controls.Count > 0) Using controltoremove = cFlowLayoutPanel.Controls(0) cFlowLayoutPanel.Controls.Remove(controltoremove) controltoremove.Dispose() End Using Loop GC.Collect() GC.WaitForPendingFinalizers() cFlowLayoutPanel.Controls.Clear() End Sub
Good Luck! …or ask My Brain.
sources or more info:
https://blogs.technet.microsoft.com/markrussinovich/2010/02/24/pushing-the-limits-of-windows-user-and-gdi-objects-part-1/
http://stackoverflow.com/questions/1378668/clearing-controls-from-flowlayoutpanel-not-calling-destructors/
Display all PHP Errors and Warnings
When debugging PHP I find myself searching again and again for this little piece of code to display the PHP errors. So here it is for future reference…
If you wish to see all the PHP errors and warnings in your script, simply include the following bit of code:
error_reporting(E_ALL);
ini_set(‘display_errors’, ‘1’);
Now, continue to beat your head against the keyboard while you hunt down that missing semicolon or closing parenthesis. Need help, contact My Brain.
Phonegap Build changes
Nice. The ever-developing world of IT… or, “how to create more work for each other”.
My Brain develops Apps using a framework called Phonegap. Quick development, easy coding, simple configuration. Until you need to update an exisiting app and you are suddenly faced with the changes that were implemented since the last build…
This time the App did not want to access the Internet anymore… at all! So, Google to the rescue, finding this document with some good clues. I needed #10, which starts out perfectly phrased: “This is sooo new and obnoxious, one can only have pitty on returning developers.” …

Being a developer you have to love puzzles!