as bad as things have gotten in the past 4 days, they are going to get a lot worse before they get better. security leaders, never let a crisis go to waste: please go to your boards and ask for help right now. not for ai, for the basics. (we need to hold on for ~18 months.)
@RouteBetter Congrats on the update. UI definitely looks cleaner and better organized. It appears the maximum charge option has been removed though, and the planner seems to like targeting >95% like on this example. That 65-100% charge takes forever, even on the Taycan.
@itskyleconner I keep thinking a @Rivian and @LucidMotors merger (keeping the brands separate) would create the best EV auto group. They seem to have complementary strengths and even already target different audiences. Idk but it’s like it’s meant to be. Thoughts?
@JackRhysider@wiglenet Phones should geofence saved Wi-Fi networks using initial connection location; only auto-connect within a reasonable radius. They track GPS location constantly anyway—leverage for user's benefit.
@BeardedTesla This is Tesla’s fault if we’re being honest. NACS adoption is win, for sure, but opening up the v3 superchargers without extending their reach ruins the experience for everyone. No one wants to park like that.
@itskyleconner@ionnaofficial Great growth and cool model but @PilotFlyingJ was MVP for us on our 1300 mile trip this week. Not splashy but they were reliable and fast on the 6 charges I did with them on my Taycan. Basically same experience as gas and that’s key for mass adoption.
Developers think Software Architects have the easiest highly paid job.
Well... not quite 👇
Here's what devs imagine an Architect does:
- Doesn't write code
- Draws diagrams all day
- Just makes decisions in meetings
- Gets to choose the "cool" tech stack
- Always says "yes" or "no" with confidence
- Doesn't have to deal with bugs
- Works only 4 hours a day
- Has a high salary
But here's what actually happens:
- Writes the core code everyone else will build on
- Spends hours reviewing pull requests for critical changes
- Explains the same architecture to 5 different teams
- Balances business needs with technical debt
- Makes trade-offs nobody will be happy about
- Deals with production issues at 2 AM
- Handles conflicting opinions from stakeholders
- Documents decisions so future devs understand why
- Manages tech stack upgrades without breaking things
- Tracks performance, security, and scalability risks
- Mentors developers while staying hands-on
- Negotiates scope and timelines under pressure
- Reads endless RFCs and framework updates
- Constantly defends architecture choices with data
- Stays accountable when things go wrong
- Learning new things each week to keep up with changing technology
Being a Software Architect is rewarding — but it's far from easy.
It's not just about drawing boxes; it's about owning the outcomes.
What's the biggest misconception you've heard about Software Architects?
—
♻️ Repost to help others learn about Software Architect role
➕ Follow me ( @AntonMartyniuk ) for more
@P4LSEC “It’s just like showing an ID to buy booze!” Except that the clerk now takes a copy of your ID and puts it in a public S3 bucket; not that securing it would make a difference since they’ll just be selling it to anyone anyways.