|
in any case, now I'm craving a twinkie... 
|
|
|
|
|
His gravestone should say:
RIP
George Romero
Please stay put
|
|
|
|
|
He'll be back soon as the worlds first zombie movie director though.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Having more than 11 years of experience as an asp.net web developer, I have worked only for one company, developing their website
from the ground up and supporting it. I started working there without supervision of a senior developer, and had no one to ask my
questions and I was the only developer. I managed to find solutions and implement the required functionalities from Ebooks and
the internet. Also I had time to study new technologies and were passionate about it, while might have not been able to use them
for the company since they didn't want me to do so. After that I migrated to another country and now I have found it challenging
to get employed as a web developer. The employers are so hard and expect a developer with a lot of successful projects and strong
team work experience, etc.
I don't feel confident as a senior developer I am happy to go with any job even a junior one.
I have written my CV the standard way, and have applied to many jobs and have had several interviews. However, my special
background and also me not being an outgoing person who keep conversation going(introverted) has prevented me from landing a job.
Most of my life I have been behind my computer developing programs, finding solutions, studying new technologies. I would be
happy to work as a freelance developer also and know there are websites like upwork, golance, etc. But have not experienced that
and a newbie.
I want a quick way to a web developer job, even with a low salary. Any suggestion? It would be highly appreciated.
I am skilled in ASP.NET(web forms, mvc), SQL Server, HTML5, CSS3, Javascript, Jquery, just learned .NET Core, Entity Framework,
AngularJs, ReactJs, Bootstrap, SASS, git, MEAN, NodeJs.
Thanks
modified 15-Jul-17 23:41pm.
|
|
|
|
|
I have no idea in which country you're applying for positions but I suspect it's similar in most countries. In the US I've had a similar issue. I built an internet company from the ground up, had a few contract positions, and still have trouble finding work the "traditional way" despite my experience. Honestly, I don't have much advice besides what's gotten me more interviews and interest. The fact is HR doesn't always hire based on experience. Sometimes a single thing you say makes all the difference even though it shouldn't in my opinion.
So that being said - #1) brag. I don't mean be arrogant or full of yourself. No ones like that. But don't be humble. Brag about what you've accomplished. Remember, they aren't looking deeply through your whole GitHub, work history, or articles. They spend a minute or so glancing at your CV to see if you bring more value than the 100 other applicants. It's a numbers game. Focus on getting an interview through your CV - not the job. Get the job through the interview when you can speak your mind in full.
#2) Find a flaw. When you're interviewing, you're immediately in a "weak" position. If you can point to a flaw in their system and propose a valid fix, now you are in a dominant position. Your skills have improved their systems before they've even hired you. An easy way for ASP.NET developers is to point to common security flaws since they're unfortunately often overlooked.
#3) Be yourself. Don't try to be who you think they want. Just be you. If they bring up a topic you're interested in, talk to them about it. If you can teach someone during an interview, that's another powerful position you put yourself in.
#4) Don't get depressed because you did everything right and still didn't get the job. Sometimes you lose the job simply because you didn't have the same interests as the person interviewing you. People form opinions of other people not based on merit but on feeling. I know from a friend in HR that they once hired someone simply because the manager on the interview loved baseball and had a good conversation with one applicant about the current baseball season.
#5) None of this is fact. It's all my subjective opinion based on experience. Nothing more. What works for me might not work for you and vice versa. Just keep trying and building your portfolio. As a fellow introvert I know it's hard connecting with people in 30m or an hour during an interview, but if you really show passion for what you do it'll get through. Whether that's enough is up to them. Their loss if they pass.
Best of luck!
|
|
|
|
|
Excellent post! A few things to add:
Jon McKee wrote: #1) brag. I don't mean be arrogant or full of yourself. No ones like that. But don't be humble.
Go through your work history and make a list of accomplishments. Practice talking about your accomplishments -- mirrors are great listeners, and you can watch your own face and body language. Know your own accomplishments well, so you can talk yourself up without sounding like rote. This gives the interviewer a sense of your abilities and it makes you sound more confident than awwwing and uhmmming through the interview.
Jon McKee wrote: #3) Be yourself. Don't try to be who you think they want.
Never be afraid to say "I don't know" if you don't have an answer. If not knowing something costs you that job? You probably don't want to be there anyway.
But if you can relate something you have done to something the interviewer is asking? It fills the gap. This doesn't work in all cases (nothing does) but in my experience it works most of the time.
Jon McKee wrote: #4) Don't get depressed because you did everything right and still didn't get the job.
Absolutely! Two things to consider:
1. There may be hundreds of people vying for the position you are interviewing for. Only a handful get interviews so if you got an interview you have already done well! Focus on that important fact, and not that you didn't get the job.
2. You may be the right person for the job -- skills, abilities, personality, etc. -- but the person who got the job may be a better fit. You did nothing wrong -- simply said, you were not perceived as the best candidate. On this one job. Learn from it and go on to the next one. Remember, you got an interview so you were probably in the 95th percentile (or higher).
Think about any answer you gave that you don't think was good enough. Figure out what you should have said and be prepared for the next time it is asked.
|
|
|
|
|
Excellent points! I know I personally have an issue with sounding a little "rehearsed" because I do. I have an involuntary physical reaction to public speaking and interviews but not stakeholder presentations for some reason, haha. It's not that I'm mentally nervous anymore (at least not consciously) but I still have the physical reaction. If I already have a good layout to what I want to say I can focus on suppressing that reaction so I don't sound like I'm "choking" as much. Usually only lasts about 10 minutes but those minutes are probably the most important for building a first impression.
|
|
|
|
|
devboycpp wrote: The employers are so hard and expect a developer with a lot of successful projects and strong team work experience, etc.
Since you've worked at only one company for 11 years (which in itself is impressive nowadays):
- break apart your work into discrete projects, even if it was for the same end product
- for each project, indicate the key people (even if it's only one person, but I would doubt that) you had to interface with for requirements, reviews, etc.
You've already identified 3 broad categories: design, development, maintenance. I suspect you can elaborate on the different requirements (projects) in each of those categories and the "team work" needed to accomplish the project. After all, you can't develop a website for a company in the dark (though looking at some websites, it seems that's exactly what happened.  )
Marc
Latest Article - Create a Dockerized Python Fiddle Web App
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
|
Get in touch with these guys, they'll hire anyone (it'll get you in various places quickly but you'll need to set yourself up as a contractor wherever you are based).. Home | Capgemini Worldwide
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Brent Jenkins wrote: .. Home | Capgemini Worldwide
Do you have experience with them? That's one of the most convoluted websites I've seen in a while, not to mention some glaring formatting errors (like a huge font the lead consultant job listing I looked at) as one drills deeper. It's also surprising that when you finally figure out a link for applying that doesn't take you in circles, you get a "come visit us." Riiight. I smell BS.
Marc
Latest Article - Create a Dockerized Python Fiddle Web App
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: Do you have experience with them?
I have a couple of times. Once they wanted to hire me for a short term position on London. The requirements were really flaky, sounded like nobody really understood what was required. I turned it down.
I've worked at big companies that use them and to be honest, their 'staff' seem mostly useless. Mainly because here in the UK they seem to bring in developers and testers from India who just don't have enough experience (not their fault), get them the visa to work in the UK (which is what they really want), pay them a low day rate and pimp them out to big companies as their own 'highly experienced consultants'. I feel sorry for the guys who get caught up with them, but for a year or two's suffering it can open the door for decent guys to move on.
I don't get why big companies don't realise what companies like Cap Gemini are about. It's a con. I've even seen one company sack highly experienced staff (some with over 12 years experience) and replace them with Cap Gemini guys just to (in theory) save a few pounds or because of ludicrous changes in their hiring policies.
Taking all that into account, for a starter with little experience and a willingness to get involved, it might help them get a foot on the ladder. Just don't expect Cap Gemini to look after you, it's purely a business relationship.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
One of the things I've learned is, no matter how much you study, there are always things you get completely oblivious about, specially if you're solo (and for a long time, like yourself).
After some time I learned that I need to get out there, study other people's projects. For example, when I first saw a project that implemented caching using Redis, I was stumped, I felt ashamed of how long I've been without even hearing about. It's something I never found on the books I read.
And this is just one example, there are many, many problems and solutions, from down to implementation detail, to logical and physical architecture. You may think that you made something work and that you'll know a lot, but the fact is, you usually don't (I'm including myself in this).
There's a lot to learn. Think to yourself if you have ever designed highly scalable systems, which could easily handle, say 5 thousand requests per second, that can scale horizontally and implement design patterns which makes it easy to maintain, have decoupled layers adopts a microservice architecture, can be deployed without breaking availability, run automated unit and integration tests before a blue green deployment scheme.
So, study a lot of other people's projects (study stack overflow architecture, which they wrote an article about). There are many on github. Join a community you can prepare for interviews (VanHack is a good one).
Good luck.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
A couple of points that should help you out.
1) Think in terms of value.
- What value do you bring to the table?
- Why do they value Teams? (what would YOU value about being on a Team?)
- Value Honesty? (But only positives. I blew an interview by criticizing an ex-ex-ex boss!)
- Why do they want to spend all that money on someone? Why should it be you?
(You said you were self-motivated, and continued to learn/study)
2) Your CV should NOT be a check list of skills, but a statement of IMPACT.
- NOT: Wrote reports for management.
- YES: Redesign reports into a dashboard, improving user experience, and reducing paper waste!
- The latter has IMPACT in it. YOU GET PAID FOR IMPACT!
- This is where the "bragging" comes in. You have to lift up what you have done.
3) Have questions.
- Do you have Team Activities to foster better Teamwork?
- Do you have brown bag lunches where Team members share about their recent learns?
- How do you handle Developer Conferences and training?
- Is there a Team Library of books that the team recommends everyone on the team read?
- Is your Team Cooperative or Competitive?
See... Just asking the right questions... But test them on other people before using them!
here are 3 to think about (Not all questions are good!):
- Do you want me to Kick Butt AND Take Names?
- How does your Team handle Conflict Resolution?
- How do I report a Team member for breaking the rules?
4) Ask yourself up lifting questions before your walk in. Questions you know, and will answer EXTREMELY positively. And ask them, and answer them, in your head. To increase your confidence.
(This is to override the self-doubt questions we all ask ourselves constantly)
- If they hire me, how hard will I work to make sure they realize it was a GREAT DECISION?
- What will I do to make this company better?
- Will I be here on-time?
- Will I rise to any challenge?
- Will they love my passion? My Energy? (for me, find better ones for you?)
these questions should elicit your feelings of competence. What you are strong at.
If you can't find any. THIS is where your lack of self-confidence is coming from.
Find a weak one, and build from there:
- Will I give it my best?
- Would it be great to get this gig?
If you can't answer YES to that one. Practice saying "Would you like fries with that?" LOL
The point is simple. The company is in NEED of a developer to make an ASSET worth money to them.
You are in NEED of someone who needs to hire a builder so you can eat, but also so you can build things you enjoy building?
Now, there is ONE of them. And many of you. How can you stand out as a clear choice?
- Show some enthusiasm
- Know your stuff
- Be able to explain what you have done with passion (hitting on the IMPACT).
- Show that you are adaptable, and you are POSITIVE.
- Know THEIR values. Get to their values?
- Avoid divisive topics (Politics, Religion, CODE FORMATTING RULES!)
Finally, during the interview. Since you are an introvert, you probably don't blurt out answers. But make sure 2 things:
1) If it is a good question: MEMORIZE IT for later practice
2) Tie your answer BACK to your CV when you can:
Have you ever had to optimize a complex query written by someone else?
Absolutely. In fact, that first job I listed, XYZ, I walked in cold, and took over for a developer who was gone. I had to learn the whole system, and immediately work out a slow query slowing down the website. It became a priority. Once I understood the query, I XXXXX and it was appreciated so much, my boss took me to lunch to thank me...
Notice how wordy that is. Because as an introvert. Your normal answer would be:
Yeah, sure.
But can you spot the differences? Mine is long-winded, but you got to know me. It says:
- Team Player
- Can learn Quickly
- Can work Priorities
- Likes to be appreciated
- Is social
- Not awkward around management
I used to interview people a lot. People with experience make the interview about a blend of THEM and WHAT they can do for me. New people are about buzzwords and tech, and HOPE.
I really hope this helps... Sorry it is so long.
Also, stating your Country (Probably UK because you use CV and not Resume) can be helpful. I am stateside, so we are a bit more aggressive. Adjust accordingly.
|
|
|
|
|
I find it extremely interesting that no one suggested using LinkedIn.
I've been gradually refining my LinkedIn page. I sometimes update it before doing the resume update.
A web developer should be able present himself (or herself) favorably on a LinkedIn page.
I (and I suspect others) would be willing to have a look at it and offer suggestions.
|
|
|
|
|
|
Quote: forced to post by wife
Oh dear, after all these years posting, is that really you Peter.
How can we be sure now...
|
|
|
|
|
Kornfeld Eliyahu Peter posted: I forced to post it by wife...
How the mighty have fallen... 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
We're not one bit sorry for you Peter. You have seen the stuff that Griff's cat is forcing him to post!
... such stuff as dreams are made on
|
|
|
|
|
Better plant that tree now
|
|
|
|
|
When will you guys learn, Her Indoors is always in charge. That's how the marriage lasts.
|
|
|
|
|
|
That's what I mean! My bachelor life has been over for 54 coming up 55 years. I've got that hang-dog, downtrodden look. But then so does everyone else that's lasted that long.
|
|
|
|
|
|
There has to be some solution ...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
