My web development blog

Where I sometimes also write about other stuffs.

It's 2017

... and things are less different than I'd like. What has happened since the last time I updated?

somewhy.com is no longer owned by me
I gave up the domain to someone with an interest in the name, and you may see something cool there soon. :)

When I'm out, I constantly find myself asking / being asked this question: what do we do today? This app was created to help provide answers to that question for myself, and others. Duwotz is now on Google Play only and planned to be on the App Store soon.

Not much happened, but still, 2016 was cool right?
Permalink | Posted 4:32PM 2-1-2017 by Quentin.

About dependency injection

This past week I went to the .NET meetup and saw several presentations. The first one was on dependency injection. Following the meetup I googled on the topic and found this helpful StackOverflow thread.

Extract from the second top answer:
This gives you a ton of advantages. Two important ones are the ability to control functionality from a central place (the Main() function) instead of spreading it throughout your program, and the ability to more easily test each class in isolation (because you can pass mocks or other faked objects into its constructor instead of a real value).

The drawback, of course, is that you now have one mega-function that knows about all the classes used by your program. That's what DI frameworks can help with. But if you're having trouble understanding why this approach is valuable, I'd recommend starting with manual dependency injection first, so you can better appreciate what the various frameworks out there can do for you.

This linked article from the thread, Dependency Injection Demystified, also delivered on what it promised.

Wow it's been long since I last posted.
Permalink | Posted 10:11PM 3-2-2015 by Quentin.

Sundry matters -- Magic hands

In my jobs working with applications, I often also end up having to do user support. A common scenario occurs frequently enough that I think it bears considering:
- A user calls me up saying there's a problem with an app he/she is using.
- I go over to the user's desk and ask for the steps taken that led to the error.
- The user walks me through the steps that he/she took.
- And then, the error mentioned doesn't appear.

At this point, I normally ask the user whether those were the exact steps taken, to which the user will usually answer, quite certainly, that yes, those were the exact steps taken. I would then try to consider in my head the possibilities for errors along the steps taken by the user but, usually, the problem raised won't be reproducible by this stage. In these cases, I sometimes tell the user that I have magic hands, and some other times I tell them the computer just likes my face.

Of course, in all seriousness "magic hands" isn't really a satisfactory answer for the error being "magically" fixed, but how do we find out what caused the problem in the first place?

Program flow potentially branches every time there is a function call or a conditional statement in the code. Therefore, one should be able to tell with precision how a program will run if the value of all relevant variables are known at these branching points in the program. It would be of immense aid in tracing program issues if these variables are logged in some manner every time a branching point is encountered. I wonder how this could be done in, say, .NET, which is what I'm using mostly nowadays.
Permalink | Posted 10:36PM 9-8-2012 by Quentin.

Adding rows to ASP.NET GridViews

Recently I've been working with GridViews to allow entry of data into database tables. One thing that I've had to figure out was how to add a row to a GridView for inserting records.

That link, by the way, links to some example code and explanation of how I did it. I haven't seen a complete example of this being done while I was searching online for ways to go about doing it, only vague suggestions without any code. Then again, perhaps I've gone about doing it the wrong way by letting the user enter directly into a GridView. Perhaps also I should be moving to MVC, or even off ASP.NET altogether.
Permalink | Posted 6:29PM 1-7-2012 by Quentin.

Sundry matters -- books, experience with other developers

Been thinking of getting some books on programming topics and the like, but just realised that the only brick-and-mortar shop that I know about which sells these is closed, that's a downer. Will probably have to get the books from Amazon or something.

These couple of weeks I've been liaising with some third-party developers working with my employer, and I've come to notice something: it is really easy for a developer to have an incomplete understanding of a client's requirements. That's one point right there for the whole Agile concept of releasing often and getting regular feedback from the users. A developer, even with the best of intentions, can way too easily miss out nuances in the users' requirements. There is, therefore, benefit to having the users see developed products and then giving feedback often rather than putting in too much time upfront trying to get "complete" requirements.
Permalink | Posted 11:26PM 10-6-2012 by Quentin.

displaying page 1 of 6
Next> Last>>