A while back, I wrote an application that processes sales information. These sales actually represent a hierarchy of data because there can be refunds, charge backs, charge backs of charge backs, refunds of refunds, adjustments, and so on and so forth. The way the data processing is handled, though, treating the entire hierarchy as a single transaction is important. This requires a bit of recursion.
Earlier today I was looking at the blog activity, and saw that a new milestone had been reached.
Today marks achieving 100,000+ hits. Thank you for taking time to visit this little blog. I hope that means that the content on here is valuable. Writing about various technical topics and ideas is a fun pastime and helps me formalize a lot of ideas/solutions that I ultimately utilize as a professional developer.
Here’s to the next milestone!
A while back, I blogged about a handy task scheduler and repeater. I use this code often and when I started using it with a heavy memory/data footprint, some serious memory leaks came to light.
I said it before, but I’ll say it again. Writing web-based line of business applications entails creating a lot of views with tables. I wrote a (imho) a pretty nice table directive for Angular 1.x, and now it’s time to move that directive, in concept, to an Angular2 component.