I've been working 15+ years as a UX developer, with varying results. From my experience, the best way to get developers and designers to work well together is to have frequent short demos/reviews (ideally weekly). That has helped solve random problems like:
1. This user flow does not match backend reality, let me explain why.
2. How does this screen design handle XYZ usage?
3. I cannot export this asset from figma, please share.
4. Would you mind verifying that the fonts/colors/spacing look okay?
5. Are you sure about not reusing an existing icon from our library?
6. How should we handle error and loading states?
7. How important is this design feature? It'll take me a while to build it.
8. Did you expect this desktop layout to be full width or 1600px?
9. Can you give me an overview of what changed since the last design version?
10. This is how I implemented the design. Is that correct?
Highly recommend Brian's Tacklebox program. It helped me create a framework for validating my product idea, while gaining the skills (and confidence) for running customer interviews, landing page tests, mapping markets, etc.
Obviously, you still need to put in the work to reach out to potential users. But the program helps you approach it in a structured format.
I did this back in 2014 with my wife-to-be. We traveled through Ireland, England, France, Spain & India.
In order to stretch our travel funds, we took local transport, stayed in hostels and campsites, and ate street food. Somewhat proud of the fact that we lived + traveled on $30-$90/day for more than a year.
For me, the best part was taking the same buses and trains as the locals. It gives you a glimpse into their everyday routine and also makes it easier to start a conversation.
Coming back and restarting income took a while though. Mainly because of personal preferences on the kind of work... ultimately just ended up doing the same kind of work that I left (frontend development).
Thinking of doing it again this year, but too scared to abandon income yet again. Might just try remote work this time.
Strange how "broadband" and "high speed internet" can have a different meaning in various parts of the country. For ex: a 10 mbps dsl line is considered "high speed" in New Hampshire.
> It does not take AirBnB to have problems with other parties within an apartment block.
This is important to note. AirBnB is not the "cause" of the problem, but seems to make it easier to cause the problem. Shouldn't they just increase the guest liability?
I'm a strong proponent of "living like the locals" so hope that spirit of AirBnB does not fade away.
Yes, it does seem vague. Isn't the NHTSA investigation meant to be a non-biased root-cause-analysis about last year's trailer crash? Instead, this just seems to be a grading report on Tesla's autopilot compliance.
This is pretty neat! I've been thinking of having a goal of writing one article + presentation every month, and this is the perfect workflow to accomplish both - write the article draft in markdown format, and then run this tool when ready to publish.
Curious about a couple of things:
1. Is there a way to add notes to the presentation?
2. Is the {.big} notation standard markdown, or something specific to this tool?
I've noticed strong feelings of obsession towards an idea/goal, particularly when it's not achievable.