Hacker Newsnew | past | comments | ask | show | jobs | submit | mnembrini's commentslogin

We were hiring for senior devs java/spring boot so I coded a tiny "Todo app" rest API, basically a single crud controller, and filled the code with many mistakes. Some obvious, some less obvious. Missing authentication, no tests, logging with System.out etc.. then we ask the candidate to review the code (we provide a laptop with a few IDEs but no AI tools). When they point out errors, I get them to explain why they are errors by playing the junior engineer to see how they explain technical issues to someone that might not have the same understanding I am not looking for them to find all issues but if they can't find at least some it's a red flag. It takes about 20-25 minutes and gives really good insights. The other 30 minutes we asked some questions about past projects and some technical questions

So far it provided good signals


Even before AI, I liked to have candidates do a code review on a pull request.

I guess that's even more important now that AI-generated code needs to be reviewed.


Love this. +1 to the explaining part


In Intellij if you open a PR it will highlight lines that have changed in the PR differently (even from multiple commits) and you can click on the colored border to see the version of the code on the main branch


2 yes, although if you are splitting only one regular character the implementation doesn't use a Regen internally

3 is not an issue anymore since java 22 https://blog.jetbrains.com/idea/2024/02/constructor-makeover...


About workflow recovery: if I'm running multiple instance of my app that uses DBOS and they all crash, how do you divide the work of retrying pending workflows?


Each workflow is tagged by the executor ID that runs it. You can command each new executor to handle a subset of the pending workflows. This is done automatically on DBOS Cloud. Here's the self-hosting guide: https://docs.dbos.dev/typescript/tutorials/development/self-...


Interesting design but a bit hard to use on mobile :) will have to check it out later


I found it painful because it's just some javascript bash masquerade costume. Here's the content:

https://9ol.es/reef

Just do this if that's still too painful

    $ nodejs -e "Object.entries($(curl 9ol.es/reef)).map(([md,{content}]) => console.log(md, content));"
These people seem to have a very weird sense of humor ... sounds entertaining.


To be fair if the fixes are trivial they shouldn't need any extra context from a ticket to understand


The direct links are giving a 404 for me


This seems exactly what you are looking for https://www.causal.app/


After looking through their landing page, I totally agree, this looks perfect. Thank you!



Very cool, hadn't heard about that tool. Do you think that's more powerful than simple shell scripts around HTTPie/xh/curlie?


Certainly worth a try but one might start wondering whether this is so much better than classical bash + curl


There are some example links in this post about HATEOAS

https://engineering.3ap.ch/post/using-hateoas-with-rest/

I think the main distinction according to the original paper is if you are doing just HTTP CRUD ( not REST) or also HATEOAS


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: