5 karma · joined June 18, 2010
Seems like we're both saying "an ounce of prevention..." here
But what this is basically suggesting is "locking out" your employer. While I agree that is absolutely what should happen, doing this without the leadership AND the developer in agreement about why sounds like disaster.
I know it's likely impossible to capture all the work and discussion it takes to reshape a company's process in a blog post, but I feel like if I had a dependence on OT in my company (as the "patient"), and a lockout went into effect, I would be focusing on the lockout, not every other problem in the company that caused it (which as management, it's my job to figure those problems out). What is being suggested is basically arm twisting to get what you want :/
That never works when you cause more pain to the company than it's able to alleviate over time. They'll eventually get tired of the pain and move on to another drug unless you succeed in getting them to understand.
I feel like better advice is to tell developers that they need to discuss this with their direct reports, boss, whomever, and talk about the problem and WHY you'll actually make the company better gains at sustainable pace. And by all means, point out and suggest ways for your boss to improve things.
If after educating your "patient" the issue still persists, of course, twist away. But not everyone in this world needs these sorts of tactics to improve their workplace, and even in those workplaces, there are likely more successful ways to cure the pain, not just treat it.
Surely there is far more to this than simply "throwing weight" around by Apple, unfortunately. As well, it hasn't been that long since the carriers ruled everything about our experience with our phone. I'm sure there's plenty of old bureaucracy left for getting them to say "yes" to what all of us would want.
Perhaps, even, the things that frustrate you were some of the things Apple had to give up to give us the other awesomeness :P
Your reaction was my initial reaction as well, and definitely one I sympathize with (which made me actually comment). But, after thinking about my own basic experiences with contracts (and if you've ever signed a mortgage, for instance; a daunting amount of contractual repercussions, heh), I can only imagine the war room that negotiations must be with those carriers.
But all that, of course, is conjecture... Apple could just be assholes :P
Twin Engine Labs - workwithus@twinenginelabs.com
We're an award winning, cutting edge design and engineering shop. We bootstrapped our company from two people (designer and engineer) to 11, and along the way learned a lot of lessons. A few of them are:
1. Building tools that make our jobs easier in the future is smart and gives our agency an edge. You will be expected to constantly try to improve our process, and your voice will be heard.
2. Following that point, if you think something should change? Do it. Let me know about it (CEO), get buy in from the other engineers, and don't wreck our timelines. But stop talking and start doing!
3. Salespeople will never estimate your project officially. Ultimately, I will bring in a project, lay it in front of you, and ask the team to do a planning poker session. Your velocity is set at a scant 10 points, and the timeline is bid against that initial velocity. Under promise, over deliver.
4. If you estimate poorly, you are expected to fix it. If the project just went off the rails due to things out of your control, then your feet won't be held to the fire, but if it's genuinely your fault, fix it. It's completely in your control.
5. Try the impossible. We built The Fantastic Flying Books of Mr. Morris Lessmore, an impossible feat for it's day. We've built complex interfaces for Cisco, Symantec, and now are working with O'Reilly. Don't be afraid to use 2D Game frameworks if you have to. People don't contract Twin Engine Labs to do the status quo.
6. Be a full stack engineer. Know iOS but not Rails? Talk to us. Know Rails but not iOS? Talk to us. You will be placed in projects of your capacity, but very quickly ramped up to both platforms. We expect you to know everything from server deployments to iOS deployments, to Postgres optimization to Core Data optimization, from caching in Restful APIs to caching NSURL connections. Being a full stack engineer allows you to move faster than every other shop out there.
7. Finally, work directly with the customer. You, as the engineer, will always be expected to speak with the customer faster than I can. I will always give you air cover when you need it (and I typically can see that coming from a mile away). As well, you'll hear their requirements from their mouths (no games of telephone here), and get to ask them questions, with the safety net that I always stand behind our employees.
Perks? Multiple projects in a year, constantly learning the cutting edge techniques, and some seriously huge names under your belt.
Our environment is flat. No Pointy Haired Bosses allowed or bean counters here. Paint yourself purple, turn yourself upside down, and spin around three times while you code. As long as you deliver, I don't care how you do it.
Employees come into work at what is a reasonable hour to them. Our employees set their own start times, with flexible work at home situations when required. Most of them come into work because... well... we like each other :)
Intrigued? Talk to us. We've helped multiple entrepreneurs sink funding, watched multiple apps receive awards, and are known in our region and nationally.
Being able to have windows automatically be positioned is key to the tiling wm, I feel. It allows you to have a layout work as you'd expect without fumbling or thinking about it.
I do agree about the inaccessibility of desktop Linux (though it seems to be getting so much better these days!). A previous co-worker of mine uses AwesomeWM every day inside of a VMWare instance with Mac hotkeys disabled and loves doing that. Might want to give that a shot if you like what SizeUp gives you.
Anywho, figured some examples might give others' a heads up before devoting hours and mind share to trying it out.
I used to be a Mac/TextMate zealot (Rubyist, go figure), and have wholly switched over to AwesomeWM, Vim, and a host of other open source tools and will never look back. I just feel like an incapable two year old with a messy desk trying to work in a floating WM like OS X/Windows now.
If you want to try AwesomeWM, but don't want to risk going crazy from setting up xinit scripts or scrapping all that vanilla Gnome install gives you, follow this wiki article and it'll side side-by-side in Gnome: http://awesome.naquadah.org/wiki/Quickly_Setting_up_Awesome_...
I get NetworkManager support, audio support, bluetooth, and battery life all out of the box. As long as you're not a purist about what's running in your WM and what's not, this setup works great with little risk/time investment.