News for hackers. Stuff that matters.

jerojasro

Re:Tinc Is Not Catan on Wednesday February 09, 2022 @02:20PM (#30277131)
Let's assume that this project merely clones the game mechanics and uses scans of its artwork, and all it does is providing a software version of the game, available at no cost.

With those assumptions in mind, would it be OK from a legal/copyright POV to release such an adaptation to the general public?

Re:Generating a Java program with 90% less code on Wednesday December 04, 2019 @02:01PM (#21705700)
I could not find any link to github/download/trials... any ideas of how can I try this language? or is this just vaporware?
Re:Ask HN: Successful one-person online businesses? on Wednesday October 23, 2019 @04:31PM (#21338667)
how come nobody has mentioned pinboard.in ?
Re:Faces of Open Source on Tuesday October 22, 2019 @02:42PM (#21327162)
Missing Theo de Raadt as well.
Re:Elm 0.19.1 on Monday October 21, 2019 @12:50PM (#21314414)
Thanks for mentioning this and calling him out.
No, he doesn't. Any of those alternatives you mention (apprenticeship, etc.) require someone senior to you overseeing your tasks/progress. That someone can be a colleague, boss, CS teacher, etc. It's up to the entity overseeing your development (be it a school, or a company) to provide such expertise.

Once again, it's OK that you (person, programmer) don't know that. But as a company, there should be a strong guarantee that you (company) have the knowledge to build a good product. It's fine for a company to have some people who don't know this stuff, but not to not have anyone capable (and in a position that allows them to) notice these kind of mistakes.

This indeed should not be news. It's OK for you as a developer (even a professional one) to not know about this. You can learn it from your colleagues, debugging poor performance situations like this, etc.

But it's not OK for a company to offer a service built in such a naive way (naive from a comp-sci point of view). To me this kind of mistakes are a symptom of having a poor CTO, poor hiring/dev practices, etc.