I’d like to tell a story about my #WhitePrivilege. It’s one that helped me land my first office job, which contributed to starting my career while I was still in high school.

1/25 I had worked at a fast food restaurant for a year, had been promoted a couple of times, and I was a traveling team trainer. My next step would have been assistant store manager. But I knew my heart wasn’t in food service for the long run—I wanted to get into engineering.

2/25

I’ve been in that boat as a hiring manager. I’ll share my story from SAP Concur to help shed some (positive) light on the situation, @daveaglick.

#remotework #culture

1/13

https://twitter.com/daveaglick/status/1208515621618671618

When our group was beginning to grow, we knew we needed to foster a remote culture to succeed over time. But the group was young and most of us were new to the company. Only a few folks had experience with distributed teams, and none of us had felt truly successful with it.

2/13

@rj_dudley In summary, OData was a way to serialize a SQL statement into a URL. When first applied, it gave too much power to the client, allowing it to use joins, where clauses, and sorting. A lot of that power can be dialed back now, but I still found it challenging to limit the exposure. @rj_dudley By opening up an OData endpoint, you lose control of what your clients are able to do and you don't have explicit queries or use cases tracked. So when you need to change your schema, it becomes challenging to maintain backward compatibility with what your clients are doing.