|
VBA is very powerful. I picked up some new VBA knowledge today
diligent hands rule....
|
|
|
|
|
We do a lot of importing from spreadsheets. Last week a colleague helped a customer setup an import for a much smaller file that you are dealing with. (~7k rows and 20 columns) He had created a nice little pivot grid with subtotals and totals so we'd have something to compare to.
The import worked like a charm but checking the total against the pivot grid showed differences. Highlighting the column for the values we were after also did not match what was imported. It was off by a small amount...still enough for the customer and the colleague to think that something must be wrong with the import/software so they generated a support ticket.
It took way too long to figure out that around a dozen or so cells had numbers formatted as text which were not calculating in the pivot grid or in the automatic total in the toolbar. The import was actually correct!
This file in question is an exported report from another boh system. (not ours) When the customer was made aware of the problem, the first question was how to easily find and fix those cells. They weren't real happy with the answer I gave...scroll through the sheet and look for the cells that are left-aligned, click on them one at a time and convert to number. It's what I did and took around 5 minutes...really, it's not my problem...you don't have to fix it at all, just trust the import which was right all along! Of course the next question was related to why didn't the import just fix the file for them.  I can't win! 
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
I first read that title as "The Joys of..."  Oh, nevermind.
|
|
|
|
|
Slacker007 wrote: I first read that title as "The Joys of..." Oh, nevermind.
If you were thinking about the joys of ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) ing, it was ed anyway. Close enough.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
You should have to use a Java ETL tool like Pentaho/Kettle. 14GB just for reading the "distributed registry" aka Spring+ config files.
|
|
|
|
|
1400 columns!?
What human will even be able to read and interpret that much data? 
|
|
|
|
|
Sander Rossel wrote: 1400 columns!?
The changes I was debugging were to allow scaling down the report size at customer request; after years of insisting on adding more stuff to it. 
Sander Rossel wrote: What human will even be able to read and interpret that much data?
My understanding is that they fold, spindle, and mutilate out a subset of columns containing whatever they're actually interested in at the moment; and then feed it into a stats program for a second round of folding, spindling, and mutilating in order to get a result of "we did good last year, give us another grant to keep doing this for next year".
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I was thinking about how my development life has changed a little in the last decade. No longer is it just Visual Studio. It's Visual Studio, and Azure DevOps, and SQL Server management studio, and pgAdmin, and Redis desktop manager, npm and webpack, Chrome and DevTools, CodeProject and SO, remote desktop, PowerShell, and all the ridiculousness around hosting, domain management and DNS.
That's a lotta stuff, which I guess I could group roughly as
IDEs
Build tools
Debug tools
Data storage management
Remote management tools
Source code control
Library management systems
Hosting services and tools (including backups)
Community support
[also: Office + online Office (MS + Google)]
[also: Security apps (password managers / authorisation apps)]
[also: Chat / video conference apps]
[also: graphic design apps]
Coffee
Is this normal? Anything else you guys are generally using day to day (or no longer using these days)?
cheers
Chris Maunder
modified 23-Nov-20 12:43pm.
|
|
|
|
|
Yeah, the toolchain has grown a lot in recent years.
For me these are the ones I use the most regularly:
IDEs:
Visual Studio 2019
Visual Studio Code
Programmer's Notepad (used as a scratchpad / quick editor)
Data:
Navicat for PostgreSQL
Redis
Source Control:
Sourcetree
Azure Devops for builds and deployments
Browsers:
Edge (Chrome), Chrome
Insomnia and Swagger for testing Web APIs
Others:
WSL2 to SSL into servers
WinSCP
Comms:
Outlook (stuck with 2010 due to Org)
Slack
Whatsapp
Zoom
Misc:
Paint.net for screenshots
modified 23-Nov-20 10:39am.
|
|
|
|
|
Based on the role/work, I think it pretty much covers all but one:
Collaboration tools - Outlook, Slack
|
|
|
|
|
These days?
SSMS
Notepad
CSC
Plus the utilities I develop with them.
|
|
|
|
|
I'd add Excel, PaintShop Pro, and Outlook plus a couple of in-house tools for monitoring odds and ends.
Oh, and Expresso.
And Fusion 360, but that's more personal than work related.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
As a simple C++/MFC desktop developer (no DB, no online/web), I'm relatively conservative.
Just Visual Studio and an old version of Araxis Merge and Visual Assist and ReSharperC++ and notepad++
And jira and git and azure devops.
This has has been my setup for many years (except azure devops which is new-ish)
I'd rather be phishing!
|
|
|
|
|
our shop just upgraded from writing in the dirt with sticks, to stone tablets. big win, if you ask me!! 
- Visual Studio 2019
- SQL Server
- DevOps using Git repos. Continuous integration with DevOps as well as sprint planning, etc.
- Visual Code
- LinqPad 5
- Learning AWS
|
|
|
|
|
I would group all of those, mentioned above, by:
Development Machine (Offline):
IDEs
Build and debug tools
Remote management tools
Data Center or Cloud (Online):
Data storage management
Source code control
Library management systems
Hosting services and tools (including backups)
Community support
Miscellaneous:
Coffee
|
|
|
|
|
These are all tools I use daily:
1. Coffee (makes me decide to live another day)
2. Coffee (ensures I let the rest of you live another day)
3. Remote Desktop (working from home)
4. Visual Studio
5. Trace Viewer (an in-house debugging tool)
6. Visual SourceSafe (don't; just don't)
7. Coffee (renews #1 and #2)
8. Chrome, Google, www.codeproject.com  and www.stackoverflow.com 
9. Notepad
10. Paint.net
11. Builder (in-house automated build tool)
These are as needed:
12. WinMerge
13. SysInternals suite
Software Zen: delete this;
|
|
|
|
|
6. Visual SourceSafe (don't; just don't)
I will : my condolences. ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif) 
I'd rather be phishing!
|
|
|
|
|
Maximilien wrote: Visual SourceSafe
Is that still a thing?
|
|
|
|
|
In our defense we have a set of best practices which are aggressively enforced, automated backups, and smart people using it. We are a small group that started with over a dozen people years ago and are now down to five after some financial misadventures by the company. Our workload is heavy enough and SourceSafe is such an ingrained part of our toolchain that we've never been able to switch.
Software Zen: delete this;
|
|
|
|
|
Up until about 2 years ago we were using VSS as well, then (what was meant to be a temporary step) we moved to SourceGear. This is very similar to VSS so really no learning curve.
They have VSS to Source migration tool (probably a day's downtime with about a weeks prep). It was very easy/relatively painless process. The repository resides in SQL, Visual Studio integration, GUI tool or Browser. It does have its funnies, but nothing serious (that I've come across).
It does have a migration to GIT as well (for later).
BTW, not associated with SourceGear, just a user.
// TODO: Insert something here
|
|
|
|
|
Back in 2015 we had a lull in the workflow, so I took a serious look at modernizing our toolchain. I considered SourceGear, but opted for git. Unfortunately our situation went to hell in a handbasket as we were talking about the change, so that all fell by the wayside.
Software Zen: delete this;
|
|
|
|
|
We have VSS and TFS. Management/Corp IT is making us move to 100% TFS, but most of us like VSS better.
Bond
Keep all things as simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
I looked at TFS. Even for a small group like ours, it would have required someone maintaining it full time. While git is not terribly intuitive, at least the maintenance is simple.
Software Zen: delete this;
|
|
|
|
|
What maintenance?
We've been using TFS for over 8 years (now also use VSTS and Git).The TFS system "just works". Developers check stuff in and out, merge to test and release branches, run the build tools and don't really think about it.
I suppose there's a bit of "maintenance" adding new users or if someone moves to a new project, and, of course, the Systems team backs up the server and its database, but we've found it's generally set it and forget it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
