fs_software

2 miesiące temudiscuss

[dead]

5 miesięcy temudiscuss

I've been building a platform for code review-based interviews.

Was going to post "Show HN" but the guidelines say blog posts / sign up pages should be a regular post. Since I'm running a pilot (just trying to learn and iterate) the platform is invite only. So I guess this is both a blog post and a sign up page for folks interested in trying it out.

Just me working on this on nights and weekends for now. Open to feedback!

fs_software

6 miesięcy temudiscuss

> Any misfortune ‘that lies outside the sphere of choice’ should be considered an opportunity to strengthen our resolve, not an excuse to weaken it.

This is an interesting perspective that I've practiced but haven't explicitly considered before.

fs_software

6 miesięcy temudiscuss

I'm working on moving beyond the LeetCode interview for software developers.

Most software engineering interviews are a “signal crisis”. They measure recall, not real-world engineering.

I'm working on moving the evaluation from “writing code under pressure” to technical judgment via structured code review.

https://entrevue.app

fs_software

7 miesięcy temudiscuss

I want to learn how to be bored again.

I also want to learn how to ask better questions.

fs_software

7 miesięcy temudiscuss

I wonder how teens who already use social media will be affected compared with kids who won’t have accounts until age 16.

fs_software

7 miesięcy temudiscuss

https://www.w3.org/WAI/ARIA/apg/

fs_software

7 miesięcy temudiscuss

If you know your team's velocity, this methodology has worked well for me in the past:

- ask enough questions about the scope of work to do a prototype

- build a prototype to identify constraints / complexity

- ask followup questions

- break the body of work down into a list of tickets (spike/discovery tickets included)

- use the PERT formula to estimate the total number of story points for the body of work

- take the total estimated points and divide by your team velocity for a duration of time (e.g. 100 total points / 40 points per 2 weeks = 2.5 weeks)

fs_software

9 miesięcy temudiscuss

In my opinion, pair programming and system design discussions are important in the interview process. Those sessions enable hiring teams to assess how the candidate leverages AI tools to build features, debugs, and thinks about solving system-level problems.

However, I'm convinced the future of technical screening for software developers is to do so with code reviews rather than evaluating solely on code production.

The ability to review code is crucial in our industry. You'll be reviewing code often regardless of who (or what) generated it.

fs_software

Submissions

Show HN: One-click code review interview

OpenClaw is a security nightmare dressed up as a daydream

How to Not Get Hacked Through File Uploads

My Solution to LeetCode Interviews

Competence as Tragedy

The teammate who asks too many questions is the one you need

Spotify Shuffle: Making Random Feel More Human

Code is cheap now, but software isn't

Why ID Format Matters More Than ID Generation (Lessons from Production)

Ivan Sutherland Sketchpad Demo 1963 [video]

Where have all the mentors gone?

[untitled]

comments