wceu

  • “Successful writing is not done after publishing. My job isn’t just to publish, but to help my clients with their goals.” @darioohead #WCEU

  • “Find someone to review your writing. Reviewers might tell you things you don’t want to hear. They’re a blessing.” @darioohead #WCEU

  • Online tools to help w/ writing: grammarly.com ( free grammar checker ) hemingwayapp.com @darioohead #WCEU

  • .@darioohead now at @WCEurope sharing writing tips and how to write to achieve your goals. #WCEU

  • Next lightning @WCEurope talk: “Translating WordPress into a Language Nobody Speaks” #WCEU @swissspidy

  • “Accessibly at WordCamps doesn’t have to be expensive. Focus on your attendees… make the event accessible as possible.” @miss_jwo #WCEU

  • Take it from me (#wcmia organizer). You can never have enough signs at a WordCamp. @miss_jwo #WCEU

  • “Coffee and tea are the bloodline of events. Not being able to access that is a problem.” @miss_jwo #WCEU

  • Up next: @boemedia talking about the Importance of Information Architecture at @WCEurope. #WCEU

  • Listening now to @miss_jwo at @WCEurope who is talking about diversity and the dangers of ignoring it. #WCEU

  • I don’t have to imagine. I have Twitter. #WCEU twitter.com/jillbinder/sta…

  • If the child care area at @WCEurope doesn’t have a sign outside with “child themes here” on it then an opportunity was missed. #WCEU

  • “Use a passward manager. That way when your boyfriend/girlfriend asks you your Facebook PWD, you say you don’t know.” @markjaquith #WCEU

  • C.L.U.E. – how to pick a password. Complex, Long, Unique, Enigmatic. @markjaquith #WCEU

  • “Don’t put production credentials in your code repo. Keep them in a separate file that Git ignores.” @markjaquith #WCEU

  • “You can use a GIT diff and easily tell if files have been unexpectedly modified.” @markjaquith #WCEU

  • “Update everything. Doesn’t matter how secure WordPress is if your platform isn’t secure.” @markjaquith #WCEU

  • In code, don’t repeat yourself. In code, don’t repeat yourself. In code, don’t repeat yourself. In code, don’t repeat… @markjaquith #WCEU

  • “Sanitize everything.” Like when your 5yr old brings you a “sandwich” she made. @markjaquith #WCEU

  • Me during @markjaquith talk. #WCEU

  • “Don’t trust yourself. The code you wrote two years ago was a worse version of you.” @markjaquith #WCEU

  • “Trust no one – don’t trust the people who wrote previous code, nor users that enter data.” @markjaquith #WCEU

  • BIEBER ALERT. @markjaquith #WCEU

  • “Security is not a destination… you’re never done or completely secure.” @markjaquith #WCEU

  • Tip: Never play “2 truths and a lie” with @markjaquith. But good illustration on having a non-trusting security mindset. #WCEU

  • Now listening to @markjaquith at @WCEurope talking about the process and mindset of securing your WordPress site. #WCEU

  • .@lxdraghici shares tips at @WCEurope about how to determine if a feature is worth pursuing. #WCEU

  • “User-central design: we needed to validate assumptions before acting on them, meaning we needed user feedback.” @lxdraghici #WCEU

  • Interesting: @CaptainFormWP has 60+ employees if I heard @lxdraghici right. More than what I would have thought. #WCEU

  • Up next at @WCEurope: @lxdraghici talking about how users have provided ‘gifts’ back to her as a product designer. #WCEU