tl;dr - it’s valuable to update your LinkedIn profile to be a concise, accurate, and current summary of your accomplishment. Spend at most two hours updating it, then ask a friend (ideally a recruiter) for feedback. Incorporate that feedback and don’t think about your profile again for at least a year.
While writing my notes on landing an engineering executive role, a topic that came up in feedback a number of times was how valuable it is to have a reasonably good LinkedIn profile.
I started my first executive job search when I was 25. Eventually, I got an offer to lead engineering at a startup with four engineers, which I turned down to join Uber. It wasn’t until a decade later that I joined Calm and started my first executive role. If you start researching executive career paths, you’ll find folks who nominally become engineering executives at 21 when they found a company, and other that are 30+ years into their career without taking an engineering executive role.
You live with your family in Area Delta-44 of floor 212. Floors 140 through 266 are your world. Your life is walls and corridors, air ducts and stairwells, and—if you’re lucky—elevators. You live…
I was just on a call where I heard one of the more succinct definitions of the difference between Postman and the waves of “Full Lifecycle API Management” solutions that have come before us. API Management providers possessed a core set of API gateway capabilities that they would bundle documentation, portal, analytics, and other platform capabilities you will need-—forcing you to buy it all as a bundle. With Postman, and an API platform, you get to choose and pick all the platform capabilities you want to go with your core API capabilities—-you pay for Postman for the privilege of being able to choose. Which in my mind is the way things should be, and a very API-first way to approach things.
GPT and my own career trajectory - Marginal REVOLUTION
For any given output, I suspect fewer people will read my work. You don’t have to think the GPTs can copy me, but at the very least lots of potential readers will be playing around with GPT in lieu of doing other things, including reading me. After all, I already would prefer to “read GPT” […]
ChatGPT and the revenge of history - Marginal REVOLUTION
I have been posing it many questions about Jonathan Swift, Adam Smith, and the Bible. Chat does very well in all those areas, and rarely hallucinates. Is it because those are settled, well-established texts, with none of the drama “still in action”? I suspect Chat is a boon for the historian and the historian of […]
I have been immersed in the Mastodon universe since Thanksgiving. I have been growing my network for both my personal and professional domains, and have been playing with the Mastodon API daily. I have been slowly automating much of my curation, posting, filtering, and other information activities I historically conduct via Twitter, but now I am automating using the Mastodon API. To help me automate using the Mastodon API, I am using a single OpenAPI definition, from which I generate a single reference collection, and use to spawn a mix of capability collections. These collections do one thing for me, helping me accomplish common tasks like posting a message, pulling statuses, and searching for users. I then manually run these collections, schedule using monitors, and bake into CI/CD pipelines for a variety of projects. I have one set of collections I use, and then when I switch between the kinlane.com domain and the apievangelist.com domain, I simply use environments to make the switch—demonstrating the beauty and usefulness of federated APIs (and Postman).