https://stackoverflow.com/questions/16426398/active-admin-in...
2,869 karma · joined March 30, 2011
https://stackoverflow.com/questions/16426398/active-admin-in...
Removing the character limit is similar to the spam problem. It shifts the mental burden from the sender to the receiver. Instead of the sender being forced to compress, the receiver has to spend more time processing the text.
https://research.gigaom.com/2013/02/if-amazon-is-the-future-...
> ...temp workers scramble like rats in a maze, pulling boxes off shelves, directed by handheld devices that not only show where the goods are stored but the most efficient path to walk. These devices also monitor each worker’s performance, coaxing them to move faster, move faster, move faster.
Try segmenting potential hires into different categories and using different strategies for each group. You should also clearly communicate the process, so they don't get the wrong idea.
>Additionally, the people who tend to drop off because of this extra effort tend to be senior applicants
Is this before or after the phone screen? If they think the work-hire test is going to be in addition to a phone screen and an on-site whiteboard session, they'll drop. If they're senior devs, you should be able to tell from their resumes. Do a phone screen, and if they pass, explain that they can either do a work-hire test or a whiteboarding session. Explain that the work-hire test should be doable in 4 hours, so they don't envision a week long project. Also explain that it's a substitute for the whiteboard portion of the on-site. People who tend to hate whiteboard coding will choose the work-hire test and vice versa.
If you're trying to find diamonds in the rough among junior talent, sending out a first-pass work-hire test might work. You'd still get better results if you explained that it was short and a substitute for the onsite whiteboard session.
It's always been there. Except now, they have the power of social media. Do you find a view "problematic"? No problem. Just round up a few thousand like-minded cohorts and burn the heretics.
Kalimantan, where the fires are burning, hit 3300 PSI.
http://www.theatlantic.com/national/archive/2014/09/police-o...
Sure. But everyone's looking for senior developers. And salary tends to top out for senior devs, so it's not like salary scales linearly with age.
Intuit would lobby against it.
http://techcrunch.com/2013/03/27/turbotax-maker-funnels-mill...
> So when employers complain about not being able to find workers, what they really mean is that they can’t find workers who meet their specific requirements at the wage they are willing to offer.
e.g. Onsite work, "culture fit", low wages, interview hazing....
After a while, you should start seeing some common ranges between regular software engineers and senior engineers. Use those as a starting point in negotiations. Interview at enough places (10+), and you should see what your market value is.
It depends on where you live. In Silicon Valley, they have local measures to raise parcel taxes to fund the schools. All money stays in the district and none of it goes to administration.
About half of Congress sends their kids to public school.
http://www.publicschoolreview.com/blog/how-many-politicians-...
How is this the hard part? They have a valid excuse. If they work remotely or get their work done, it's not a problem.
I think you're beating yourself up too much. A lot of good programmers feel the same way. [1][2][3] If you haven't done something before, it's going to take longer[4]. Also, spending more time initially isn't bad, if it will save you time in the future.
Part of the reason, you might feel that you're lagging, is that the landscape changes so fast. In another thread, someone pointed out the most productive programmers use a stable set of tools and know them inside out. [5] If you have to keep learning new libraries, this will slow down your productivity. Also, contra to what another poster said, taking notes is a good thing. I frequently come across situations where I feel I've done something, so I look back at my notes or git commits. If I have to make all the same mistakes again, it will take 3-4x as long.
1 - http://www.stilldrinking.org/programming-sucks
2 - https://the-pastry-box-project.net/ed-finkler/2014-july-6
3 - http://www.marco.org/2014/07/11/developers-dystopian-future
>That I’d been told $75k was reasonable, and that I would have to look for work elsewhere if it was going to be $44k.
That sounds like an ultimatum. The problem is he's bluffing. He gets his bluff called, and then what? He's out on the street, in a worse place then he started from. My advice is not to bluff. Get a job first, don't look back. When you take a counter-offer, you also run the risk of having them get resentful, and firing you the first chance possible.
>2/ Typical protection of abusive companies by telling employees who are being openly screwed
This is based on what I've seen. I think companies should pay their employees market wages. But most companies will only give you a 5% raise, not a 20k one. If you know how to consistently get companies to give you a 20k raise, please share.
>3/ Easy to say when you're not living paycheck to paycheck and you see your dream slowly crumble before your eyes
I'm being realistic. Companies don't like hiring people who will take any job. He doesn't have to walk in there like Don Draper. Being nervous is fine. A lot of people get anxious. But going in there with a sob story isn't going to help his case. Even if they don’t turn him away, they can still use his living situation to lowball his salary.
Yes. A lot of back-end devs would rather chew glass than debug for four browsers, plus mobile devices.