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.
I sometimes wrestle with this because I find what's interesting to me is not to other people. I like theory a lot, and sometimes people are just more practical.
So I have an upcoming article I'm writing that is rather involved.
It's a tool that allows you to write .NET code in a subset of C#, and then it will render that subset to any .NET language (VB, C#, F#) whatever.
What it's for is to make it easier to develop code generation tools. You can use something like T4 text templating with it to render dynamic code instead of having to build a CodeDOM graph in code without sacrificing the language agnostic nature of the CodeDOM.
What it does is turn a CodeDOM compatible syntactic subset of C# into a CodeDOM graph
How it works involves parsing, type and name resolution, - basically everything a compiler does except the actual code generation part. So like, two of the three tiers.
So, the article could be an article about the tool, or it could be an article on like a beginners compiler writing guide.
Which is more interesting? The tool or the pseudo-compiler guide?
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.
Please both So two connected articles. Why?
a.) Both are interesting
b.) During christmas you have a lot of time
c.) But the most important: It will hopefully helps you having your hand on the keyboard and therefore away from cigarettes
It does not solve my Problem, but it answers my question
Tell them it's OK, even Santa is on board with this, he named one of his reindeer 'Doner' didn't he?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
So I've inherited this WinForms project for a customer who's a two hour drive away.
It's a fun project and a good customer, but the code quality is... It (mostly) works, let's leave it at that
What's worse though, is the manner of deployment.
Which is each work station one by one
Software on a USB and go.
Of course a couple of people aren't at the office or have another work laptop at home.
In that case it's phone them one by one and update using TeamViewer.
Since I'm not going there for every update (which can be ad-hoc and unplanned) the phone and Team Viewer option is used frequently.
I wrote a little program that closes the application and then copy/pastes a newer version from a file server which also happens to be someone's regular computer.
That way I only need to copy/paste the new version to a single computer and everyone gets the new version.
That sounds great except not everyone has file access to that computer (even though it has all the reports and the database as well).
Seems like I'll be updating individual workstations for a while...
Any sort of version control wasn't present until now, so everyone has version 126.96.36.199, but they can still be different code bases (but the individual code bases can never be recovered unless you do some reverse engineering).