I'm a model nomad, using whatever solved my last problem the best and where it makes the most sense to start my next work in.

However with the latest models Fable, Kimi K3, 5.6, it's getting to a point where I sometimes forget what model I am on without noticing a difference. And once I realize it because something may not be exactly like I expected it I won't switch for that work either because I don't want to invalidate the cache.

For the next work I will do there is maybe a 50/50 chance to remember to switch the model before I start.

That's not what I would call stickiness towards a certain provider.

▲ amelius 5 hours ago | parent [-]

You didn't say what kind of problems you solve with AI. It matters a lot if you are doing HTML versus C++, for example.

▲ blensor 5 hours ago | parent [-]

In no order of importance:

  - Refactoring a 13 year old in-house vacation rental booking system ( python/turbogears )
  - Backend development for our VR fitness game ( flask/python )
  - Unity development on our VR fitness game ( C#/Unity )
  - VR game development experiments ( Godot/GDScript )
  - Standalone SLAM localization service ( C++ )
  - Audio analysis ( python/pytorch )
  - Virtual display with Viture display glasses ( C )
  - Reverse engineering a library I am using for another project ( ghidra -> C - no MCP yet, that's something I am looking forward to )
  - Public facing website rebuilding for the booking system above ( PHP/JS )
  - Generative 3D environments for our VR fitness game ( python )
  - Wireless camera/IMU based tracker for the SLAM system ( C )

Once I've dug in with a specific model into a problem I tend to stick to that because I have a feeling what it will do and how well it works, but when I start a new thing I usually use whatever the model was last set to.

	▲	amelius 5 hours ago \| parent [-]
		Wow, now we're talking :)