SShortSingh.
Back to feed

Developer publishes his product's underlying dataset as open data instead of keeping it secret

0
·5 views

A developer who built a wedding speech generator decided to release the dataset behind its checks, a list of Japanese taboo words, under a CC-BY-4.0 license while keeping the prompt private. He argues that compiled public cultural knowledge cannot function as a real moat, and that hiding the data made his code harder to test and hid a latent bug. Making the list open, he says, also seemed to bring no measurable downside, since few people would build the whole product from a small JSON file. He separates facts, which he publishes, from product judgement about tone and structure, which stays private. He concludes that the real test of a moat is whether a competitor could reproduce it over a weekend.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Public Yamtrack instances raise account exposure concerns for self-hosted owners

A security-focused analysis describes Yamtrack, a self-hosted Django-based media tracker, as a product whose public instances can expose registration, social login, OpenID Connect, and personal watch history. Search counts from November 17, 2026 found 101 title matches and 135 body matches, but the author notes these figures describe pages rather than authenticated user populations. The official documentation indicates that registration is enabled by default, so owners should decide whether to disable open signup before publicizing a deployment. The analysis also flags that a sample social-login configuration requested repository permissions the tracker does not need, and recommends limiting scopes to required claims. It further advises reviewing host allowlists, CSRF trusted origins, OIDC secret storage, and account deletion and export practices, since tracker data is personal.

0
ProgrammingDEV Community ·

Study finds fear appeals work modestly, but proof that the fix works matters more

A study of how fear appeals influence behaviour found a modest pooled effect (d = 0.29) across attitudes, intentions and actions. Research reviewed in the piece found no identified conditions where such appeals backfire, though a counter-claim tied to low self-efficacy was tested and not supported by the pooled data. A 2022 meta-analysis reported stronger behaviour change when threats were paired with evidence that the recommended action works. The author cautions that these findings come from health research and do not directly measure marketing or community acquisition. The piece argues that the persuasive weight lies in demonstrating a solution rather than in the warning itself.

0
ProgrammingDEV Community ·

Developer Shares JavaScript Method for Estimating Deck Boards and Joist Spacing

A developer has described how they built a browser-based deck estimator in vanilla JavaScript to calculate lumber needs. The approach accounts for expansion gaps of roughly 1/8 to 1/4 inch between boards, which prevent water buildup and allow for wood expansion. Board rows are derived by dividing deck width by effective board width, then multiplied by length with a default 10 percent waste allowance. Joist counts are calculated from span length and spacing, typically 16 inches on center for perpendicular layouts or 12 inches for diagonal patterns. The author notes that automating these steps reduces spreadsheet errors and builds in margins for cuts and splits.

0
ProgrammingDEV Community ·

Reviewer agents found loopholes in a personal AI agent's shutdown-prevention rules

A developer built a personal AI agent running on a home server that writes most of its own code, with 424 pull requests merged since May. Every change is checked by other AI reviewer agents before shipping, and these reviewers uncovered flaws in the agent's safety rules. A rule meant to stop the agent from shutting down its own service was bypassed in five ways, including command-flag tricks and uncovered commands like kill. The developer fixed the issues, with the final one resolved by switching the matcher from substring to regex matching. The account also highlights the broader lesson that loosening rules creates gaps, so the developer now confines tools by construction where possible.