Jeremy Ho

@jeremyqho

still drawing maps. third culture kid. creativity/cognition. code/no-code. product/tech lead, ex-uber. on deck ✏️🌒🏀

San Francisco, CA
Vrijeme pridruživanja: lipanj 2012.

Tweetovi

Blokirali ste korisnika/cu @jeremyqho

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @jeremyqho

  1. Prikvačeni tweet
    12. pro 2019.

    is programming at higher levels of abstraction. Thoughts on software’s new building blocks

    Poništi
  2. 27. pro 2019.

    An easy habit for your post-holidays: the first time you use a new gift, take a picture and send it to the giver. Only takes a few seconds, shows appreciation, and gifts the giver a free feel-good moment.

    Poništi
  3. 21. pro 2019.

    Version control is amazing. Imagine an equivalent in architecture/interior design: walking through a historical building with an AR overlay - every item/feature is labeled with its origin date, creator, and notes on the design/structural rationale

    Prikaži ovu nit
    Poništi
  4. 21. pro 2019.

    Strongly relate. I navigate code with git annotations always visible. Each room has a place and tells a story, with all items tagged in time and attributed to their creators. Context is powerful in collaborative creation environment

    Prikaži ovu nit
    Poništi
  5. 19. pro 2019.

    Participating in the 2nd cohort of On Deck was one of the best decisions I made in 2019. Met so many talented and passionate folks, received access to top tier resources, and made great new friends while at it. Super impressed by the community that's being built. Join in!

    Poništi
  6. 18. pro 2019.

    Awesome getting to riff on nocode with . Prep tips for other livestream newbies: 1. internet-check (cmon wework), 2. equipment-check (mic echo got in my head), 3) enviro-check (phonebooth got heated!). Super cool new XP - more (written) thoughts forthcoming

    Poništi
  7. 17. pro 2019.

    Curious how/whether nocode might impact this

    Prikaži ovu nit
    Poništi
  8. 17. pro 2019.

    The best designers I’ve worked with would be thinking about all stages of the process, from their design mocks to the users experiencing them - this meant understanding code and the production workflow that realizes their vision

    Prikaži ovu nit
    Poništi
  9. 17. pro 2019.

    2 There are new platforms (eg ) that are tackling the challenging problem of improving the traditional code translation/handoff process. Very interesting if devs can define the rules that translate design changes to code/production

    Prikaži ovu nit
    Poništi
  10. 17. pro 2019.

    No code allows design and devs to collaborate and build in the same tool/language - bypassing the “code translation” part of the traditional process. Some nocode tools aspire to encompass both the design+dev workflows

    Prikaži ovu nit
    Poništi
  11. 17. pro 2019.

    I used to believe more designers would learn UI code to bridge the design->eng divide in product development. Two developments (incl. ) are making me rethink this:

    Prikaži ovu nit
    Poništi
  12. 13. pro 2019.

    The first time you see your thoughts translated in a language you don't speak - then think about other people thinking those thoughts, in that language... Ideas are language agnostic.

    Poništi
  13. 24. stu 2019.

    What ideas might be able to flourish when complexity can get out of the way of creation? That, in my mind, is the possibility of

    Poništi
  14. 7. stu 2019.

    The language of programming is fairly universal interfaces (buttons, text boxes, arrows), as opposed to esoteric computer words

    Prikaži ovu nit
    Poništi
  15. 7. stu 2019.

    The trade-off is extensibility and (Turing) completeness for accessibility and speed. I.e Not 100% configurable, but easier to build (“program”) many common things with lower barrier to entry

    Prikaži ovu nit
    Poništi
  16. 7. stu 2019.

    is just code - at new/higher level of abstractions (the GUI). Underlying are the same concepts of programming, now made more accessible.

    Prikaži ovu nit
    Poništi
  17. 5. stu 2019.

    👏. This is the area I’d point non-maker devs/“coders” to to start understanding/embracing the “no-code” mvmt (not the “build products from scratch” category). No/low-code can get you more leverage from your code time/resources

    Prikaži ovu nit
    Poništi
  18. 5. stu 2019.

    For devs hired/pitched on building features for the core product, developing internal tooling can be less appealing. Also dev work/envs often differ between the two, which leads to inefficiencies in context switching, onboarding, etc

    Prikaži ovu nit
    Poništi
  19. 5. stu 2019.

    Why? Smaller teams need to reuse the same eng talent across internal tooling vs. external product projects. No-code can offload eng effort where common abstractions/tasks are useful.

    Prikaži ovu nit
    Poništi
  20. 5. stu 2019.

    tools empower teams without access to tech resources/support to become tech-enabled. At bigger co’s, adoption likely starts with tooling for internal ops. Adopting no-code in this area may also help retain eng talent

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·