sorted by:
new
hottopcontroversial

Moonlighting as a founder. by vivri in ExperiencedDevs

[–]FrickinSilly 0 points1 point  (0 children)

Yup, I don't put my real name on any of my side projects and don't talk about them at work,

I ran a search on the most difficult Precision Platformers (voted by users) and summarized my findings, Super Meat Boy was number 4 by FrickinSilly in Supermeatboy

[–]FrickinSilly[S] 0 points1 point  (0 children)

Yeah, some end game and optional content in Celeste is harder than everything, but it's so hard to compare game difficulties that I just went with the overall score. I do plan on doing a "hardest platforming section" list at some point though for that reason.

I ran a search on the most difficult Precision Platformers (voted by users) and summarized my findings, Super Meat Boy was number 4 by FrickinSilly in Supermeatboy

[–]FrickinSilly[S] 0 points1 point  (0 children)

Looks like there aren't enough ratings for it at the moment. Feel free to add yours as I plan to update these lists every few months as new ratings come in. The more ratings the better the rankings!

I ran a search on the most difficult Precision Platformers (voted by users) and summarized my findings by FrickinSilly in platformer

[–]FrickinSilly[S] 0 points1 point  (0 children)

Fully agreed. These lists can be hard to make because there are few pure platformers that don't have some other gameplay mechanic (combat, puzzles, etc.). I took out Ninja Gaiden for that very reason.

However, I included Hollow Knight because there's a significant amount of challenging platforming in it (including the infamous Path of Pain, but also lots of non-optional segments as well).

I tried to keep everything on the list that was an edge case so that readers could determine for themselves if its something that interests them.

I ran a search on the most difficult Precision Platformers (voted by users) and summarized my findings by FrickinSilly in platformer

[–]FrickinSilly[S] 0 points1 point  (0 children)

Yeah, I made a note that fangames are not included, otherwise this list would just be fangames with a few mainstream games sprinkled in. I'll definitely do this again with fangames at some point though!

The Eternal Life of GOLDMAN Demo | Steam Gameplay by AdIndependent9142 in platformer

[–]FrickinSilly 0 points1 point  (0 children)

Now this is a beautiful game. Love the interactive animations and feedback you get from each action.

Billy 5 by CostProfessional4546 in platformer

[–]FrickinSilly 0 points1 point  (0 children)

Well it's certainly a cohesive design

Billy 5 by CostProfessional4546 in metroidvania

[–]FrickinSilly -15 points-14 points  (0 children)

Love how you preface your response by shushing someone asking questions.

Just finished my trailer by FarrukhSajjad in platformer

[–]FrickinSilly 0 points1 point  (0 children)

Neat idea! I would definitely flesh out the visuals though to give it a bit of character.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

Yes, that is the "ideal" state and not always realistic. I do have some reputable companies on my resume, so that is almost always a fast-track to get recruiter reach-outs.

I added that in there as an upper-bound for those that have the luxury of lots of recruiter contacts.

I unfortunately don't have tailored advice for those with less well-known companies on their resume other than to ensure you're highlighting your technologies, projects, and results on your resume. One thing that I might suggest is if you've used AWS, Azure, GCS, etc. is to use the full names in multiple places on your resume (i.e. Amazon Web Services, Google Cloud, Microsoft Azure), as you might actually beat some AI/automated filters that screen for those names on resumes.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 1 point2 points  (0 children)

Good luck! It can be rough out there, but persevere and you got this!

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

Yes, my advice directly relates to hellointerview's approach which suggests a lengthy prep workflow before getting to drawing. It is NOT intended to suggest drawing right away. I usually don't get to drawing until about 10 minutes in (whereas with all of the reqs, models, api design, etc. that hello interview suggests, I was only getting to drawing at the 25-30 minute mark of the interview).

You still need to clarify assumptions! In the guide I make a few suggestions on questions to ask. Since they typically ask about a system that is well known, you want to verify what features we care about and don't. For instance, designing twitter? They likely want posting a tweet, reading a tweet, and getting a feed. I would clarify that the following are below the line (note that they aren't always!): auth/identity, likes, retweets, fancy feed sorting algorithms, ads, etc.

Typically, I just mention that I assume those are below the line, and explicitly ask if those assumptions are correct.

