Personal Website for Programmers
github.com
github.com
If I'm looking at someone's personal site, it should look personal --- not "I cloned someone else's I found on GitHub and changed the names and details to mine."
And my own website is basically the Pelican generator default with a different color selected. Far more damning is the placid update schedule. Try not to put dated content on your front page if you're putting a website in front of manager's faces.
> If I'm looking at someone's personal site, it should look personal --- not "I cloned someone else's I found on GitHub
To me that seems petty and I feel you'll end up isolating a good portion of the talent pool. Anecdotally, I can only recall a handful of personal sites that appeared to be truly personal (by your definition) and not all may have been.
For whatever reason this reminds me of: https://www.reddit.com/r/Jokes/comments/67e0hl/whenever_i_ge...
Especially since "I'd expect a dev to not rewrite everything themselves, and leverage what's already available" is just as reasonable.
There's not exactly a specific "right answer" about whether you need a personal website, what it should look like, or how it should be written.
I feel like this depends on the type of dev. If you write C code for microcontrollers then who cares, but if you do web dev then using a generic template not authored by you seems like a bad sign, no?
But part of why I consider it arbitrary is it's easy to come up with contradictory criteria, each of which might make sense. (-1 for using latest technology on a personal website, since it shows they buy into hype/resume-driven-development. -1 for not using the latest technology, since it shows they don't know the tools of the trade). I think this bleeds from trying to judge someone's professional capabilities as part of a team, from something produced in their spare time.
Portfolio sites are used to showcase the developer's work. If the developer's work sucks then it doesn't matter if it was done just for fun or as an extension of his CV.
A personal website is not a software development project. It is not something to use to evaluate a developers technical skills. When you have a real project on the line, then you will see the real skills come out.
For a personal website, I’d expect a developer to give a fuck enough to develop something on his own.
You get zero signal from the fact that someone decided to use a default template.
If I want just someone to write simple stuff I have whole of India to choose from and they are way cheaper than you. If I'm looking for a web dev from western market I'm looking for highly talented people and if you can not showcase that talent then what good are you for?
From my experience thous who have no personal projects of passion that involve programming to any extend usually aren't that good at their job. That obviously doesn't mean that you can not or shouldn't have other hobbies that are not computer related, but again if it comes down to two candidates and one has proof of work in their github profile then the choice isn't that hard to make.
Hell, I can’t even find time to pick a template and design the look and feel or choose what content to put on my own website.
They didn't say they reject candidates based on this, simply that it doesn't make a 'good impression'. Weather you agree or not, it shouldn't be hard to understand why someone would think that.
Why? if it is petty, why not slam it? it is a single opinion - do we need at least N people to share it before we can slam it?
>They didn't say they reject candidates based on this, simply that it doesn't make a 'good impression'. Weather you agree or not, it shouldn't be hard to understand why someone would think that.
Unless you make 'Good Impression' on recruiter you aren't gonna pass forward in the process, so it is indeed equivalent with rejection.
My personal website is a wordpress blog we've I've dumped some photos of the hardware stuff I do as a hobby.
I'm curious to hear how this factors into your views on what to look for when hiring people?
(I say this as someone who used to overengineer my own personal websites with the hottest tech stack of the week, but am now in the process of throwing it all away for a simple WordPress site.)
A good website that demonstrates some ability to write frontend code well is a shortcut to demonstrating that you're good at what I want to employ you to do. It's a showcase of your skills, just as a graphic designer would have a Dribbble portfolio or a backend dev would have a few repos on Github. I'm not suggesting you can't get hired without a nice site, but if I get your resume you're much more likely to get a call for an interview if you do.
No, the equivalent here would be to expect back-end devs to build their own blog applications. What a waste of time. I did that when I was younger and it was only a distraction from actually writing and building things that mattered.
No one is forcing you to do any of this stuff. If you can find a job you like without doing it then that's awesome, but plenty of people can't. I'm suggesting a way that people can avoid being filtered out based on their resume because, whether you like it or not, wanting a candidate to demonstrate that they can code reasonably well before the interview stage is quite common.
I think people get a bit too hung up on the way FAANG-size corporations do hiring, with code tests, full time hiring managers, etc. That's only a fraction of the software industry, and if you're applying to somewhere smaller having a public portfolio is useful.
That you should build something if you don't have anything to show off at all is a completely different point -- and that doesn't seem to be your point when I reread your previous comment? At which point, I'd recommend building something more interesting than a blog unless you're a beginner, and I'd avoid mixing your writing with your attempt to build your first demo project. But this thread isn't about beginner advice.
However, outside of junior level positions, I don't think there's much you can glean from whether somebody has done trivial side projects or not. Obviously an ambitious side project is worth a lot, but the bar for building one is really high and there are so many great devs who can't reasonably make the time outside of work to do that.
In the beginning I felt like I would need a portfolio and all that, so this minimal thing was supposed to be super temporary. But it turned out that actually talking to customers about their needs and what I could do for them was a quite reliable way to land projects. If anyone asks to see prior projects I send them a selected list that seems appropriate in that context.
Having a WordPress blog is generic enough that it alone won't really sway any opinion, but the content you have on it can. The same goes for a GitHub account.
It's really the "I copied someone else's work and made it look like it's mine" type of thing that gives a bad impression.
source: I've been a hiring manager for large companies (and a few startups) in SF for the last 8 years.
Using templates can be free, or low cost, compared to writing everything from scratch yourself. There are other things I'd rather be doing in my spare time.
Doesn't it friend in what you're hiring for? I'm not sure a backend developer should be expected to craft together a great website.
And even if you're hiring for the front end, I've found that being proficient at a11y or building React apps or designing elegant CSS doesn't really predict your ability to execute on a professional profile site, which is essentially a marketing tool.
Disclaimer: I'm working on a tool for developers [1] in this vein.
"Is your website too bland? Did you just git clone someone else's repository? Concerned about job prospects? Do not fret!"
That only makes sense if you're hiring a frontend developer. Many people who are excellent programmers hate frontend development, and will happily use a theme or clone a repo if they can avoid frontend work that way.
That might be different if you hire web developers of course.
It's amazing how many people forget that there are gainfully employed programmers who've never touched a line of JavaScript.
We need websites too.
I think the functional requirements in this case are to impress someone who doesn't code, an HR person, etc. Because a qualified programmer manager shouldn't be particularly impressed with any personal homepage put together in a reasonable amount of time for the sole purpose of impressing a hiring manager.
There's places where it's worth it to "think outside the box" and then there are places that -- well, there's a reason we have boxes, because they work well for what they're designed to do.
From a graphical point of view, it looks a little off to me (I'm not a designer, so take with a grain of salt). The whole website is flat while the boxes have these little shadows. Too many things are centered: the menu on the left, the boxes on the right. The headers on the right side are too close to the left-hand menu.
Also I can't see where the links are pointing by hovering on them.
This thinking can be dangerous. Aesthetically pleasing != good design, too often it can be the opposite. You definitely need to understand the "psychological effects" your page or app has on its users. First, you have to put yourself in their mind, then can you start building, then go back and iterate.
I know this may be a hobby project without much budget, so find a designer friend and bring them on board. It's very difficult to do this in a vacuum.
Honestly if I came across this site in the wild I'd quickly pass to something else.
Is over complicating simple web pages the impression you want to send?
Web Designers can show the full range of skills by designing their website well.
Web Developers can't exactly cram all their elegantly designed components into one website.
Other than that, I think this is nice, clean and attractive. Devs aren't all designers and shouldn't be expected to be.
Most people don't benefit very much from having prettily-designed websites.
- Do I want the site to demonstrate the areas of coding I most enjoy (eg HTML5 canvas)? Or should I use it as a glossy form of CV which I can use to impress potential clients?
- Do I want it to act as a simplistic (single-page) calling card? Or should I be looking to use it more as an interactive hub aiming to do stuff like gather contacts, generate discussion on blog posts (which I could submit/share on HN, LinkedIn, Twitter) etc, etc.
- What tech should I be choosing to demo to visitors? If I go for a React front end is that going to put off potential clients with Vue projects I could work on? If I want to attract bread-and-butter work should I be looking to demo a Wordpress site with a home-built theme and plugins? Do I want to show off my skills with 3rd Party APIs?
At the moment I'm thinking of doing a minimalistic HTML site hosted in an AWS S3 bucket, with a picture of my cat above a big CTA button saying "Hire my human!" and a couple of links to my GitHub and LinkedIn accounts. At least it'll be easy to maintain and easy to replace once I'm clearer on the areas of work I want to focus on.
I’m going for a very minimalistic look and it’s still a work in progress, but I’m aiming to keep load times fast, minimal JS, etc.
Features I’m thinking of adding - a links page showcasing interesting links on the internet
Also checkout my 404 page :)
Well, it was kind of "public" to begin with, so you have to expect that people will tell you what they think about it. I don't see anything wrong in that.
Minimalism is about limiting yourself to the minimum necessary to communicate a message or make something usable, in the case of a website the minimum is the raw content. That means that visually you would only have the actual content, without distractions. What you did is instead to remove it, which results in an almost empty page that isn’t interesting to visit.
Overall, no, this is not impressive. This should be an intro page, I kept scrolling as I thought it was one of those fullpage.js kinda deals.
Also, think about whether your desire for information on visitors really justifies adding yet another data point to Google's dataset.