Terms of Use

What using Joshfonseca means

Reading, searching or linking to joshfonseca.com means you accept the rules on this page for the way you use the blog’s articles on software engineering, language models and mobile apps. Questions can go to [email protected].

Technical information, not professional advice

Posts are general technical information and personal opinion. They are not legal, security, compliance or engineering sign-off for your project. Code samples are written to illustrate an idea and may omit error handling, hardening or licence checks. Test everything in a safe environment and keep backups before running it against real data or production systems. Language models can produce confident but wrong answers, so check any output against documentation before relying on it. App store rules, platform versions and model behaviour change often, so a post may be out of date by the time you read it.

Who owns the content

The written posts, page design and original diagrams on Joshfonseca remain the operator’s property unless credited to someone else. You may read them, quote a short passage with a clear credit and share links. Code snippets are offered for you to learn from and adapt in your own work unless a post states other terms. Copying full posts, republishing them or using them for commercial purposes needs written permission.

Using the site properly

Do not probe the blog for weaknesses without permission, flood it with automated requests, scrape it at a rate that harms other readers, upload malicious code or use it to send spam. Using the blog to break a software licence or someone else’s terms of service is also off limits. Access may be limited if that is what it takes to keep the blog stable and its readers safe.

Sending us things

When you send a correction, bug report or topic idea, you confirm that you are allowed to share it, including any code. By sending it you let the operator read it and learn from it when planning future posts, without any obligation to answer or print it.

Ads, affiliate links and outside sites

The blog may show advertising and may contain affiliate links to things a developer might need, such as code editors, hosting plans, books, courses, model APIs or app development tools. These can earn the operator a commission at no extra cost to you, and they do not shape what a post concludes. The sites behind those links are outside our control: their prices, features, data practices and availability are their own business, and we are not responsible for what they publish or sell.

Warranties and liability

The blog is provided as is and as available. As far as the law permits, the operator does not promise that posts will be accurate, complete, current or free of interruption, and is not liable for loss, including lost data or downtime in your own software, arising from use of the site or reliance on its articles. Statutory consumer rights that no contract can take away stay intact, as does any liability the law does not allow to be excluded.

Changes and severability

These terms can be updated whenever the blog’s features or content change, and the new wording takes effect when it appears on this page. If a part is found unenforceable, the remainder stays in effect.

Contact

For anything about these terms, email [email protected].