I realised that I don't always use AI the right way, and one sometimes leave me stressed.
When I know what I'm talking about, or I'm willing to learn what's happening, I'm engaged the whole time, still passionate about all things tech.
When I hand a domain over to AI and I don't take the time to understand it, it feels less like a skill and more like a slot machine. That one leaves me stressed.
Is a foldable device the future of the laptop? Since I can reach my machine from anywhere, and we work more and more via "chats", the big screen has become something I need for specific tasks, not were I need to be all the time. A lot of jobs may not need a desk at all.
I've been using @WisprFlow for a while. I expected the productivity boost, what I didn't expect are the insights.
They show me how I actually communicate with AI. I wish they would go deeper. It's helping me understand my own communication style much better, which makes me reflects in the way I talk to people too.
Coming around to this: coding used to be full of emotion and human bias, we wrote it all by hand, after all, we had a connection β€οΈ. With AI, code is impersonal, and imo is fine.
"Nobody" feels attacked when an agent rewrites a file in our PR, or when a review asks you to touch code you would have defended a year ago.
In the long term I think this means better standardisation and higher quality.
@TermiusHQ@Tailscale I tried Claude Dispatch or other cloud agents approach. Same problem every time: it's not my machine. Different environment, not a great access and I can't step in and take over when something goes sideways or when I'm closer to a bigger screen.
Two weeks ago I got @TermiusHQ + @Tailscale working together. Now I can reach the machine my agents run on from anywhere, and pick up those same sessions when I get home.
It's beautiful, and I can walk and wonder while I work on my personal projects.
I do essentially everything on my computer through the terminal. So this isn't a workaround for me, it's my actual setup same config, same tools, same running sessions.
@StaniKulechov The key takeaway is that this should never have been possible. There are moments where a warning is sufficient, and moments where the pricing is clearly unfavourable. This was the latter, imo.
@matt_krandel@TomFrankly@joelrunyon Unless you can benefit from the first-mover advantage, having a PWA competing with native/hybrid apps is a big risk (quality, performance, etc.) and even then if you get traction... you now have to build something for real. New team, new competencies, a completely new app...
@TomFrankly@matt_krandel@joelrunyon Iβd also donβt underestimate the impact that an MVP can have on the final product. Iβd no longer consider PWA a good option nowadays, personally Iβd go for hybrid approach with RN or Flatter
@GergelyOrosz Interesting! With some friends we were saying that IT is a world that needs the same amount of people as the contraction worker industry but has way higher barrier to enter it. If this barrier is reduced we will just do more projects, non the same with less people (imo)
@GergelyOrosz How is it possible that Teams is considered better or same level of Slack? Out of 270m users only a tiny tiny amount is using it because they want but most of them because they have to. On the other side you CHOOSE Slack. There is so much more value in that 20m users
@jjenzz@expo Curious to read the answers! The only way I was able to solve it has been by listening to the events on the native side and rendering a native view