Freyjadour
Member
Ftfyclients are a pain in the ass...
Ftfyclients are a pain in the ass...
If you guys could upload html and css files to a cms, and this cms generates form code and places it in your html, is there any kind of framework you would prefer? The current forms are very old, ugly and not responsive. I'm thinking about moving to Bootstrap or is that already out of fashion?
Just pick apart the styles you'd use from bootstrap instead of using the whole framework.
How do you guys create a website and just like what you created? I've been redesigning my portfolio website for a while now and I'm just not satisfied with it. Something always looks off.
I've got an interview for a job on Tuesday, sort of a dream job. I've been told the interview will take around 2 hours and I'll be doing paired programming. I've never done paired programming before, but it seems like I great way to learn so I'm intrigued.
Good luck! I've got the same kind of thing tomorrow with a "big" internet company, and it's scaring the crap out of me. It's actually online, because I'm in a different part of the country, so two developers/managers will be quizzing me, watching me type in an unfamiliar editor, and talking to me as I program. Plus, I have no idea what they'll be asking, just that it's mostly front-end development.
It just seems weird, because it's so different from how I normally develop: sit and think for a while, wire up a crappy prototype, then write and test (and rewrite and re-test) a real version, doing plenty of online/book research to help make sure I'm getting things right. I'm very methodical. Not slow, necessarily, but to an observer, it would sure seem so. I don't write things on-demand, in a time crunch, from scratch. I don't know if I can.
It seems like an okay way to test rote knowledge (assuming the interviewee isn't too nervous to come up with the answers), but I would've preferred an overnight "homework" test, which they then quiz me about thoroughly, to make sure I understand what I wrote, and why. That I could ace.
I've got plenty of references and lots of delivered code over my career to show that I know how to develop. But I'm just afraid that I won't be able to make them believe it in this setting.
I'm absolutely petrified. Not of how I'll perform, since at this point, it depends more on their questions than on me learning anything in the next 24 hours. But I'm afraid of how I'll feel about myself if I fail.
I've got an interview for a job on Tuesday, sort of a dream job. I've been told the interview will take around 2 hours and I'll be doing paired programming. I've never done paired programming before, but it seems like I great way to learn so I'm intrigued.
Anyone had any experience like this in an interview setting? I'm not sure how best to make a good impression, but hopefully I'm knowledgeable enough to do so.
Edit: This will be in PHP/JavaScript,HTML,CSS,etc
I wouldn't feel too bad if you fail, because even if you have talent, you'd better hope they have the talent to spot talent. The biggest difference they should spot between a junior developer and a senior developer is that the senior developer takes more time to think. The reason I got my current job is because I was honest and didn't try to pretend I had the infinite knowledge of the universe behind me. I don't have much experience with these things though.
I did an overnight test for this job, a code kata, it was pretty simple, but it seems to have landed me an interview at least so hopefully I did a good job. I'll leave it up to the fates on this one, I have no idea how many people are applying. I'll go in with enthusiasm and hopefully I can prove myself in 2 hours. But it still feels like random luck!
I wouldn't feel too bad if you fail, because even if you have talent, you'd better hope they have the talent to spot talent. The biggest difference they should spot between a junior developer and a senior developer is that the senior developer takes more time to think...
I did an overnight test for this job, a code kata, it was pretty simple, but it seems to have landed me an interview at least so hopefully I did a good job. I'll leave it up to the fates on this one, I have no idea how many people are applying. I'll go in with enthusiasm and hopefully I can prove myself in 2 hours. But it still feels like random luck!
When it's with a client, reduce the time they're exposed to the design. Things you look at too often and too much always become bland and such over-exposure is never representative of the casual use most people do of a consumer website.What do you guys do about the scenario where a client (or coworker) of yours gets sick of looking at their redesign before it even goes live?
I have seen this a lot in the duration of my career, where you'll work up a redesign of site or application, and after x-amount of design review sessions, and x-amount of code reviews and project meetings - and sometimes even team members will get tired of their new design before it ever sees the light of day.
How do you "manage up" to internal or external clients, higher ups or PM's - to get them to see the forest through the trees. It kills me to see the initial WOW of a redesign loose its impact while the development team is in hardcore heads down code mode. It's so demotivating, and I have battled this kind of thing for a long time.
I saw it just yesterday. A new design that everyone freaking loved and suddenly yesterday a woman called a meeting to "Touch Base" and tried to reset the whole thing - where only a week ago she was raaaaaaaving about it. She's a particularly ignorant and uninformed client but weilds the Cudule of Xanthor at my company. Her comments were heard but not acted upon. It still took the wind out of my team's sails.
How do you guys in this field negotiate those treacherous waters?
My specialty is not web design but I am still interested and work closely on some related projects.
The way I see it though, is it best to always use svg icons and CSS gradients and shadows on pages people will often visit? It's better performance right, and anything else is just old habit or for really old compatibility?
In my experience, the best thing about SVG images and CSS gradients/shadows is that they scale well on displays with very different pixel densities or zoom levels. I try to use them whenever I get the chance.My specialty is not web design but I am still interested and work closely on some related projects.
The way I see it though, is it best to always use svg icons and CSS gradients and shadows on pages people will often visit? It's better performance right, and anything else is just old habit or for really old compatibility?
What do you guys do about the scenario where a client (or coworker) of yours gets sick of looking at their redesign before it even goes live?
I have seen this a lot in the duration of my career, where you'll work up a redesign of site or application, and after x-amount of design review sessions, and x-amount of code reviews and project meetings - and sometimes even team members will get tired of their new design before it ever sees the light of day.
How do you "manage up" to internal or external clients, higher ups or PM's - to get them to see the forest through the trees. It kills me to see the initial WOW of a redesign loose its impact while the development team is in hardcore heads down code mode. It's so demotivating, and I have battled this kind of thing for a long time.
I saw it just yesterday. A new design that everyone freaking loved and suddenly yesterday a woman called a meeting to "Touch Base" and tried to reset the whole thing - where only a week ago she was raaaaaaaving about it. She's a particularly ignorant and uninformed client but weilds the Cudule of Xanthor at my company. Her comments were heard but not acted upon. It still took the wind out of my team's sails.
How do you guys in this field negotiate those treacherous waters?
Anyone using MVVM JS stuff like Knockout? I've been trying to get into learning it, but it feels like too much of a paradigm shift in coding. It changes so much about how you code and how your code ends up looking.
Knockout was the most intuitive for me. My JS code is still readable and easy to comprehend quickly. And I like that my HTML stays in my HTML -- instead of being put between script tags, like some other templating libraries do. Makes it easier to see what the page/app will look like before I've even bound it to any data.Anyone using MVVM JS stuff like Knockout? I've been trying to get into learning it, but it feels like too much of a paradigm shift in coding. It changes so much about how you code and how your code ends up looking.
Good luck, even if things don't work out there are many people looking for developers every day. Did they ask for your portfolio?
So if I wanted to build a website from scratch, I'd start with HTML, CSS, and PHP?
I'd think you'd start simply with HTML and CSS. Beyond that, it depends what sort of website you want to build.
What's PHP for, then? It was looking like basic functionality when I was looking at the different languages in the OP.
So speaking of responsive design... I'm having one hell of a time trying to get responsive images working in a test page I've thrown together. Tried "copying" several different guides, but nothing is happening for me in Chrome I'm doing something wrong but don't know what it is.
You mean HTML picture element? You'll need chrome canary.
PHP is backend stuff. HTML and CSS first and then Javascript after.
What's PHP for, then? It was looking like basic functionality when I was looking at the different languages in the OP.
Looking at the apparent differences between front end and back end, if I wanted to build a website from scratch, wouldn't I need to know the back end, too? I'm confused on why PHP or something like it isn't necessary.
You mean HTML picture element? You'll need chrome canary.
Looking at the apparent differences between front end and back end, if I wanted to build a website from scratch, wouldn't I need to know the back end, too? I'm confused on why PHP or something like it isn't necessary.
The long and short of it is: every website you build will require HTML and CSS. But not every website necessarily requires PHP. In other words, not every website requires a robust backend.
Looking at the apparent differences between front end and back end, if I wanted to build a website from scratch, wouldn't I need to know the back end, too? I'm confused on why PHP or something like it isn't necessary.
You really don't need to know PHP as there are hundreds of CMS out their you can use if you really are in need of a backend. It's always good to know, but not necessary to know in order to create a website.
Using a CMS isn't what I'd consider building a website from scratch.
CSS seems like its closer to design than programming....