It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 14 years ago.
I feel like I die a little on the inside every time I work on converting this legacy code to Web app. The database is crap. All the filed and column are nvarchar and blank (Empty string) suppose to mean Nothing (Null) instead using Null to mean nothing. For something like percentage instead of using decimal. You tag on extra two zero and store it as string (nvarchar). As i dig into the database, working on the code and discover how the old legacy app work. I die a bit.
I sympathize. Dying a little bit is bad for your health. One way to feel better is to fix it, a little bit at a time. Make it a little more right and you will feel that much better.
Yes everday. We have a mixture of utilities that are either really really bad C++ (MFC) or VB6 which by implication is bad ;-)
I worked for 5 years as a contractor and part of that job is working on really really bad code. By the time a contractor is brought in, things are usually pretty dire. My soul died years ago!
I'm doing it right now. I'm working on architectural assessment of migrating to a .NET solution from:
old VB6 code that has dozens of forms and only a couple of classes
a SQL Server 7 back-end with 60+ DTS packages
It's all very old and has practically no error-handling.
I go cry now...
yes, I have had that. One is where the database is made up of excel like tables. With some of the same data in every table.
Then there is the flowchart based program that does the data entering...no naming conventions, useless or no comments, unexplained constants all over the place... and don't even get me started on the flowchart software itself...
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I am working on a team which is making a website similar to, say, Instagram. Similar in the sense that we are employing similar technologies in the back end, but the concept has no relation to Instagram.
Anyway, I was reading this article here which describes Instagram's compete stack:
What Powers Instagram: Hundreds of Instances, Dozens of Technologies
I'll be honest - I was quite overwhelmed by the number of different technologies they employ. What I want to know is that is it necessary to start with so many different and specific technologies to make something which can sustain a lot of traffic, and continue to work just fine?
Currently, we are working with an Apache web server, MySQL database, Django/python framework, HTML/CSS/Javascript front end, and Ajax to make things more dynamic - you know, the works. We are aiming to utilize Amazon Web Services to host our project. Our project is being built on Linux machines (Ubuntu).
Do we need to use a lot of other software packages/tools to ensure our website is top-notch? It is fully functional from our perspective. This may seem like a novice question, but we are novices relative to Instagram developers.
Start simple. Specialize as you have need.
Instagram is a MASSIVE property, and serves a lot of traffic under uncommon circumstances. Don't take their infrastructure as the way to start things. Start with what works, and then as you find things don't work, replace them.
As web projects grow and mature over time, they will often incorporate more and more specialized technologies and architectures to accommodate their specific needs. Don't take their infrastructures as a template, but rather, as a lesson to expect to grow and evolve your infrastructure as your product evolves.
Measure everything. Know where you need to get better. Iterate. GOTO 1. :)
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
How does one write a language? I really can't imagine how this would be done. Do you have to write some binary code? I think I'm far from capable of writing a real programming language -- I'm a hobby programmer -- but I just want to understand how it works.
I don't ask for 'a working demo' (because I presume that'd be a demo like ten pages long) but the general steps one has to take, what you have to write and what that what you have to write has to do, what language do you recommend (that I think I'm not capable of it doesn't mean I don't want to try).
EDIT:
So is my assumption that one would write some code in an arbitrary language that translates it into an already existent language and compile that to machine code?
PS I accidentally voted to reopen my own question, but I think it's reasonable it's closed, so how can I undo that?
Start by writing a specification and grammar that describe what your language does.
Then, write a parser and compiler that turns your language into a simpler language, such as C or MSIL or Javascript.
Finally, run an existing compiler for that language.
You may want to look into LLVM.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
i wanted to ask a question that i myself have been asked in class by our database teacher;
What makes MySQL different from other Sqls? I've always been using MySQL due to the fact that's what we have been taught when i learned how to program websites, but honestly? I dont know what makes MySQL better then other SQL's(For program development) such as;
SQLite
MS Access
PostgreSQL
MongoDB
I was hoping someone could point me towards the answer or perhaps even give me a explanation of it.
I hope it was alright to post this question here as i'm unsure as to were else it should have been posted.
I'd choose MySQL over
SQLite, because SQLite is too "lite" for a lot of purposes; it does not have multi-user access, so would not work quite well in server environment
MS Access and PostgreSQL, because they are less common and I'm more likely to get useful community support for them (especially valid for MS Access :-)
MongoDB, because that is not SQL database at all, and you've asked about SQL databases
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
How come many startups used MySQL or PostgreSQL rather than MongoDB when they started? Many of them seem to migrate to MongoDB later - why's that? Does it need a lot more effort in working with MongoDB? Why don't they just jump straight into MongoDB?
To quote User Dan Grossman:
You dumped a decades-tested, fully featured RDBMS for a young, beta-quality, feature-thin document store with little community support. Unless you're already running tens of thousands of dollars a month in servers and think MongoDB was a better fit for the nature of your data, you probably wasted a lot of time for negative benefit. MongoDB is fun to toy with, and I've built a few apps using it myself for that reason, but it's almost never a better choice than Postgres/MySQL/SQL Server/etc. for production applications.
Mongodb and PostgreSql thoughts
MongoDB isn't SQL based nor is it relational which takes it out of the comfort zone of most developers and out of the common lingo of most CEOs. There are enough options that don't require re-inventing the development wheel and dealing with the learning curve of a different technology.
Also the first public release was in 2009, so you're still talking about a fairly new platform and people are going to be hesitant to use it. Not to mention the experienced developer base isn't as wide as for a SQL based DB.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 12 years ago.
Lets look around for famous programming languages and their runtime environments and frameworks...
C, C++ are hard and complex for a
small and simple application.
Java is going to be a commercial
stuff for Oracle.
PHP is good but only about web.
C#, VB.NET and commonly .NET
Framework is Microsoft product.
Mono project? A few people trust it
as i saw!
Python and ruby and ... They are good
but not good enough!-
I hope i don't forget any other famous language!
My question is:
Does Open Source World Need A New Great Programming Language?
This question will probably be closed as subjective but here's my subjective view anyway:
Definitely not, the open source world is already far too fragmented already and has more than enough languages.
There are already fantastic open source communities around Java, Python, Ruby and PHP. All are great languages for the domains that they are designed for.
There are also some great upcoming languages such as Scala, Clojure etc.
It's a waste of time trying to be perfectionist about what language to use since everyone has a different idea of "perfect" and the value in a language lies in it being well used and providing an open, comprehensive platform for development, not in in being the "perfect" language for just two or three people in the world.