Fable is great. But do you know what's better? Something that costs a little less and has better route modeling out of the box specialized for coding tasks.
I mean for tokens sake subscriptions aren't gonna be forever. Better build some cheap alternatives first.
স্টুডেন্ট লাইফে কমিউনিটি থেকে যা শিখেছি, কিছুটা ব্যাক দেওয়ার চেষ্টা।
আশা করি যারা দেখবে তারা ফিডব্যাক আর সাজেশন দিয়ে আমাকে আরও ইমপ্রুভ করতে হেল্প করবেন বা ফিউচারে আর কিসের উপর কনটেন্ট বানালে ভালো হয় আইডিয়া দিয়ে যাবেন।
https://t.co/EkuTqrF6pD
@lukefernandezio@1Umairshaikh Calls feel too intrusive to me. Usually just mail/msg on socials. But the highest response rate is when you talk to them face to face.
@PrimeLioRX782@IAmPascio The number of projects isn't very good measure. I usually work in one session per project. Agents get deployed based on work complexity via work tree. Average is at 2-3 , max about 8.
I work on 3-4 sessions in parallel since I never maintain more than 5 side projects.
@NitinthisSide_ It's developer C:
- Researches new AI architecture.
- Fine tuned low level software to milk more performance out of GPU.
- Trains and improves AI models so Developer A and B become less valuable every year.
Polsia just raised $30M at a $250M valuation.
Approaching $10M annual run rate.
One Founder + AI. Zero employees.
Polsia runs companies autonomously.
It also ran its own fundraising.
I just showed up for signatures.
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
Although worried about AI but one thing I am loving about it is the improvement to engineering quality. More code is under test coverage and more people are thinking about architecture and performance. We can use the extra compute for SLOP or Strategy.
The choice is ours.