21–26 of 26 posts
This is somewhat more difficult to program, but definitely the more efficient way of doing it.
Here is a recipe for a successful shitpost on hacker news: 1. Write a blog post about your experience with X. Your description shall not be complete nor correct. 2. Wrap it around with a thesis on a random topic, which is semi-related to your experience, and which is by no means proven by your description. 3. ?? 4. profit!
I slightly prefer the 'worse' solution for the second problem, at least in terms of substance, not necessarily style. The trick the 'improved' version does with uniq seems a little hacky to me, somehow. The first problem has a clear improvement. I just checked ruby doc and 'reduce' and 'inject' seem to be synonyms, as far as I can tell.
I've never done Ruby, but what I don't like about that second solution is how much logic it puts into formatting directives in a string literal: > "#{x}#{input.split('').count(x)}" Just because Ruby apparently allows you to do that much in a formatting directive doesn't mean you should.
1) The popup at the bottom saying "Sign Up Now to Receive a Free Developer Career Cheat Sheet plus a Free Course to Help Get that First Coding Job! Let's make that breakthrough together".
and
2) Zero to Launch is on his calendar.
The author of this post has paid thousands of dollars to learn how to market and sell a course on how to get a programming job.
William has looked back after 2 years learning. He's blown away and is showing those that are slogging it out, 2 years away from that point.
The author will learn that, actually, you can do this every 1 - 2 years and still get blown away. Even more shocking is looking at that newbie code at 4 years in.
Fact is there is clear improvement. He's on the right trajectory. He's just in the stage where you feel unstoppable and perhaps hasn't yet been humbled by a few bad projects.
He should be applauded and welcomed. He has put in the time, improved significantly in 2 years and is on the path away from mediocrity.
In the end, many programmers stop learning after Uni or at least outside of formal training. We are, here, part of a pack that practices continuous skill improvement out of love for our craft and it looks like we have a new member.
To the author, keep at it mate - great progress!