It's been a minute since my last post but I've been living life and of course - trading!

I've made some updates to V2:

1. Added more information to the summary area, this gives you all the info you probably want to know in a compact space

2. Enhanced the themes so you can choose your own from a selection of 100+ pre-configured palettes for dark and light screens

3. Added ticker symbols and some broker artwork, will add more when I find them

4. Redesigned D.I.M.E. to make it easer to configure your .csv  files for import. I use this for 100% import success

5. For you day traders who may move in/out of multiple trades a day, I made it easer to keep track of long trading runs by rolling-up the trade which saves screen space and your time calculating each trade total

6. I also made the grouping trades logic automatic when importing a file - this saves a ton of your time!

7. When a trade is complete, you have the option to 'lock' the trade so you don't accidently make changes to the wrong row, or even worse, delete the wrong row!

8. Added an installer versus simply zipping the files. I think it's easier because of the point-n-click everyone is accustomed to

9. If you've added multiple accounts, its now easier to find all accounts by clicking on the 'list accounts' icon

So there we go! As I use Stocklog+ I find that something could be easier or more convenient and BAM! it kicks off a programming session to make trading life easier.

If you haven't tried Stocklog+, give it a spin since it's free to download and none of the functions are gated. Once you get the hang of it, I think you'll find it really does make logging your trades much faster which means - you'll actually do it 😉 

Every programmer hates it, no one will raise their hand to do, and everyone says: I didn't think that was my job?!

Do you have a hot-shot programmer, or a team who thinks their coding doesn't smell? 😤

Owners, Dev Managers, or Senior Dev with a 'smart junior' - The one thing you can do to reign everyone in... have them:

"Write end-user documentation for your application"

I can guarantee no one will make it out the door without finding a few errors in the code, especially if you're the coder! You can look at the code tens-to-hundreds of times and not spot the error. Even run it through a checker - "All looks good here boss!"

You won't find anything until you try explaining how something functions, in great detail, that will cause you to lean back in your chair and say "Huh, that's not what it should be doing.", or finally realize the steps are just too confusing and it should be simpler.

It's a great way to humble yourself and the team! It helps you locate errors before the users do, allowing you to get in front of it, maybe even delay sending code into production?! (I know... delaying is almost sacrilege!!) 

I suggest anyone who has a hand in programming, customer service, quality assurance, or any part of the life cycle - try to write documentation with the mindset that a user has never seen your application and they need to start at page ZERO!

Needless-to-say, we will be writing some updates ASAP and going through the documentation process again because of the changes.

It might be painful. No one want's to do it. But trust me, it will benefit everyone on the team to WRITE exactly how something works, with all the buttons & sliders, and what should be the end results.

It's eye-opening!