Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site showing pretty much a subset of the info I can already see from your GitHub account, except the latter doesn't require JS to view. If I'm looking at someone's personal site, it should look personal --- not "I cloned someone els…
Personal Website for Programmers
101–110 of 111 posts
Re: Personal Website for Programmers
#102Earlier quoted context omitted.
motherfuckingwebsite has google analytics. kind of surprising imo.
Makes it noncompliant with GDPR too. Tho maybe one could argue the exemption for personal use here.
Re: Personal Website for Programmers
#103Earlier quoted context omitted.
IMHO the content matters way more than the form. And your website is empty, so I would focus on this instead of the rainbow text (which is just a bit too fast to be distracting).
I am going for a minimal look however and still working on projects to put on the site.
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.
Re: Personal Website for Programmers
#104Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site showing pretty much a subset of the info I can already see from your GitHub account, except the latter doesn't require JS to view. If I'm looking at someone's personal site, it should look personal --- not "I cloned someone els…
Re: Personal Website for Programmers
#105Earlier quoted context omitted.
Judgements like "I'd expect dev to write it themselves" come across as arbitrary. I think there's no shared context wherein interviewers / job-applicants have the same set of assumptions. 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…
> Judgements like "I'd expect dev to write it themselves" come across as arbitrary. 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?
Re: Personal Website for Programmers
#106Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site showing pretty much a subset of the info I can already see from your GitHub account, except the latter doesn't require JS to view. If I'm looking at someone's personal site, it should look personal --- not "I cloned someone els…
Re: Personal Website for Programmers
#107Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site showing pretty much a subset of the info I can already see from your GitHub account, except the latter doesn't require JS to view. If I'm looking at someone's personal site, it should look personal --- not "I cloned someone els…
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.
Re: Personal Website for Programmers
#108Earlier quoted context omitted.
Personally I place more weight on their professional experience / portfolio and don't feel that having a pretty or flashy site is a good predictor of a developer's ability, especially when most devs are using templates anyways. But yea, all else equal a nicer site is an advantage even if a minimal one at that, not going to disagree with you there.
While it's nice for someone to have a public portfolio of URLs they've worked on you can't really rely on that so much now. 15 years ago sure, everyone made websites so you just asked to see what site's the candidate had built. Over the past 10 years I've found it increasingly common that developers working with front end tech are building things they can't show off - SaaS, internal apps, etc. That's one of the reaso…
Re: Personal Website for Programmers
#109Earlier quoted context omitted.
I don't find it aggressive. It's honest, without any digressions or trying to be more than a list of mistakes and bad decisions that were made.
It's very opinionated, it offers no help or pointers about how to fix any of the problems, and it wasn't asked for.
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.
Re: Personal Website for Programmers
#110When I hover over some of the "links", my FF 67 doesn't tell me where the link points to. I don't really like clicking on links if I can't tell what they're doing. Too spooky for me.