Best practices
-
“Our old software” syndrome
A few days back, while prototyping a new solution for a customer, one of the key users said: “But in our old software it didn’t work like that.” I was about to…
-
Standard enemy
The biggest jeopardies often lurk where we least expect them. When implementing an ERP system such as Microsoft Dynamics NAV, what should be one of our best…
-
Business case – do I eat it or?
It’s a well known fact that IT projects fail every so often. Standish Group has been researching the success and failure factors of IT projects for a decade…
-
Not-so-elementary costing: The Change
They say the only constant is change. I’d say that the only other constant is error. We humans tend to err. Give a repeatable task to a human, and they’ll mess…
-
Scrap doesn’t just happen
In reality, if you need 1,000 of whatever product, the manufacturing process is rarely going to yield exactly 1,000 of it, even if you feed into the first…
-
Why are “mandatory” fields baaad?
Last time, I gave you a recipe on how to do a bad thing. If you really need to do something bad, I figure it’s better to do it the way that would hurt the…
-
Code of coding 4: Die, hard(coding) 2
In Croatia, most of roads resemble battlefields. They are so full of holes and patches from all kinds of repairs over time, that they have to re-pave them…
-
Version management
When I posted my last relevant post on this blog, I’ve got a comment from infonote (a visitor) how bad it was that Microsoft Dynamics NAV can’t use a…
-
Code of coding 2: Documenting changes
Few days ago, when I wrote about coding, I didn’t have a slightest idea that at the same time, at the completely opposite part of the globe, Dave was blogging…
-
Code of coding
Code is boring. It is geeky. And it’s ugly, too. In C/AL it is especially ugly. While contemporary development tools come with all sort of gizmos which make…