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.
How many people who do have a clue are still around? And why are they not working on it?
Just how can we keep having a clue, even when people leave or are not available anymore? Is that not what reqirement management, change management and project documentation are for? If these things do not exist (except - just maybe - between someone's ears), then building it new reduces the problem to getting a clue. At least you don't also have to wrestle with all sorts of undocumented surprises as well.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
We did that last year... rewriting an old system that I didn't write or knew how it worked. We ended up basically copying the old db and implementing a new back-end and front end, which at least came out looking prettier than the old one.
The advantage of using a web framework is that the application can be platform independent, is this needed ?
Otherwise I have my doubts, seen some things like the new PgAdmin4 for PostgreSQL that have become bloated and slow as molasses ...
They also seem to struggle with understanding where the code is running.
Trying to use Process.Start or Office Interop to open files on the client; trying to use MessageBox.Show to ask the user a question; trying to save files in a specific path on the client from server-side code; trying to read uploaded files directly from the path in the FileName property; etc.
Of course, I think a lot of these problems are caused, or at least exacerbated, by Visual Studio. When you run the project in VS, it's an interactive process on the same computer, so there's nothing to warn novice web devs that their assumptions are wrong. At the very least, it should be a non-interactive process, so that no UI can magically appear from the server-side code. If it could behave as if it has its own file system, completely separate from the developer's PC, that would cure even more misconceptions.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Quite. It was even worse back with classic ASP as given the stuff that runs on the client and the stuff that runs on the server were on the same file it was even easier to not appreciate that the little "%" in the tag made a big difference.
Of course that paradigm has gone full circle with razor but at least people are discouraged from putting business code in their views.
I still want to know where people are learning to string concatenate their SQL statements though. What articles are the looking at to learn how to code? Ones from 1996?
Rewriting may not be an easy undertaken when an application is "huge" running on a particular platform. Recently, I noticed that SAP Concur (https://www.concursolutions.com/default.asp) is still a conventional active server page application. If it could be easily rewritten, SAP would have done it long time ago.
I think this is a natural instinct in a majority of developers. - That don't make it right though, mister.
Many many years ago Joel Spolsky wrote on his blog about the refactoring/rewrite of Netscape. It may have been while they were under AOL. Almost all devs pressed for a rewrite: "Nobody can make this stinking pile of horse residue good.". In the end a total rewrite was decided on. The result was a release delay of of 2-3 years as I remember it. His takeback was: "resist your instincts, do it gradually".
"If we don't change direction, we'll end up where we're going"
For now they are putting down a web like service framework which is going to componentize the app to the next level.
That might be a good thing, particularly if the console app might be implemented as a web app at some point, or you want a future web app to have access and manipulate the same data. One API to rule them all!
Mmm.. the console app is, in fact, a hardware controller on RaspeberryPi. It ain't gonna be turned into a web app anytime soon.
What itch me the most so far is that their service architecture, so far, only support transient service, not something that be ongoing...
I just remarked that battery controllers are something on going.. not something you poll every now and then to wake up...
For example, code-wise, services with Start()/Stop()/IsRunning or Connect()/Disconnect()/IsConnected methods represent hardware controller better I believe than single Run(CancellationToken) method ones
99% of .NET framework documentation is made that way - that's why I hate .NET with a burning passion. Win32 API are much better documented, and still they don't approach the quality of Win16 documentation.
This is one of those pages that proves MS's documentation is generated by an automated tool, in case anyone still needs any convincing. Pulled entirely from source code--no comments, no documentation. Which infers developers are in charge of the documentation.