Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To be fair on candidates, CLI programs create technical debt the moment they're written.

A good answer that strikes a balance between size of data, latency and frequency requirements is a candidate who is able to show that they can choose the right tool that the next person will be comfortable with.



True on the premise, yep, though I'm not sure how using CLI programs like LEGO blocks creates a tech debt?


I remember replacing a CLI program built like Lego blocks. It was 90-100 LEGO blocks, written over the course of decades, in: Cobol; Fortran; C; Java; Bash; and Perl, and the Legos "connected" with environmental variables. Nobody wanted to touch it lest they break it. Sometimes it's possible to do things too smartly. Apache Spark runs locally (and via CLI).


No no, I didn't mean that at all. I meant a script using well-known CLI programs.

Obviously organically grown Frankenstein programs are a huge liability, I think every reasonable techie agrees on that.


Well your little CLI-query is suddenly in production and then... it easily escalates.


I already said I never managed a data lake and simply got stuff when it was needed but if you need to criticize then by all means, go wild.


True but it's typically less debt than anything involving a gui, pricetag, or separate server.


Configuring debugged, optimized software, with a shell script is orders of magnitude cheaper than developing novel software.




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

Search: