Counter argument: Not everything a frontend engineer wants should be available via one API call. Particularly if your API is available to 3rd parties.
API design is a skill, but if you are taking a UI first approach, then make it a useful endpoint for EVERYONE, not just your own frontend team!
For the last couple of months I've been pretty burnt out on work and the world. Although it only took a bit of parsing a binary file and spitting out some graphs to cheer me right up again
Even as a team lead, my main language these days is markdown
I choose to believe he was playing 4D chess, rather than a completely clueless prompt jockey. The reddit thread was an interesting read too: www.reddit.com/r/Programmer...
The more I read, the more I feel this was a giant grift. The site was intentionally poor to drive people to it to see how poor it was.
The sites purpose: "Turn anonymous website visitors into B2B leads.
Identify companies visiting your website and get access to decision-makers’ emails."
Manager: "What's this milestone 'Living on a prayer' ?"
Me: "That's the documentation deliverable."
Manager: "What's the status of that?"
Me: "We're halfway there"
Manager: "Why is progress so slow?"
Me: "You fired Tommy"
Manager: "So?"
Me: "Tommy used to work on the docs"
I love developer curiosity. I was talking to a devops colleague about using open telemetry, but we may need to change how we collect metrics.
"Oh! One of my team has done a PoC for using open telemetry!"
A black and white cat sulking on a red cushion
Particularly cold day in the office, so I turned on my heated desk pad. This idiot is giving me their best sulking face after I kicked her off said heated mat.
It's highly dependent on the person. I try and structure it so that they have a few sprints of simpler tasks/bugs interspersed with riding shotgun with a senior engineer. Even with simpler bugs; get the to go away and poke about, then come back to a senior with a plan of how they want to implement.
The rolling stones once said:
You can't always get what you want.
But if you try sometimes,
well, you just might find,
you become team lead.
I wouldn't recommend this as the best career development strategy
A week at #ndclondon done. Absolutely exhausted, but wired to get the ball rolling on some projects. Big thanks to @rendle.dev for the high performance dotnet workshop. Definitely showing the value of revisiting, revalidating and iterating as dotnet gets better.
Wilbur, a large dog who is a Very Good Boy, wearing his NDC London attendee badge.
You get to meet the most wonderful people at @ndcconferences.com.
Loving the OTEL integration with Aspire, but I think I have a fundamental problem with it. Aspire seems to promote microservice patterns, but doesn't solve the inherent problems of them.
Day 2 of the NDC workshops. Day 1 is definitely still in the queue awaiting processing.
I never really got onboard with professional social media before, my linked in is a testament to this, but I'm going to give it another go
