IndieWeb post types

Yes do it!! Nottingham would love to have you here 😁

Q: What can you do as a consumer?

Answer from Jeremy: Use #Firefox and anti-tracking software Answer from Remy: Don't be a consumer - build for the Web platform, make and share things

Jeremy: Nowadays, having a website is "disruptive" - use that to your advantage!

#TechNott

A great point from @adactio - don't resign yourself to inevitability. We can change the way that the Web works, we can take back our control, as long as we fight for it. #TechNott #IndieWeb

"Reducing complexity increases chance of mass adoption" - this is the reason that folks are seeing this content on Twitter on #TechNott rather than directly on my own blog.

But the #IndieWeb are trying to make things better - come and help us build a better Web which works for you!

Also very cool to see the original Web browser had built-in developer tools to allow you to change the content / styles of any web page! #TechNott

This talk from @adactio and @rem at #TechNott is also really interesting to think about how websites and applications age, and potentially whether someone will be resurrecting something you've built in the future?

I thought I spotted a rel=webmention link on the slides earlier at #TechNott 🤓 #IndieWeb

Hand sanitiser being brought down the food queue is a great idea at #TechNott to prevent #coronavirus

Don't fix the thing at 3am - just get it to limp through to tomorrow when you're caffeinated and have your team around to help - great point from @NickyWrightson at #TechNott

I guess it's more that we have development environments to play around with, the staging environment should be treated as prod - ie treat it the same with infra, security, support policies etc.

But that's true - it's better to play in staging than prod!

I both really like the idea of, and am terrified of, not having a staging environment. Having seen how some folks treat their staging environment, I'd never wish users to experience that in production! #TechNott

Consider your error handling better - does it mean you want to get called out if you hit an error? Is it actually an error scenario? #TechNott

We've got the awesome @NickyWrightson kicking off her talk at #TechNott about doing out of hours on call the right way - very excited to see the updates she's made since I saw it in September

#TechNott tonight is buzzing! We've got a packed room, and lots of faces I don't recognise - awesome stuff 🙌

Is anyone at #TechNott interested in #PHP? You're in luck, because Thursday is #PHPMiNDS and we've got the awesome @akrabat speaking about Slim 4: PHP's Microwebframework

More details on the website https://phpminds.org/ and the Meetup https://www.meetup.com/PHPMiNDS-in-Nottingham/events/268999773/

@MrAndrew is kicking off tonight's #TechNott - which is the first of the spring season - with some absolutely awesome speakers. Very excited to hear these talks

I've spent the last few weeks going up over the threshold and then dipping under 😅

Very excited for the talks tonight at #TechNott - @NickyWrightson's talk at #DevOpsDays London was really insightful for how to run on-call right, and I've heard great things about the talk from @adactio and @rem - hope to see y'all there!

Within my team, we use Git flow with 2 person enforced code review before a merge (within a 10 person team). We use the code review to enforce this, alongside any other changes required.

I'm a strong proponent of good commit messages, so one thing I've been doing since joining the team is encouraging this to be better.