Sample Application Application Page 1: Fill & Download for Free

Shorter the better ... if you had to go over one page, make sure all your most critical information (recent jobs, key skills, achievements, relevant awards & certifications, etc) are on page 1.See some samples (especially the last one which is my own) at ... http://resume2jobs.net/sample-resume/. My own resume is 2 pages, but page 1 provides enough meat for readers to want to go onto page 2.

Most of the people struct to install cakephp in windows. So that today we are going learn installation steps about CakePHP.Step1:Download CakePHP package from the rapid development php framework. and extract that package and locate it your xampp htdocs.Example: I have an application and my application path is G:/xampp/htdocs/cakephp/sample. Here “sample” is my application root folder.“sample” application file structure:-sample --app --lib --plugins --vendors --.htaccess --index.php1 -sample2 --app3 --lib4 --plugins5 --vendors6 --.htaccess7 --index.phpStep2:You can access this application Page on localhost but still it has URL rewriting issues. So that in this step we avoid that URL rewriting problem by creating custom apache conf file.I have created one custom apache configuration file and locate it to my xampp/apache/conf folder.Example: custom.confI have located it to G:/xampp/apache/conf/custom.conf then i have written apache alias rule for redirection with directory access.Ref: Apache HTTP Server Version 2.2Here i have added my custom.conf configurationalias /sample G:/xampp/htdocs/cakephp/sample/app/webroot <Directory "G:/xampp/htdocs/cakephp/"> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory>alias /sample G:/xampp/htdocs/cakephp/sample/app/webroot  <Directory "G:/xampp/htdocs/cakephp/"> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> and then we need to do little modification in G:/xampp/apache/conf/httpd.conf file. Just include this custom.conf file in to your httpd.confHere is my codeInclude "conf/custom.conf"1Include "conf/custom.conf"And then you must add RewriteBase in application htaccess files. In my sample application i have followed like this type htaccess and also i have added that codesample/.htaccess<IfModule mod_rewrite.c> RewriteEngine on RewriteBase /sample/app/ RewriteRule ^$ app/webroot/ [L] RewriteRule (.*) app/webroot/$1 [L] </IfModule><IfModule mod_rewrite.c> RewriteEngine on RewriteBase /sample/app/ RewriteRule ^$ app/webroot/ [L] RewriteRule (.*) app/webroot/$1 [L] </IfModule> Sample/app/.htaccess<IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^$ webroot/ [L] RewriteRule (.*) webroot/$1 [L] </IfModule><IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^$ webroot/ [L] RewriteRule (.*) webroot/$1 [L] </IfModule> sample/app/webroot/.htaccess<IfModule mod_rewrite.c> RewriteEngine On RewriteBase /sample/ RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ index.php [L] </IfModule><IfModule mod_rewrite.c> RewriteEngine On RewriteBase /sample/ RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ index.php [L] </IfModule> that’s it. This is simplest way to avoid URL rewriting issue in CakePHP..Step3:Then. You must change the security salt in your core.php filelocation : sample/app/Config/core.php/** * A random string used in security hashing methods. */ Configure::write('Security.salt', '984743sdfhsdjkfhdsjkh87^*&$^78JKDFHDJKFHDSJKFJHD'); /** * A random numeric string (digits only) used to encrypt/decrypt strings. */ Configure::write('Security.cipherSeed', '473865278356283209832138');/** * A random string used in security hashing methods. */ Configure::write('Security.salt', '984743sdfhsdjkfhdsjkh87^*&$^78JKDFHDJKFHDSJKFJHD');   /** * A random numeric string (digits only) used to encrypt/decrypt strings. */ Configure::write('Security.cipherSeed', '473865278356283209832138'); No need apache VirtualHost concept but we have used apache alias concept instead of this.Now your CakePHP installation is ready. Put this url to your browser Page on localhost then you can your cakephp application

