The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Basically, have you ever run into something you think you solved that you thought you shouldn't be able to solve, and it was much easier than would think to the point where you're not sure if it works?
I know what I wrote, so I will have an idea on whether it works or no, and why. It happened a few times.
Whenever I start feeling clever, she reminds me that I cook chicken in a non-stick pan with lots of vegetable oil to prevent it from sticking. Call it a balance
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Or, it is sort of as hard as you thought, but you finish it up and start testing and it's all working really well. That happens occasionally and it's kind of nice.
The thing I find is that there's a sort of 'be both the forest and the trees, young padawan' type of thing that happens ideally. Where you are keeping both the big picture and details in correct perspective throughout the process. I remember when I was young and would try to draw, and I'd get totally lost in the details and end up with a person with huge frankenstein hands because I'd completely lost the big picture perspective.
The ones where I manage to really nail it or it flows much easier than expected are very often the ones where I am always able to keep the big picture perspective while moving around within the details.
In my latest project, it looks like one of those serendipitous experiences.
I've made a rather amazing little parser generator. And some of the things it does i just didn't think were possible with it when I set about coding it. It's very expressive. It doesn't "feel" like an LL(1) parser. Woo!
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
So, I wind up at a decision point which has had me stymied for ten years on one of my personal projects.
Waaaay back in 2009 I was between projects and I decided that a good exercise for keeping my skillz fresh was to finally develop a Code Management System similar to OpenVMS' CMS (just because).
The core of the code (and the SQL database repository) was working within a week and after a couple of months I had a Command-Line front-end client nearly feature-complete.
Then I was at an impasse...
I had planned on having SHOW and LIST commands -- similar to those on OpenVMS' User Authorization Facility (UAF).
If you're familiar with UAF you may have realized that SHOW and LIST are essentially redundant -- the only difference being their default options.
So, while working on my version of CMS did I really want to implement two redundant features? It's been TEN YEARS(!) and I still don't know.
So this week… I decided, "Hey, I can make a really really simple Code Version repository in XML!"... and now I have most of the (few) features working... and I need to decide whether or not I need both SHOW and LIST !
We are using GIT but have disabled GIT functionality in Visual Studio a long time ago as we found it too unreliable / not supporting all functionality.
So my advice is to use an external Git tool, or if you are a die hard the GIT command line. https://www.slant.co/topics/2089/~best-git-clients-for-windows[^]
I don't think GIT is horrible, it might seem complex at first, but in comparison with Subversion it's much more reliable.
I've heard and told horror stories about TFS (or TFVC to be precise).
I used to do the same about Git when I first started using it.
SVN was da bomb!
Now I've been using Git for a while and I'd never want to go back to SVN.
It's all a matter of knowing the tools at your disposal and getting used to them.
I've found Git support in Visual Studio a bit lacking though, so I'm using SourceTree (by Atlassian) myself.
I'm finding myself using Git in VS more often though, so perhaps I'll switch to using Git with Visual Studio 2019.
I mostly agree, the only thing I use VS's built in git for is history/blame on single files.
The main difference is that only procrastination stands between me and dumping SourceTree
Atlasian took so long after defacto killing SourceTree 2.x by declining to patch security vulnerabilities to fix all the problems that kept 3.x from being as capable as the old version that I've lost all faith in them being able to deliver an acceptable quality product long term even though they've finally worked out all of the major bugs.
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?
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