Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I built the most over-engineered Deal With It emoji generator

emoji.build

Post reply on HN
Print view View original

81–90 of 153 posts

Re: Show HN: I built the most over-engineered Deal With It emoji generator

#85

Post by pc86 »

com2kid wrote: post #76
airstrike wrote: post #7

> Unfortunately, they were not impressed and ultimately did not offer me the job :( Sorry to hear that. No recruiting process is perfect. They often get it wrong, as they clearly did here!

I interviewed a developer once who was super junior on paper but had a side project of a fully featured desktop anime episode to watch/watched tracker with lots of library feature features. Hire. Interviewed another Dev who made arcade sticks as a side project. Hired. You can't teach passion. Hire all that passionate people you can. Tech stacks are irrelevant compared to the love of building things.

Also a great filter from the other side.

I was not hired once because I didn't have React experience, despite having years of both Vue and Angular and having led teams building non-trivial apps in both. IME focusing on such a minor detail like that means either a) you're going to be so pressured to get stuff out of the door they can't handle slightly lower productivity for a month while you learn the different syntax, and/or b) the person hiring you isn't technical enough to know this is a minor detail.

Either way, better off somewhere else :)

Re: Show HN: I built the most over-engineered Deal With It emoji generator

#90

Post by teqsun »

klimeryk wrote: post #25
teqsun wrote: post #19

That's fantastic stuff! Minor UX notes: - clicking the header doesn't navigate back to the "home" screen - singular page history (so the back button doesn't take you back to the previous page state) Combined it made it not intuitive for me how to "get rid" of the selection I'd created (I eventually figured it out, but the previous two points were what I intuitively tried first)

> clicking the header doesn't navigate back to the "home" screen - singular page history (so the back button doesn't take you back to the previous page state) Could you describe in more detail this? I'm not sure I agree that state changes should be pushed to browser history. In my experience this usually leads to confusing user experience. But that might be also just years of conditioning and I'm missing some best pr…

My natural instinct to return to the "default" view (as in, how the page looked the very first time before I interacted with anything) was to click the header text at the top (that says "deal with it"). Same as you click the "Hacker News" text at the top to return to the default home page view.

Just as something to be a quick "oops, didn't want to use that image, I want to go back to how the site is when I first visited it", and essentially wipe the state.

The history stuff is secondary, since that was my second instinct after trying to find and hit a "home" button, just from my personal UX perspective.

Post reply on HN