Great list that sparked my memory. The tmux scroll back issue was very frustrating for me, and ultimately what made me stop using it. What got me hooked on trying to use it - I do remember being amazed I could close my laptop, go home, and just reopen my laptop and immediately start typing away on my remote terminal without issue most of the time.
A few other issues I do remember running into (probably 10 years ago?):
1. Because it was udp, sometimes a captive portal, work, or hotel firewall blocked it.
2. It was also not installed by default anywhere, so sometimes sysadmins at work were unwilling to install it for me.
3. I sometimes ran into issues with color handling and utf8. I honestly don't remember if it was mosh or my terminal, though. It seemed to happen more often when I used mosh, but I could be misremembering.
It is an advanced driving assistance system. It kind of drives your car for you (lane centering, basic obstacle avoidance, and adaptive cruise control all without you have to touch the wheel or the pedals) as long as you’re looking forward and paying attention to the road.
They have demonstrated full self driving capabilities with a car driving “itself” to Taco Bell. I have a comma3 and have never had much success with that feature. The car drove itself very slowly and seems to just weirdly creep through stop signs. I think the last time I tested that was over a year and a half ago, so it may have improved.
I use mine only on the highways. I noticed for long trips (6+ hours), I can drive longer distances in one go and not feel as fatigued when I reach my destination. As an example, a 10 hour trip to visit family (11-12 hours including stops) I can do by myself in one day with the comma device instead of stopping halfway, or splitting driving time with someone else. For shorter trips (3-6 hours), I arrive to my destination with more energy than when I drive without these features. I am also able to focus more on potential obstacles further down the road than without it.
I think my device has already paid for itself thanks to a couple year period where I had to do that 12 hour trip I mentioned a couple times per month. Plus it is a really nice dash cam.
If you're considering a similar pattern with Flutter rather than ReactNative, they call it "add to app" and there's a couple good talks on how others have approached this [1], [2] from the recent FlutterConUSA, as well as a couple articles that include details and case studies [3], [4]
I haven't tried this myself with a large project (just small examples as proof-of-concepts), but the approach seems very sound. One thing I liked is once you have the legacy app shell figured out, it's not a crazy approach to mock out the bridge/native services and run the app in just flutter (or react native) for development/testing acceleration, then adding final integration testing/QA with the full legacy app shell. I've seen some odd behaviors from apps that have used this approach that I would have to imagine can be serious headaches to debug. That said, it does seem the approach pays off long-term.
There's not much published online about it, but I believe Headspace has used this approach for its mobile app. See [5]
Agreed with the comments on the demo video music. It was startling.
I'm pretty skeptical still as all your demo has shown is similar to what a boilerplate tool might do, but with more unknowns. You have to start somewhere, though, and I think you're on a decent path.
I've been experimenting with chatgpt to do similar workflows to what you're describing for your vision of Second. From my experiments, it seems your demo may be approaching close to the current limits of gpt models. Fine-tune training on my existing code base and requirements may help, but I still feel like we're a very long way away from your vision for Second. Maybe even far enough away that it won't ever be realized.
Still, you've already built a much better workflow than my experiments have yielded so far, and I think it is a very exciting proposition.
Feel free to disregard, but I think I'd approach the business differently than you have - raise your prices drastically and instead of a dev-facing tool to start, make your offering more like an agency. Hire devs and designers to build the client work and sales people to find more deals. Have devs and designers use your tool, providing feedback. Restrict modes of communication to AI-parseable docs between the client and devs/designers. Collect data as you iterate through as many projects as you can find and staff to deliver. Then train/fine-tune LLMs on that whole dataset. Iterate on your tool throughout this whole process. Even better if you could embed yourself/your tool into existing agencies and dev shop firms, but that seems like it could be difficult to navigate.
I was educated in the US and took AP US History in high school. I don't recall a specific reference to Zersetzung within that curriculum, but the idea that life in East Germany was difficult due to Stasi oppression was covered. I don't recall specific examples like the story I asked about though (besides my own extracurricular references from movies/books).
> IBM, Bell Labs, GE; who else should be on that list?
Intel felt quite a bit like IBM during my time there circa 2010.
I wasn't familiar with this quote, but wow was that my experience at large tech orgs. I wish I would have known this about 15 years ago, as perhaps I would have done a better job picking orgs to work at early in my career instead of being so frustrated.
Not directly relevant, but I've had all sorts of issues, similar in nature, with other companies that use Zendesk and integrations with Zendesk. It seems surprisingly bad given its popularity.
Flutter is actively working on the bug you're referring to, and I think you're valid in bringing this critique of the jankyness of animations on first run, but the large number of Flutter apps currently deployed clearly proves it is very usable on iOS. You have to workaround that jank, which is extremely frustrating, but I wouldn't write off the entire platform for it. It will be fixed.
FWIW, the cold start issue (which was hitting me with regular 10-30+ second delays for even the simplest of functions) has recently been "fixed" (at least, I'm down to <1-2 second cold starts).
> Business is not about doing things right, it's about being profitable
I find this line particularly insightful. It was the biggest lesson I learned in my transition from academia to industry. No one cared that my work was correct and on time, they cared that the vendor we used caused us to miss the deadline and because I was in charge of the overall system, it was still my fault. A tough lesson, but a good one.
1. Media player connected to projector running RasPlex - this software is outdated enough and buffers on some high bitrate content that I should buy a replacement device, but it still works well enough. I tried upgrading to a newer raspi and wasted an hour trying to get it to run, then gave up. So, I still use my old one. It still gets used daily and works well enough (only issue is the buffering on occasion).
2. RetroPie - I rarely game, but it's cool to be able to turn this on and have a library of all the games I played (and those I never had) from childhood.
The other 2 I just have sitting on my desk and occasionally use for small dev projects or to test out some new project I read about on here, hackaday, etc.
An ongoing project that I haven't made much progress with is an automated turret that squirts squirrels with water. I made something similar in college (a "paintball gun" turret with openCV blob detection/tracking) that had decent performance. Now that openCV on rpi can outperform my old college laptop, I want to setup the pi to detect squirrels, track them, and keep them away from a bird feeder/plants in my backyard.
A few other issues I do remember running into (probably 10 years ago?):
1. Because it was udp, sometimes a captive portal, work, or hotel firewall blocked it.
2. It was also not installed by default anywhere, so sometimes sysadmins at work were unwilling to install it for me.
3. I sometimes ran into issues with color handling and utf8. I honestly don't remember if it was mosh or my terminal, though. It seemed to happen more often when I used mosh, but I could be misremembering.