Hot answers tagged lamp
37
Again, this is only for my plant, and I'm the only one who will ever be supporting it unless I leave the company, and then my replacement would be supporting it. Not someone else already in the company.
1 -- Don't Assume you're the only one who's going to support this. You do like your sick time and vacation, right? What if you need to take extended ...
10
Congratulations, you've embarked on the single riskiest type of project that is possible.
Complete rewrite, second system, unresolved people problems, lack of technical direction, up front willingness to make it big - any of those are red flags that would cause sane people to run screaming the other way. The only bonus is that it would be hard to pick a ...
9
That being said, is it better to violate the company standard and go with the setup that I can support better, or is it better to go with the setup that the company can support better if I ever were to leave, even though no one currently in the company can support their own standard anyway?
It is a management decision. Make them know your concerns and ...
8
I hate to say it, but be prepared for the worst. You will likely be maintaining someone else's possibly horrendous code. You may not be able to "fix" it the way you want because the person that created it is still there and still calling the shots.
On the other hand it will be very fulfilling to work on larger projects and be part of a team.
Best thing I ...
7
A daily occurrance of WTFs. Not just in code, but also how people interact with each other, how projects get started and killed, etc. It is possible that you will start in a good environment, but there is always something that does not make sense (which could be good to know, so you know what to avoid).
7
Do you have any aspirations for promotion, or working on other projects? If so, I suggest that "doing your own thing" will have two negative effects almost certainly resulting in (paraphrase) "I will be the one supporting it, until I leave"
Because you chose not to follow the company standards shows you are not particularly suitable for more senior roles, ...
5
The best place I know of to host a Java Web application is on Google App Engine. It scales really well as it's free for low usage. Once you hit your quotas it's then pay as you go.
Most Java Web hosting can cost anywhere from $25 per month and up, but Google App Engine is free to start.
Our organization hosts many Web applications and Web sites on ...
5
Does everyone tend to use the same OS/version?
No.
We specifically write software that runs on a variety of Linuxes (Lini? Linen?). A same OS or same version isn't particularly helpful.
Unless one is writing kernel-oriented software, exact Linux versions don't matter the way exact Windows versions seem to matter. Why? Linux conforms to a standard ...
5
Companies have standards for a reason, if there is a formally stated standard that says to use x, then youu need to justify y.
This doesn't mean that you can't use y, it does mean that you should understand the reasoning behind the standard and and get approval before violating it.
Perhaps after you understand why, you'll no longer want to violate it, ...
5
Take a deep breath and relax. Things will go at different paces for different reasons.
Sometimes things will seem slower, sometimes faster.
You'll have people to share problems with - and to help them with theirs.
You may be rated as much on how you get on with others as well as the code you write.
You'll need to figure out what 'style' the office works in ...
5
Ask yourself why you want to move from LAMP; is it because of deficiencies in the stack, or deficiencies in the practices and design around the original application? Bad code can be written in any environment, from assembler to the most astronautical architectures.
Currently, my company runs a highly scalable set of web services on Linux, nginx, MySQL, and ...
3
Most web applications I have installed have a setup "wizard" that runs when I first navigate to where the site is hosted and it will run the scripts using some nice interface, which is a very nice feature.. However, the scripts are all there for me to see usually and i have also bypassed the setup wizard all together and just run the sql scripts myself.
...
3
There isn't a single authoritative source for LAMP. A good place to start is subscribing to the news on the front pages of each of the components: your favorite Linux distro, apache, mysql, and php. They should all have rss feeds. Mysql even has a facebook page. Likewise for related technologies you may be using, such as jQuery or a CMS.
There are ...
3
As far as why LAMP has a bigger mindshare (if not market share) than WAMP: probably because the LAMP components don't have licensing costs. That makes getting started cheaper. Cheap Linux hosting has to be cheaper than cheap Windows hosting just for that reason alone. The free/libre nature of LAMP makes it possible to just try it out for free. From there, ...
2
One option would be to get a Linux virtual server and install the software of your choice on it (that might even let you stick with Oracle products if that's your preference).
If that's a little too much setup and administration for you, you could look at using Bitnami's TomStack. (There are some Amazon EC2 Machine Images listed at the bottom - inlcuding ...
2
Yes. 1M pv/mo is not that much. LAMP can handle that without any problem, as long as you create your site according to best practices. Which means multi-level caching, client side optimization etc.
Recommended reading:
1
In my work we have two main ways of doing it: SQL inserts in a version controlled package, and setting up as much data as we can via internal tools.
Since the SQL inserts are versioned then we can branch those alongside any application updates and create a modified set. This can then be merged just as with any other code. One word of advice with this method ...
1
YAGNI applies there.
If it's for your use only, use whatever works best for you.
If it's for distribution, then you need to provide at least instructions on how to use the schema file, or a build script. The easiest it will be, the more people will be interested in going with your application.
1
Using scripts to create database used to be the case some time back. It was also the time the database administration is a full time profession. Our application used to ship with oracle sql scripts to manage db creation. Some time DBAs then gave feedback about missing index etc, for performance.
Today we ship with pre-built database (postgres) and ...
1
You should go with a setup script, which the installer can customize.
There is much more to defining a database than you can easily include in the application code. As a system scales up data placement, index options etc. become more important. Its nice to have an install script where you have fine control over all the database parameters, rather than rely ...
1
Are you planning to distribute it, or you're the one who's going to install it? In the former case, go with a setup script (or schema creation on the first run). In the latter case, a schema file would do. The upside of manual schema creation is that you don't have to give the database user that your PHP files are connecting as any schema editing rights. The ...
1
Yep, you have a problem - but the solution is not to rewrite!
Now, solutions for actually fixing your problem in a constructive way.. you need to start shearing off layers of the old system and replacing them, that's clear, and that means that you need to maintain compatibility with what you already have. So that sounds like web services (which you can ...
1
According to Joel Spolsky - the single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch.
You say:
poorly written due to a large number of patches and possible hundreds of programmers
That is not the reason. Joel explains all in the following article ...
1
I don't see any path from this that isn't full of failure - one of the biggest draws of the LAMP stack is that PHP has a lot of libraries, and if the code is already in PHP you're certain that PHP supports anything you need to do.
You can write bad, unmaintainable code in any language, but your choices for "Enterprise" web are basically Python, Ruby, C#, ...
1
Because as you say the team is all ready there, you job is to fit on that team and be a part of them.
To archive that you need to follow them and not make them try to follow you - what I mean: to follow them, to let them guide you, to let them show you the road, and to make that you need to do what they say to you and not make many arguments.
At the end ...
1
In this case you need to follow the standard. If the standard doesn't seem to apply, you need to talk to your manager about doing it in a different language.
Of all the standards to follow in development, I personally feel that language choice is the most important. Ignoring the standard language choice in favor of one you are more comfortable with leaves ...
1
I think that you can anticipate many of the problems that could arise from this and make a detailed plan for if and when you ever had to leave the company.
One problem that could gum up the works would be if you left and HR had to search for your replacement. Given they either actively try to understand what you did and hire according to the skills ...
1
As developer, the most important skill to focus on is development. There's a lot more differences between Linux and Windows than case sensitivity. A LAMP dev should have a strong server management skill set, but you're not a sys admin.
A couple of concrete goals:
Being comfortable on the command line is a must. Be able to set up, secure, configure and ...
1
This is a good question and has been circulating for awhile. The main difference between windows and linux is that the linux filesystem is case sensitive. This can cause issues with people going from windows to linux, because myPage.php and mypage.php are two different documents. With linux you can install extensions for what you need and not for everything. ...
1
To those that work in these platforms, was your initial experience similar?
No.
Django was quite simple. Python is quite simple.
spaghetti of dependencies, versions, and install procedures
You have to be much more specific about your experience. It was all pretty obvious from the Django documentation.
Only top voted, non community-wiki answers of a minimum length are eligible
