Updated Portfolio

Portfolio - https://jdeliaportfolio.netlify.com/

A couple of months ago, I made a post asking for feedback on my portfolio/projects; I recently updated it, and wanted some feedback.

If you were an employer, what would be my chances of being hired (and what are the biggest red flags that I need to fix).

Thanks for the feedback!

It looks nice.

I think it’s better to use words as well as icons to describe your skills. It might be a recruiter looking at your portfolio who doesn’t know much about code and who doesn’t recognise the icons.

And maybe you should replace “interested in solving code” with “love to use code to solve problems” or something of that kind. It’s stronger and it shows more passion.

Good luck with the job-hunting!

1 Like

Makes sense.

You’re right about the ‘interested’ part… thank you.

1 Like

No, or at least, not as more than an intern. I remember your portfolio, and I’m not seeing a grand redesign. But more than that, I’m looking at what you produced and asking, “would I get my money’s worth out of his work?” Here’s my reasons I would not think so:

  • The color scheme needs to be better. You need something visually eye-catching on your portfolio to get hired for HTML/CSS, since you have NO JAVASCRIPT AT ALL ON your portfolio - not a crime, but all “under the fold” and all requiring clickthrough. You’ve given no consideration to contrast, let alone color theory. What about visually-impaired viewers? Lots of people with poor eyesight use computers.

  • on hover, the ring around your “cartoon headshot” causes everything else to readjust layout. Bad. Couldn’t you have wrapped that in a div to contain the effects?

  • your github is full of sporadic (non-daily/near-daily) commits whose message is usually “update.” That tells me that your commit message would be useless on the team, and a poor indicator of how you’d communicate on a team.

  • Knowing your prior projects, I looked at ABDN. The main article is “Anchors Away!” with an “Invalid Date” error prominently displayed. This is what you put out to sell yourself. If not even for yourself, how could I trust you to put your best foot forward for my clients? (Also, an aside: Your blog is full of grandiose prose that you’ve attributed to yourself. This makes the error even worse - you thought a lot about the (blog?) content, and didn’t think about the code, or QA. I see the same text under different headlines. If you didn’t write this, just use Lorem Ipsum. It’s there for a reason.) The navbar is not responsive correctly - it responds to horizontal resizes, but puts elements off-screen.

  • AGAIN: task crusher has no default login/demo account. I was able to make an account with fake info, but without explicitly telling people this was a project to practice authentication, no one will (I only did because I remembered). BTW - neither enter nor Ctrl+Enter activate the “Create” Button in the “create task” view despite it being colored as a default button. UX fail.

  • Save for Later: Okay, more interesting visually. Flat design, high contrast. Relevant “about” section with link to portfolio, but no github repository, so I can’t see the code for the one that looks best. The upload button is active when no file is selected, but styled “disabled” after a failed upload? Shouldn’t it be the other way? Also, why the heck do I have to take a picture of a tweet to upload it? Isn’t that just an image dropbox app, then? Wouldn’t searching tweets require some text awareness? You do say it’s an experiment, but without talking about your projects, what you learned, and your design decisions in the portfolio, all you’ve done is left me scratching my head.

  • the portfolio falls down flat on UX. I clicked the thumbnails twice, think I must have initiated a drag by accident, but no, it just wasn’t a link, despite enlarging on hover. Of the 3 possible candidates, the only link is the lowest on the panel (not the big picture, nor the first line with the project name either).

I know I’m coming off as harsh, but it’s because it’s what I would want to know. I see your code, and it’s not terrible (albeit completely sans documentation/commenting). You sometimes have a good eye for design. If it’s improving, I’d have no way of knowing, since your portfolio doesn’t provide any chronology. Your github is littered with more projects, so are these the best? I’d rather see 3 projects, well-polished: good UI, good UX, and motivated by a personal need - solving some pain point. I’d also like to see you use the skills you’re showing off in your projects on your actual portfolio. It doesn’t matter what your store sells if the storefront isn’t inviting. How do I contact you? Through github? Not likely. Twitter? Great - but that is a dead link. Email? Totally acceptable. But it’s the third link on the right. Where’s the big juicy high-contrast button saying “Contact Jesse”, located above the fold just begging to be pressed? Where’s the animation or parallax, or CSS virtuosity? Heck, where’s the javascript/React on your portfolio? Your projects show that you theoretically have the skills, but you seem unwilling to put them into action to sell yourself.


First, thanks for the detailed and thought out response!

  1. My Idea for the portfolio is for it to be really simple. I’d like more feedback from others on whether or not employers are judging portfolio complexity. I could implement those features, but it would feel out of place to put a bunch of random animations and distracting effects.

    Are you judging my ‘hire-ability’ based simply on my portfolio complexity, or projects? It seems like something ancillary for employers (from my experience), but I’m open for correction.

  2. Thanks for the onhover bug, I’ll have fix it.

  3. You’re right about the ‘Update’ messages. Truthfully, I usually just use ‘Update’ if its something simple like delete a word from text or some very basic and negligible change. I usually write more specific messages for more specific cases. I always feel bad when I do it, lol. I’ll have to stop doing that.

  4. Could you point me to the invalid date error, I’m not seeing it on my end (Screen capture). And the prose you’re reading is Lorem Ipsum, its been translated to english. I should maybe change that, since its a source of confusion. The navbar responsiveness is a bug that’s been bothering me, I do need fix it. It sometimes occurs, and other times doesn’t.

  5. The TaskCrusher project, does need a redesign, I keep putting it off; I will need to do something about it.

  6. SaveForLater is on private, but I can provide code samples. I am still messing around with it, and I don’t want to mistakenly expose certain things. That’s why there’s no repo.

    Good catch, on the button disabled until file is selected, I hadn’t considered that setup. You provide great suggestions to make it less error prone.

  7. The thumbnails weren’t meant to be clickable, I might change that, but refer to point #1. I do need to comment my code more, even if its a solo project. Those projects are for the most part in chronological order, and they are what I felt were most ‘eye-catching’, not necessarily the most complex.

    I’ve seen some great developers, with very basic and simple portfolios, so I’m curious how seriously an employer would judge someone’s portfolio because it wasn’t a kitchen sink of tech.

