Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
TomOwens
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
TomOwens
1mo ago
That depends. People who are around developers, often yes. Whenever someone doesn't get it, it's easy enough to explain in one sentence: Technical debt is the result of decisions that we've made, willingly or unwillingly, or
2.
▲
by
TomOwens
1mo ago
I don't think that "mess" is a good synonym for tech debt. Martin Fowler wrote about the technical debt quadrants, and "mess" seems to cover 1/2 to 3/4 of the quadrants. I don't think it accurately de
3.
▲
by
TomOwens
2mo ago
And what happens when the agent modifies or skips tests or finds other ways to circumvent the constraints? There are already examples of agents trying anything they can to achieve the objective. The code is the one source of truth for the s
4.
▲
by
TomOwens
2mo ago
Dave Farley's book is really good, and I'd highly recommend it. However, I do have an issue with his focus on applying science in the definition, even though it doesn't come across in his final conclusions. In the history of
5.
▲
by
TomOwens
3mo ago
Having a bottleneck with AI-generated code is probably a good thing. Consider before AI. In cases where code was written by a trusted human, you had confidence that they were doing the right stuff - the people understood the context and req
6.
▲
by
TomOwens
3mo ago
In practice, the frameworks don't work out of the box. Take Scrum, for example. The framework described today has had all the original technical practices used by the first Scrum Teams stripped out, with no new technical practices adde
7.
▲
by
TomOwens
3mo ago
A better title would be "Dark Agile is a scourge on the planet". There are plenty of people who've written about this, but Ron Jeffries' posts "Dark Scrum" ( https://ronjeffries.com/articles/
8.
▲
by
TomOwens
4mo ago
I graduated from a software engineering program accredited by ABET as engineering, rather than as a computing program, which would include CS, data science, information systems, and IT. Even with that, I didn't have much, if any, cours
9.
▲
by
TomOwens
6mo ago
The AGPLv3 doesn't protect against cleanroom engineering. The full passage from Clause 13 is: "...if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer ne
10.
▲
by
TomOwens
8mo ago
> You absolutely can; the model is quite capable of reproducing works it was trained on, if not perfectly then at least close enough to infringe copyright. The only thing stopping it from doing so is filters put in place by services to a
11.
▲
by
TomOwens
8mo ago
Point 2 misses the distinction between AI models and their outputs. Let's assume for a moment that training AI (or, in other words, creating an AI model) is not fair use. That means that all of the license restrictions must be adhered
12.
▲
by
TomOwens
9mo ago
The premise of this whole post is incorrect. If an organization is building an AI product or offering an AI service, then a SOC 2 report, or at least a SOC 2 Type 2 report, should answer these questions. "What happens if someone tries
13.
▲
by
TomOwens
2y ago
I'm looking through what I have access to quickly. I started with the CSA's Cloud Controls Matrix, just because they trace to a bunch of other standards. They have a control - IAM-07 - that is to "de-provision or respectively
14.
▲
by
TomOwens
3y ago
If the copyrighted code was uploaded to GitHub by the owner, there's no problem with this. When you upload code to GitHub, one of the rights that you grant to GitHub is the right to use your content for "improving the Service over
15.
▲
by
TomOwens
5y ago
Most of the comments on that app as well as here are probably wrong. I'd suspect that everyone who had the app "installed without their permission" opted into the Android COVID-19 Exposure Notification program. This was deplo
16.
▲
by
TomOwens
5y ago
I think this is why the PDF is actually the "Guide to the Software Engineering Body of Knowledge". It's not a representation of the complete body of knowledge itself, but extracting key concepts and terms and provides pointer
17.
▲
by
TomOwens
5y ago
I wonder if the people involved in approving and conducting this research are aware of the ACM's Code of Ethics. I can see pretty clear links to at least two or three of the code's ethical principles. This seems to be a pretty ser
18.
▲
by
TomOwens
5y ago
Yeah. That's a better way of putting it. The author didn't opt to change the license. He corrected a licensing error. I do agree that making the downstream users aware is important, I just don't agree that immediately yanking
19.
▲
by
TomOwens
5y ago
Vendoring is a good first step, too. As long as you have a local copy of all the dependencies, you're better off than needing to go pull them from the Internet every time you want them and risk having them gone. Potentially worse is ha
20.
▲
by
TomOwens
5y ago
This just bit me. The first thing that I noticed was that some people are not understanding the GPL. It's far more impactful to Rails than the vast majority of web applications built using Rails. The use of GPL'd files means that