Tim Lafosse

@Miguel__Fortes Yep, I’ll dm you

@Tim_Lafosse Hey these still going?

Selling two tickets for Body Movements festival this Sunday (25th August), Southwark Park London. Entry before 2:30 pm Can share via RA app

@Lev_Olo Can’t seem to send a DM, have you got DM’s on followers only set? Feel free to message me if easiest

@Lev_Olo I’m interested, will dm you

Looking for 1x saturday pride village party (pvp) brighton ticket #BrightonPride

The primary rule of user interface design is that users won't read a single god damn word you put on the page.

Me: DAOs DeFi Serverless infra protocols Play to earn gaming Accessible stable currencies Digital art Front ends competing on back ends Community equity * Banking the ~1.7 billion unbanked Actual content ownership Public goods movement 1/2

Confirmed: TikTok owner ByteDance is acquiring VR headset maker, Pico. uploadvr.com/bytedance-buyi…

#100DaysOfCode R1D56: More solidity via #CryptoZombies. Figured out that the last X digits of a number Y is Y % 10^X. e.g. 1234 % 10 = 4, 1234 % 10^2 = 34. I don't know how I didn't realise this before, it now seems so simple and useful

#100DaysOfCode R1D54/55: Continued familiarising myself with the Solidity syntax using #CryptoZombies. It's quite different to the Python/JS I am most familiar with but shares a lot of similarities to the C++ I started this challenge with.

#100DaysOfCode R1D53: @WellPaidGeek and @oliverjumpertz have inspired me to dip my toe into some Solidity and I'm loving it so far. I recommend checking out #CryptoZombies for a simple and fun tutorial that introduces the syntax.

#100DaysOfCode R1D52: Forgot to tweet before work this morning. Continued working on a getting a basic prototype both working. Having some issues debugging an error Open CV. I'd forgotten how 'useful' Python error messages can be...

#100DaysOfCode R1D51: Started using pyautogui again to. Namely, the screenshot function to set up the visual triggers that will be searched for on screen as matches for character actions. Working on making a quick prototype this time around, instead of over complicating things.

#100DaysOfCode R1D50: Halfway through. Took a little longer to reach this point than I had hoped. A flare up of a health condition has made it difficult to find the time to keep chipping away lately but I'm glad with what I have learned and achieved so far.

@NanouuSymeon No, for some reason my mum thinks I do cyber security stuff😭

#100DaysOfCode R1D49: Picked back up my OSRS bot using python that I started at the beginning of lockdown. I've since tried out game design which was not for me to hoping this gaming automation project will interest me a little more. So far, so good

#100DaysOfCode R1D48: Finished wiring up my expense app to pull down expenses that already exist in firebase on first render. It can now also add expenses in the app which are saved to the database and displayed again on the page

#100DaysOfCode R1D47: Started work pulling down the expenses that already exist in my database in to the redux store to be displayed on page on first render. Previously the store was cleared after each refresh which was less than ideal

‘Replace the keyboard’ they said ‘Don’t waste your money on paying for repairs.’ Over 100 screws later, I wish I could say it was worth the effort....

@EP__97 A classic Ethan scenario. You did always struggle with numbers > 40. Always here for you x

#100DaysOfCode R1D46: The eagle-eyed of you will have noticed I managed to repeat my use of the number 41 a few days back...this was a test and you all failed (+ started work of implementing a test database to use in my Jest/enzyme environment along side my development server)