I took a job a little over a year ago and realized within the first week that I'd made a huge mistake.For background, the place I worked before this job, American Express, was really a great place to work, and when I was hired, I truly thought it was the place to be: great pay, great benefits, working with a good team, close to home, flexible hours…it was perfect. Well, until they decided to cut costs by sending my job overseas.Thankfully, they gave me advanced warning so I could find a new gig, and after updating LinkedIn, I started to get hammered by companies and recruiters.It took a while for me to find a good fit, and it was a damn good fit: pay was going to be even higher, cheaper medical insurance, location close to my parents…it sounded great. They were converting an existing Angular 1.3 web application , a financial reporting dashboard, to React, so it was right up my alley.(for you non-tech people, these are two different ways to build a web page)The company will go unnamed, but I will say it's the parent company overseeing multiple smaller corporations that spread over a wide range of industries; each company was a pet project of a millionaire who likes to brag about his amazing business acumen, which is utterly false.During the interview process, I asked a good series of questions; since I didn't need a job right away, I could be picky. Yes, benefits started after 90 days, great. I verified that on days when my kids had school activities, I could come in early and leave early. My primary duty was to work on the conversion and set up a high-quality React application, with a goal being a series of future applications for other areas of the company.It took me a couple days to see the first issue. We were a very small, 5-person team, working in a 20'x20′ room, and one of my co-workers, “Jeff”, was very clearly on the autism spectrum; he demanded absolute quiet in the office, and because he was talented, our supervisor tolerated it. I'm not sure if you get the vibe from me, but…that is NOT a good fit for me. I'm loud, sarcastic, and I laugh and joke…this was bad.We started clashing quickly, so I tried accommodating him. As soon as he would go to lunch or the bathroom, the whole room went nuts, then settled down when he returned.After my first two weeks, my daughter started her basketball season, so I came in on a Tuesday at 6am and left at 3pm to make it to her game. The next day, I was called into my supervisor's office and told that there was a misunderstanding in my interview; I was welcome to come in early, but I had to stay until 4pm every day.This one pissed me off. Not only is it generally accepted that coders work varying hours, but I'd discussed this particular item before getting hired.I put my foot down and said that this was a condition of employment…if the job interfered with my family, I would leave. She caved, but it still took far too long to make my position clear.My first day was also the day our Quality Assurance lady put in her notice. One of her primary reasons was because every time we pushed up code, something else in the application broke. This was a major concern for me, but I thought, “I’m amazing…I’ll fix this.”Our level of security was obnoxious, and it was a major detriment to our progress.Every entrance and every door required a security badge. Garage entrance: badge. Elevator: badge. Doors: badge. By the time I got to my desk, I would swipe my badge five times. Going to the bathroom and back took four swipes.Even from inside the building, I had to sign into a VPN that automatically timed out after 30 minutes. Signing into the VPN required a user ID, a password, and a revolving token. Signing into our application required a user ID, a separate password, and a separate revolving token. If you lost your Internet for any reason, you had to start over.I tracked it once; I had to generate a token for logging in 26 times in a single 9-hour day.I started the React application, working to get a good solid “base” to work off of. Jeff, who had never done more than a tutorial to setup a sample application, immediately began telling me I was doing things wrong, despite me working in React for several years. I would politely explain why I was doing things the way I was doing them; there would be much sulking, there would be much pouting. I got the sense that Jeff had initially planned to head up the React conversion, but the Team Lead wanted somebody experienced.At one point, Jeff grew tired of not getting his way and just re-did a huge chunk of my code. I was not amused.I ended up determining that a major reason why the existing Angular application was so slow was because the back-end was a nightmare of inefficiency. Looking at the code made it pretty clear that the API was written in Node by a student-level Node developer who was so excited to be writing in Node that he neglected to ask himself “Should this be written in Node?” The nightmare of spaghetti code and callbacks was next to impossible to debug, and after a while I was able to determine that a full 50–60% of the code was dead code, it did nothing.We had no unit tests or functional tests. When I asked why not (and I don’t even like tests), I was told that tests were a waste of time for good developers. I remembered what our QA lady had told me and thought, “Hmmmmm….” I pressed that we should do this and was rebuffed, despite the fact that bugs were a massive issue.Continuing on from the security discussion, every separate call to our APIs from the web site first required a request for a new web token from a “token server”, which we then had to attach to a single web request; it timed out immediately after use. It was the most inefficient application I’ve ever seen.As soon as I started the conversion, my role changed. As soon as I setup the basic React application, I had to start modifying the existing Angular app due to requests from the owner, who had zero interest in the conversion work.And when I say requests, I mean random, stupid requests that were always the new primary focus, and we had to get them done immediately. I spent Christmas Eve making a massive change to a page, staying until 7pm, only to find that the owner forgot that he requested it the next week, demanding that we revert it. The owner would call our team lead randomly and make these demands, and just so we’re entirely clear: this was a financial reporting dashboard, of a rather small company. This application didn’t save lives. It didn’t do anything of value, to be honest, aside from tell a rich man how much money he had. There was no reason for there to ever be a change that couldn’t wait for a week to pass.After 90 days, I inquired about my benefits. It turns out that benefits start the first of the next month after your 90 days; I started on the 4th, so I had to wait almost 4 months.We didn’t have “holidays”, we just had extra Paid Time Off to give us holiday pay; however, I had to accrue the PTO, so it took me a couple months to have it…I had to work extra hours the week of my first holiday so I could have the day off.As time wore on, things continually came to light that just made it clear that the company simply sucked. Absolutely horrible.I started to notice that there was a rather odd lack of minorities that worked there. Now, I was in one office, and there were about a dozen offices we occupied, but it seemed odd. So, I had access to a file server with pictures from corporate functions; surely I'd find some non-whites at the pictures from the last Christmas party, right? And I did! At a party with about 2500 people, I saw…a single black man…with his white wife…who was the employee. There were several Latino men at the party though, so I didn't feel quite so bad….The owner was a former Marine who enjoyed spending his money on big-game hunts of endangered species. There were reminders of it everywhere, like pictures of him with a dead rhino or tiger. Somebody had access to a video of him killing an elephant; I was not amused.In our office, there was a small server room, with just a couple servers; nobody could connect to them (our data centers were off-site), and from what I understand, only the owner and the head of IT ever touched those servers. I still don’t know what was on them. That creeps me out to no end.After about 5 months, my job had been reduced to about 10% of my time on React, 30% updating the existing Angular app, 30% working in Node, and the other 30% was taken up by Tableau, a data-analysis tool that had really pretty graphs.Just a reminder: I’m a React developer. It’s what I do. It’s what I love. It’s what I was hired for.I slowly started inquiring about new opportunities.We had our company Christmas party. I’d been there for almost 9 months. It was here that I found out I wasn’t eligible for an annual bonus, as I had to have been with the company since January 1. That was nice.I looked around me and saw a total of two African-Americans in the swarm of people; both were with their white spouses.I saw the collection of Latino men, mostly the same as in the photos I’d seen previously, but now I understood: the owner also owns a golf course. They were the groundskeepers and gardeners.A company with over 2500 employees, and not a single minority was employed for a position aside from “landscaper”.I left in February; in hindsight, I should have left much, much earlier.