Some good questions to ask: Can they show you some examples of past projects they've built in Webflow? Do some checking if their work looks good on smaller devices (Webflow cascades styles down from desktop, so mobile design can sometimes get overlooked) Are they using a class framework (e.g., Client-first, Mast, Lumos, or custom)? And are they comfortable building the site with a level of modularity that enables easy reuse of sections, components, and styles? This approach simplifies future design updates and makes it easier for your team to manage and expand the site after the handover. What's their approach to SEO in Webflow? What do they do to ensure performance and loading speed are optimized? Do they have a process QA and testing before launching a site? How do they handle client feedback and revisions? Do they have a process for educating you on how to use and manage the site they built?

Horrible advice: find a way to blend your work with your interests so that you no longer understand where your core work hours start and the obsessiveness begins. Do this for > 12 hours a day, every day, holidays included. Tell your loved ones that you're busy with work, and take small satisfaction that what you just said was half true. Develop an unhealthy addiction to liquid stimulants and spring out of bed every morning with a burning curiosity that wont abate until you've tripped over enough hurdles to crush your enthusiasm for a few hours. Rinse and repeat for a decade until you're no longer a jack of all trades, but a master of most. Try to convey your interests to those around you, and failing that, retreat to social media where you will attempt to spin these as career developing STAR moments. Accept the disappointment you will feel in knowing that no one will appreciate the efforts you went to in achieving this level of tedious mastery.

fully regretting that you didn't focus more on that thing, oh and the other thing plus you're certain life would have been better for everyone if you hadn't dont quite so much of...

I started trimming hobbies. To pacify myself, I told myself that I am not stopping FOREVER, but just for now. It worked. Most of them are gone, I continue with a few, and I occasionally dabble with one or two that I put away.

Start with a group of interests that has the most overlaps in terms of skills or resources needed - call these compounded projects. Out of the compounded projects, start with the one that interests you with 2 weeks of effort. If you can’t make a significant progress in that time frame, you either lack the skills, resource, or interests in them. Move onto the next compounded project.

After you finish with the list of compounded projects, review the original list and prioritize the interests based on your experience. Create compounded projects again and go at it. Repeat.

being elastic with your interest and skills while jumping from project to project is the right approach.

(1) Start by being clear with yourself what things you're interested in knowing about vs. what things you're interested in doing.

The more work in progress streams, the more time you waste context switching. Being intentional about the things you choose to do and the order in which you do them allows you to do more things in the same amount of time than if you tried to do all of them simultaneously.

I had a lot of interests: coding, playing musical instruments, cars, woodworking, embedded systems, audio/video engineering, etc, but I had to pare it down to just a few after having had several bouts of burnouts. I'd recommend trying 200 interests at a shallow level, and eventually you'll find some of them are more interesting than others

The last three jobs I've held in the last 5 years have all felt like someone just handing me the keys to a sinking boat before they jump off. Every job is sold as having at least some greenfield development where you can "own" the domain and "lead" the direction of the project, but once you accept the offer and get on-boarded, you realize that the system is so brittle that any change will completely break and cause incidents, and there is a year's worth of backlog issues to address with duck-tape and glue before you could even consider fixing the fundamental problems.

Often the teams that built these systems are long gone, so there is nobody to ask for help when you're learning the rough edges, you're just on your own. The technology decisions are all completely set in stone because we could never justify the risk of making changes. There is so much tech debt and maintenance work, we don't really have time to do any new development with the current staffing levels. The job then becomes dominated by on-call responsibilities and fire-fighting. It's 90% toil, and almost zero actual system design and development work.

Being responsible for a whole system that you didn't build, that you know is brittle and broken, but which you cannot fix, is incredibly stressful. It's almost a hopeless situation.

To me it's pretty clearly the same targeted advertising available anywhere with the extra claim of using "voice data". It doesn't say what the voice data is or where it comes from. They could say that when people do google searches using Siri/OkGoogle/the microphone option on Google - it's information they would use in an anonymized way to target ads, or rather Google does on your behalf, and it's technically a derivative of voice data.

I'm skeptical this is what people might think it is. To be clear, I think most readers would interpret this as "your phone is surreptiously listening to you via your microphone." If that were true, then there would be telltale signs of resource draw. Handling rich audio data has practical costs, whether battery, CPU, network, memory, and/or disk; that data has to be stored, transmitted, and processed somehow. I've never seen analysis that shows that's happening. Not to mention this capability is beyond what audio capture APIs in Android and iOS offer, as far as I know.