Again, I always appreciate your feedback, even though its sometimes hard to accept (intern??!!!, haha).


1 Like
  1. Simple != Clean. A clean design is fine. Animations were just what popped out of my head. OnHover type of animations are fine, but they can’t just be UI for the sake of UI. All UI must be in service of UX. If your panels enlarge on hover, they had better be clickable. I’m judging whether I would hire you based on decisions you made. No documentation ( i don’t mean: i++; //increment the index, I mean jsdoc-style or equivalent: `this are the inputs and outputs to this function, how it behaves on edge cases, what will cause error, a summary of important details about implementation and my decisions therein. If there is some complex logic, or it’s the first time I’m figuring something out that was complex for me, I write more, sometimes keeping the pseudocode (with modifications) as “subheading” for chunks of code, along with empty lines to help readability.

  2. No problem.

  3. This ties in with the hireability. Just like I don’t want the “increment index” coder, I don’t want: p=q+(v? x: z) guy either. (No ternary hate, I love it - I mean that variable names are part of documentation, as is a commit message. I’m not perfect on this by any stretch. I tend to commit when I need to transfer machines, or after I wake up from a code fugue and have banged out 3 things on the TODO list. But I always try to make my commits reflect that.

  4. :laughing: I read some Cicero in school, but not that. “Lorem” isn’t a word I knew, so I shut off that part of my brain. Based on your translation, there’s more than the words routinely used. I found out it was cut in the middle of a word “do/lorem”, and with the whole sentence, it makes sense. Thanks for the learning opportunity. But with that said, perhaps change it back to Latin, or change the author to Cicero. For your navbar, I’m on Firefox/Win10, and have tried it on 4k and <1080p screens. No dice.

  5. The taskcrusher is emblematic of the communication/not-selling-yourself problem that I see. It could be mostly fine (by changing the “default button” issue) as-is. But without explanation, which I had to ask for last time, it’s useless to show off anything. Again: What did you use, what did you learn, why did you decide big decisions the way you did. I would rather see half as many projects well-explained.

  6. I get the private, I get putting it on the portfolio. I can’t understand doing both at the same time.

  7. As for code, if a tech person is hiring you, they’re going to look. And what I’d look for is: does this person do work that others can use and maintain? If I don’t see any comments, it’s a quick no for me. Not because they didn’t comment, but because they didn’t bother to comment what they presented to the world. As for the great developers, their resumes probably did the talking for them. I’m guessing that you’re looking for that first dev job. If so, and were I you, I’d make sure that it was super-easy to get people to see the things I wanted them to see. That doesn’t mean bells and whistles, that means UX decisions that achieve that goal, and UI decisions that channel that UX. That tells me that if hired, I don’t have to teach you (everyone’s a gamble on how easily educable they are), I can just point out when the first draft doesn’t execute the mission of the web page.

What is the mission of your portfolio page?

1 Like
  1. I’ll have to fix the date, its a browser issue. Thanks for point that out, I was suspicious of it.

  2. Are you saying that I explain the project in the portfolio, or in the Repo README?

What is the mission of your portfolio page?

To present my skills.

You have three sentences. Not long ones. What do you tell someone about that project? I would put in the portfolio. The Readme is for technical and/or non-technical people telling them how to understand/use your project, license info. As you said, you want your portfolio to “present your skills.” Is coding the only skill? What about critical reasoning? The ability to learn? The ability to evaluate your own work and progress? Both technical and non-technical people want to know that. You can’t guarantee whether anyone will look at your portfolio page. You can’t guarantee what role/background that person will have. It’s up to you to make your page work for you. I would argue that you’re only seeing part of the elephant. Your portfolio isn’t to present your skills, it’s “to sell a potential employer on hiring Jesse Delia.” Design that instrument. The one which guides people to the “call to action” (Interested in hiring Jesse Delia ? <button>Contact Jesse Now</button>). Something that stands apart. The way I view a great portfolio is: it’s a landing page for getting you into the interview room - part of your sales funnel. Read this great article on Landing pages to understand what I mean by UI serving UX, and UX being oriented to accomplish the mission of that page. In this case, the page is both the vessel of that mission, and the message itself. Why is all your most important content “below the fold”?

Bring it to the people, don’t make them go hunt for it. All that negative space above the fold is bad design. If they aren’t on mobile, they want to see your projects right away. Maybe a very minimal animation that, after 750ms, moves your image over to the side and presents them a carousel of your projects with 2-3 short sentences on each? That both presents your projects and your web skills right away. Not a single user action was required beyond navigating to the page. Emblazon a big, highly-contrasting contact button under that pic of you on the side of the screen, or for mobile viewports, have it float at the bottom of the screen maybe.

1 Like

I’m gonna implement some of your suggestions.

Will post them when finished.


1 Like

I made some updates.

I don’t feel like a description of the project, on the card would go with the aesthetic of the site.

What action would you like a user of your site to take? Design your aesthetics around that.

1 Like

I like it a lot. Simple is better than complex and confusing (and boring).

Also, the “Hire me” button it´s so cool haha. I think I will copy you on that :rofl:

1 Like