I wonder if the pressure equalization is a first for these and not in the originals. It might be the win that actually makes them comfortable this time around.
I’m intrigued to actually try this. Turning the transparency setting on and off.
On an active phone call I can carry on a conversation in the room im in 10 feet away from the person. To have that cancelled out would be interesting to try.
Noise cancelling cancels out white noise - not people's conversations.
Also - the "transparency" mode is quite common feature of noise cancelling headphones. All of the Bose NCs have had this for years. When you seal off the ear to provide NC you need to be able to hear yourself when youre on a phone call. So its more a necessity than a "nice to have".
I got hired as a project manager to oversee the 5 programmers on a massive project once. Their previous “supervisor” was the owner/ceo with NO technical background for about 14 months.
Every single feature and block of code was written in 30% the time it should have been given. The ceo had no idea the technical debt he was creating until it was too late.
The day I came aboard any new feature or change that could be completed in 100% standard time needed 200%+ the standard time to account for the shortcuts taken over the previous 14 months.
How did you approach your role as PM, aware of the tech debt but also reporting to an unaware CEO? Power through with new features at half the speed, or try to convince the CEO to allow refactoring/maintenance?
Sorry for the delayed response (no notification on mobile).
For some reason my relationship with the ceo was viewed as trusting whereas their programming team was not. I was able to get the time required (in 9 out of 10 situations) by explaining in detail why it was required.
We actually had a complete rewrite in the pipeline - an architecture written by myself - that was on the table. But they shut down before that was possible.
I don’t regret taking the position despite the frustration and difficult inherent to what I had to tackle. I got a very closeup view on technical debt that has assisted me throughout my entire career.
I do the same thing and do it for the entire “core”. Templating, session management, database tie in (all for a stateless, cloud app).
I improve it every project and it’s easy to start from there than scratch. I don’t like using available base code due to not needing 90% of features and it always feels like bloat.
I was in a situation similar to yours in 2012. I had worked for a small business programming and social media marketing firm. It was only the owner and myself working in the business – as well as subcontractors.
It was spoken about between the owner and I for years how we would grow the business and I would eventually become a partner.
We started at 32,000 a year, moved up to 70,000 a year, and moved up to $120,000 a year. When it was time to decide to take a contract worth several hundred thousand dollars… The owner decided not to because she didn’t want to grow the business that large.
I felt as though I wasted three years of my life working for a company that had no intention of actually really furthering my career -and my livelihood.
The following month I quit and left for another business. It sucked. The whole entire process. Leaving and explaining why.
My advice is to move on and try not to focus too much on it. You did as best as you could.
Additionally for mobile apps they support in app purchase subscriptions as well. You could use phonegap to develop current mobile apps with just HTML/css/backend-programming.