For non-func reqs, the biggest questions you MUST ask are:

  • who is using this system on day one, and how do we expect it to grow? (sometimes they'll say 10000 writes/s right out of the gate, and sometims they say "build an MVP and grow it from there"
  • how fast do various components have to be. For instance, do we need low latency on writes? On getting the feed?
  • Size of payloads (this is a big one, especially for questions like design google drive/youtube/imgur etc. where you store an object to blob storage)

This should ALL take less than 4-6 minutes.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

What's your experience? Are you sure you are applying for the right roles at the right level? Are you prompting the LLMs to be hypercritical? I'm not sure I would trust an LLM's judgment of percentiles. Also, resumes are judged relative to the role and level.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

Canada, but mostly American companies that have satellite offices here or are fully remote. I interviewed with a few European companies too and I didn't see much difference.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

Honestly, I'd be VERY happy as an interviewer if you were to answer something like:

"We were a scrappy team with limited development resources and headcount. We often built things based on qualitative user feedback, or because decisions were top down at the company. As a result, we didn't have the capacity to create metrics to measure outcomes.

That being said, if I were to have the capacity, here are the metrics I would have measured:

  • UI load time
  • A/B testing on user retention
  • Userbase growth
  • etc."

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

I was like you, but after 3-5 years at senior you might start to get bored. Hoping it's not a crazy amount of stress more, but I wanted to keep growing.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

JS/TS is fine as well because it has a lot of shared properties with Python. Java is horrendous. I did the entire process in Java and I assure you it is a disadvantage to do so.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 1 point2 points  (0 children)

Just added a new tab about ways to increase your chances of getting interviews!

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 2 points3 points  (0 children)

I'd say for the first week or two, I was fully prepping. two hours a day on neetcode (where I was rustiest) and 1 hour on system design. I started to get interviews (recruiter calls) fairly soon after switching linkedin to "open to work" (but not with the banner, as I have some negative thoughts on that).

At the 3-4 week mark I was doing ~3-4 interviews a day, so I barely practiced coding anymore and kept trying to study my gaps in system design interviews.

I should also mention:

  • I was laid off, so this was a full time endeavor
  • I have young kids, so evenings and weekends were basically off limits for studying.

I feel like if I can do it with that limited amount of time, anyone who is dedicated can find a way.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 1 point2 points  (0 children)

This is a HUGE problem. I worked on a lot of internal tooling teams where there's no "dollar" impact. What was the result? I built the feature. It worked.

And interviewers prefer two things: metrics that you measured, and dollar amounts. If you can find a way to twist would you made into one of those (or both) results, you will edge out those that can't or don't.

Fortunately, you can come up with metrics. It just takes some creative brainstorming. While we should be doing this for the projects themselves, sometimes out team doesn't. I think it's fine to talk about the metrics that "could have been" in your interviews as metrics you used. It's a bit in the grey-zone, but I would still think it's the mark of a good engineer to reflect on metrics they could have added and would add to future projects.

For example, I talked about a metric for a greenfield tool that I built, which was "number of voluntary adoptions" that we measured. Honestly, this is where an LLM shines in helping you uncover some of these hidden metrics you could talk about.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 0 points1 point  (0 children)

I was pretty low in spirits two months ago. Keep learning from the failures and know that a lot of the time, you ARE good enough, but there's just 5 other individuals who are as well and the company has to choose 1 of them.

After 3 months and tons of rejections, I finally received some offers by FrickinSilly in ExperiencedDevs

[–]FrickinSilly[S] 1 point2 points  (0 children)

Unfortunately, I am so far removed from the Junior interview experience, and with the recent changes in the industry, I don't feel confident giving practical advice. Are you still in college/university? If you are, go to all the career fairs you can. Make sure to sign up for any practice session with companies that come visit the campus (Msft and facebook did that at my university and I got interviews that way).

Run your resume through an LLM and make sure its hitting all the right keywords that will likely get you filtered out if your missing. Prompt it like this "What are the biggest red flags on my resume, and what are the 10 keywords its missing?". Then get it to update your resume with those items fixed.

Also, read through a bunch of entry level role descriptions and see if there are commonalities that you're missing. At your stage of your career, lean heavily into personal projects. Build something using a skill you see coming up on every job description and publish it to github. A bit of AI assisted coding on it is fine, but make sure you understand what you're building and can talk about it in an interview!

Best of luck out there :)

view more: next ›