When is too much for cakephp? [closed] - php

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I've been asked to quickly build a low traffic app with 5 year projections for 700,000 users. I'm banging it out using Azure/CakePHP/MySQL with Zurb for frontend. I'm new to this game and budget is tight until we get funding. This app is to demonstrate and actually be used live initially.
QUESTION: When does CakePHP become clunky/bloated code from a load perspective? Does anyone have stories of largest load CakePHP site?
I'm trying to build in to the business plan of when the rewrite will be required for efficiency. I know there are lots of variables here and I'm probably showing I don't even know enough to know I don't know but I can't find any hints anywhere and I'm 2 weeks into this project. I'm asking here because I land on Stack sites many many times a day to find answers quickly.
Blast away on the newb as long as I learn something from your snark. I don't mind looking stupid as long as it helps me become less stupid even just a little.
Any input unrelated to my exact inquire is highly welcome. It will all mean something. I've been out of the programming world for 12 years. A wee bit has changed in that time. I forgot how much fun it is. I'm back to trying to solve code probs in my sleep.

I run a site in CakePHP with around 2 million users subscribed and handles a few million hits per day. You should be fine:)

Related

How do you deal with other people’s messy, substandard code on a new job? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
This is a general coding question so please feel free to answer any way that is applicable to you.
When I work on new development for clients that I freelance for I write frameworks, write all the front and backend code and everything is just great.
On numerous occasions, I’ve been brought in as a contractor and sat down on day one to try and do what I’ve been asked and been frustrated, terrified and mystified at past work others have done before me. The boss always expects fast results but I feel like I need a week or two just to really get up to speed on everything going on with these complex and slopily written "frameworks" that have been done before me. Is this normal? If so, how do you PHP developers deal with this challenge?
Buddy,
I am currently in the same situation. Just to avoid being all 'Zen' - we have a job to do - lets get it done and move on to the next job.
Aim to meet your goals - get the new functionality working and just let the employer know the code stinks and that you would recommend he gets that sorted out asap. Raise the red flag and let it go. You know that you have done your job.

PHP solution for Epaper [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am working on a news paper website which has epaper facility. I am developing it in php.
Is there any script or something else where I can learn how to make an epaper site.
I want solution like this http://epaper.timesofindia.com/Default/Client.asp?Daily=TOIM&showST=true&login=default&pub=TOI&Enter=true&Skin=TOINEW&AW=1333084145015
Please help me out..
ePaper in your context is a web app developed by Pressmart, and it appears to be proprietary, or at the very least not developer-friendly. So I highly doubt there have been advances in PHP libraries for it.
I'm sure as a partner, they have internal documentation and tech support that you can request more information from. They may even have a web API with PHP examples (I've seen worse companies that knew they had to keep up).
This is all info I've gathered in the last 7 minutes, so there may be more out there. But you should always reach out to the developer support of the product if they don't have easy access to documentation, as this is a sure-sign that there is not a large population of developers in the general community that will know what you're talking about, let along give insight.

is there any profit of using E-commerce PHP Frameworks? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to know from a technical view if there is any profit of using E-commerce PHP
frameworks instead of hard coding every single detail in the website.
I see everybuddy talk about using those but is there any real profit (not just because it is more easy it should be done no ?) for now i have a project of a commercial site and i have build-ed from scratch the search engine and the navigation system and some other few things any help please (NO VOTE DOwn PLEASE if this is a bad question one comment and it will vanish).
the good things in E-commerce PHP frameworks is that they are well documented, easy to install, full functionality, less to work as updates and upgrades most of the time.
if you want to build one from scrach you should take a note that it could last several months (depends on the size of the project) and you will never know what bugs you have ... as the only person who knows the backend is you.
there is a profit ... since a new one from scrach takes a lot of time and testing ... and time=money ...
Why don't you test, most of them give out demos and there are a lot of them that are open source ...
e-commerce is more of a pain in the ass than you think at first. you have to make a large order form and build validation and sanitation scripts and spend a lot of time making the layout not look like scrap, encryption and SSL integration and then after all that it needs an admin with way too much to account for. i've done this and ... never again.

New programmer work rate and expectations [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I'm a new graduate and yave just started working a few weeks past as a web programmer. I've kind of been thrown in at the deepend and have been put straight on a project that appears on the face of it to be relatively simple, but there a lot of little intricacies that are making it quite difficult.
What sort of work rate will employers be expecting a new graduate to work at? My employer hasn't said anything but I feel like I am taking much longer than they anticipated - perhaps even regretting that the have employed me in the first place. Also, I am asking for help with logic and some best ways to tackle some problems and I also feel they think I should know more than I should. Again what would an employer be expecting from the level of a recent graduate.
I want to be as good as I can and learn as much as possible but I constantly feel under pressure as I keep thinkin I should be getting through mug more work than I currently am. Is this a common feeling in new programmers and how would my employer approach it if I wasn't performing up to their expectations. Like I said, nothing had been mentioned but I do feel they are wondering why they bothered to hire me.
Some advice on this from experienced developers would be great.
"Rate" is a hard thing to quantify when talking about software - as you note, some simple things aren't easy, and some complicated things aren't hard. In general, the most important thing is to communicate with your employer. You may be afraid to talk about the problems, but it's much easier to talk about them now than to keep your mouth shut and only announce problems when your project is due.

Localization as an afterthought-- screwed? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
So I signed on with a startup web development company as a subcontractor. They are putting together a large, complex user/product management system for a company that needs to support multiple levels of hierarchial localization. I signed a 3 month contract, and upon looking at their code, wish I hadn't.
They opted to write their own MVC framework (I guess the client company didn't want to use a prewritten one) and it's extremely poorly written. There's SQL scattered throughout almost every model view and controller (and there's no parameter-based find methods, it's all SQL) and they haven't even THOUGHT about localization yet-- something that will have an affect on nearly EVERY query.
The due date is 4 months away, and I honestly think we'd make good progress by scrapping the whole thing and going with CakePHP. Have any of you been in a similar situation, and what did you do?
PS: This is written in PHP/MySQL.
Rewriting from scratch is almost always the wrong idea (Read Joel's article Things You Should Never Do -- Part 1). But you have to start implementing small changes (big in your case). The sooner you get the code cleaned up the better it is for developing in... Get a sane data access layer and try to sort out the ad-hoc MVC first.
Also, while you are fighting battles, start planning out what needs to happen and get the upper brass used to the idea that some features might not make it in. I don't know your code base, or big or how messy it is... but if it is really bad then they should be prepared to ship a product minus some features rather than a half-baked solution.
Take charge on these issues, you (like the rest of us) get the pleasure of inheriting the sins of a codebase's previous owners. Is there any chance they would extend the contract or pay overtime for extra work you put in?
When you work for someone, you play by their rules. I've worked on a couple of sites using Expression Engine. I hated every minute of it, and I strongly recommend against it every time it comes up with my client, but what can you do, other than grind through the work until you're done?
Feel free to offer the suggestion about CakePHP, but I would drop it if nobody wants to hear it. Be happy you're only on for 3 months.

Categories