- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
You would be very, very surprised. I've found that job titles don't have much to do with what a person actually does in very specific circumstances like that. Although, it is funny that the title has more with what the person knows how to do, but it doesn't prevent them from doing other things.
Admin
So, you could have different projects targeting the same platform, possibly benefiting from using shared code, and you think a sane dev shop would allow people to mix project file formats, compilers (either brand or version), etc. at their own whim, ensuring any work done has a much higher change of not being able to integrate with other projects if need be? What if dev A has to fix project B written by dev B, but dev B used VS9 and dev A only has Eclipse/GCC set up, but has to fix a bug in dev A's code? What about the different formatting conventions causing havoc with revision control diffs/checkins? And you think this is a sane dev shop? You may want to re-evaluate that.
Admin
"... but has to fix a bug in dev A's code?"
Dev B's code, obviously.
Admin
I have the same setup in my job: i'm an "analyst" but must support legacy MS Access / VB6 apps (which make up 80% of the internal apps) by "data maintenance". Any "development" and my position gets eaten by central I.T., moved to another city and all support for the systems disavowed.
Since the business would come to a halt ~2 days after our Hackcess apps. stopped working, we "discretely" built a standalone machine with Visual Studio etc. on it and are migrating slow-time to .NET / sql server.
And how do we still claim to be doing "data maintenance"? We modify the existing MS Access apps on the live network to download the latest version of the .NET app from blob data on an sql server into a users temp folder and then execute. No "development" sir, no no, just maintenance of the same ol' Access database, nothing to see here...
Admin
Admin
He could have been draining the Access data to MSDE/SQL server express/MySql and use Access as frontend if budget for proper SQL server is not allowed. This would have solved a lot of the performance problem.
Admin
Karen glared across her desk at Tom. “Did you install a Microsoft product on your computer?”
“Yes,” Tom replied, unsure why she radiated waves of fury at him.
“Why would you do that?”
Admin
Sounds like they are trying to make IT a modular unit. Maybe up to the point where it can be replaced by another similar IT modular unit, like say, an outsourced IT department.
Admin
I would call it more a case of turf protection.
IT often has to draw lines that other groups aren't happy with. Some examples:
Answers like these can be perfectly valid, and they can be perfect cop-outs. The users may well be suggesting the wrong (or unnecessary solutions), or they may be suggested necessary solutions that upper-level management won't buy.
In any case, when told, "No," users will sometimes decide to proceed on a project on their own.
Assuming nothing has been lost to making the story anonymous, however, IT may have had a point in this case.
The story says that the accountants built the system, but that none of them are sure of what it does. That is not indicative of poorly-defined requirements and weak knowledge transfer, which tend to cause ongoing headache in business processes.
As a final point, IT has some reason to push back against providing support to implement a system they know is trouble, since a minor support role (such as providing a database) can easily be transformed to "ownership" of said system.
Admin
Admin
Oracle=Microsoft now?
Admin
Holy hell. I don't know whether to be awestruck, or incredibly disturbed.
Admin
Project files does not belong in the repo. And even if they are there, if the devs are not completely retarded a different IDE does not mean any problems. Just turn of auto formatting and off you go. If your IDE cannot generate a project from existing source, it is broken. If a dev cannot read code sufficiently to work with a plain text editor, he needs to get his shit together. It is not the fault of the dev environment, but the dev itself if shit happens in your described scenario.
Admin
I thought a "speed limit" meant that was the maximum number of methamphetamine hits you were allowed to take while driving.
Admin
But the whole premise here was that he was given an Access app and decided to rewrite is using .NET and Oracle. That's the context in which I was writing. The issue is not that he wanted to use Notepad++ instead of vi, but that he wanted to use an entirely different programming language and database engine.
Now if the question is: "Which is a better platform for a non-trivial application, Access or .NET/Oracle?" I would answer (b) in a heartbeat. If I had a period of temporary insanity and took a job in a shop that developed serious applications with Access, when I woke up I would certainly be pressing to change the platform. But I wouldn't just decide to do it and go off on my own. Because as nice as that might be for that one project, if everybody did that, the place would be an unmanageable nightmare.
Admin
Perhaps this depends on the language you're working in or the type of projects you work on. This is certainly not true for many projects that I've worked on.
An IDE's project file often includes more than just a list of files in the project. All kinds of information can get put in there that cannot be trivially recreated in another environment. Just for example, in a Visual Studio "solution" file, there is information about which modules from which projects are accessible by other projects. An Eclipse project includes information about which files are included in a jar and whether and how other jars are included within a jar. It also describes the order in which libraries should be searched. Etc.
If we switched to a different IDE, could we re-create this information? Of course. But it would require studying the project and making intelligent decisions, sometimes very subtle one. Depending on the complexity of the project, this might take just a few minutes or it might take many hours. Mistakes could introduce subtle bugs. If you have developers using different IDEs, then this would mean that every time you do a checkout, you would have to review all the project-level info to see if you needed to make changes to parallel what was done in a different IDE.
Admin
That one doesn't work either, surprisingly.
Admin
Isn't "Accountant" a better job than "Developer?"
This sounds like a missed opportunity to me.
Admin
Updating his resume to include his one-day stint at the Fortune 500 company?
Admin
Admin
Yes, because Oracle is now owned by Microsoft.
CAPTCHA: appellatio. When you have an appetite for fellatio.
Admin
If you aren't part of the problem (e.g. because it's your first day on the job) you are part of the solution, but why bother? Down the street at Someone Else Corp. they don't have the problem to begin with.
Admin
Agreed. There is no middle ground. Write it yourself ( like finance did ) and just get something up and running or bring in IT and spend more time/money than you have.
Admin
But in any sane shop, there'd be a build script that can create a working development environment (not IDE-dependent), including any necessary configuration. Doesn't matter what you have in your IDE, if it isn't in the build script then it doesn't count.
Do you also expect the end customer/client/server to be running the program within an IDE with the exact same configuration?
Admin
I once had to write a multi-user project instrumentation tracking application in Access and VBA (a port from an even more monstrous combination of ancient software). While my supervisor agreed with me that there were better tools out there, the company's IT department didn't want to give the department permission to install Visual Studio/add a few databases to the existing SQL Server installation - and they'd been asking for years. They didn't care about the fact that even the free Express versions would've easily got the job done (there was probably about 2GB of data total in there, and even that was split up in separate databases for each job site).
At least I had the decency to comment, document, and use linked tables on that behemoth...though I still feel sorry for the poor sap who will have to port it when they're finally able to convince IT.
Admin
Admin
This x100. Sure, you might get lucky and as "the new guy" be able to show the company the error of their ways and get that big migration away from VB6/introduce modern development practices/rewrite that spaghetti code monster/expose your incompetent CIO and take his job, but chances are you'll also just be ignored and/or told to just do as the boss says, if not fired for trying to fix all the problems because nobody else in the company notices the problems.
Or you can go and work for a company that doesn't have any of those problems: They don't list a job as "VB.NET" when it's really VBA; they use cutting-edge and modern development practices; they mercilessly refactor code and all developers get unlimited resources for books/training/conferences; the CIO is either a developer himself and knows how it works, or else knows to trust the dev team and shield them from upper management.
Most of the time, it's not worth it trying to fix a company that has so many things wrong for them. Even if you don't just get ignored for being the newest member of the team, a company that has LET so many things go wrong doesn't have a clue about the right way to do it, else they wouldn't be in such dire straits to begin with.
If a company has to misrepresent a job (e.g. saying it's .NET when it's VBA because both has VB in the name), or outright lie (e.g. you will be working for a subsidiary company that offers "services" to the parent company, but they make it sound like it's just internal IT) there's a fundamental issue at the core of the company and its leadership as they believe it's okay to be dishonest to employees.
Admin
I just hired with a new job under the premise, that I would be allowed to refactor their big-ball-of-mud code as I see fit. Now I am running into a lot of red tape with a manager about just doing the most basic readability / maintainability changes in that code.
What do I do? Jump job, just after 2 months?
Admin
Karen wasn’t interested in giving Tom any technical direction, so he dove in. The first step was get some space on a real database to migrate the data to. - http://tedbg.com He could then gradually move features into a .NET app and work with the users to make sure the new application mirrored what they needed from the old one. It was a little “cowboy coder”, but it would be a huge step up from what they currently had.