Suggestions
Stuart π¨βπ¦° Langridge
Owner at Kryogenix Consulting
Stuart Langridge is a freelance software engineer and the owner of Kryogenix Consulting Ltd.2 With a diverse background in technology and digital marketing, he has accumulated extensive experience in various roles throughout his career.
Professional Experience
Stuart's professional journey includes several notable positions:
- Owner of Kryogenix Consulting Ltd: As a freelance software engineer, Stuart currently runs his own consulting company.2
- Strategic Architect: He previously worked as a Strategic Architect for Ubuntu One.2
- Web Developer and Information Architect: Stuart has held roles in web development and information architecture.2
Expertise and Skills
Stuart Langridge possesses a wide range of skills and expertise:
- Software Engineering: His primary focus is on freelance software engineering.2
- Web Development: He has significant experience in web development.2
- Digital Marketing: Stuart has knowledge in SEO, PPC, CRO, and social media marketing.1
- Writing: He has authored books, including "DHTML Utopia," and has worked as a columnist.2
Career Duration
It's worth noting that Stuart has been self-employed for a considerable time. As of June 2023, he was approaching his tenth year of self-employment.3
Stuart Langridge's LinkedIn profile, under the username "stuartlangridge," reflects his diverse professional background and expertise in the technology and digital marketing fields.
Highlights
Will Cooke is #hiring. Know anyone who might be interested?
A #WebPrivacy tip.
All the websites you build are https these days, right? Good. If you do http too, you should redirect it to https as well. This protects your users' privacy, and ensures that your site won't show up on whynohttps.com if it becomes popular.
But in addition to going https, do you know about HSTS? HSTS is short for "HTTP Strict-Transport-Security", and is a way of locking a browser into using HTTPS for your service forevermore. HTTPS is good for privacy, and HSTS is good for HTTPS.
Add the HSTS header to your outgoing responses: Strict-Transport-Security: max-age=300; includeSubDomains
Then once it's OK, increase max-age. (It's in seconds and you want it to be 31536000 (1 year) but recovery is hard if you screw up. So go easy at first.)
For more detail on HSTS (and Upgrade-Insecure-Requests and whynothttps.com), check out Learn Privacy at . And if you like that and want me to write things for you, get in touch! #stuartwriting
