4 ms·
Mine are issues and yours are details. I certainly drilled down into more detail, but I'm not convinced that there's as much of a dichotomy there as you may se
by mindcrime 14y ago
Mine are issues and yours are details.
I certainly drilled down into more detail, but I'm not convinced that there's as much of a dichotomy there as you may see. Nonetheless, I understand what you're saying, but I'd counter that "details matter" and that different details matter more to some people than others. Also, I certainly don't intend that list to be seen as an alternative to your list, I mean it to be additive (from my perspective anyway).
2. Mine are about them, yours are about you.
To some extent, yes. But asking whether or not a company has, and understands, a reasonable software development methodology, or whether or not they have a culture that foster employee engagement and empowerment, is very much about them.
Mine show interest in the big picture; yours could easily paint you as a demanding nit-picker (whether you are or not).
Yes, I will say that I chose to drill down to a deeper level of detail. Basically I'm working backwards from the bad stuff I've actually seen in my career, and putting it in terms of "these things suck, I don't want to be in this environment, so convince me that this won't be the case here".
I just don't think I ever would (or ever have) discussed them with a prospective employer.
I mostly didn't in the past myself. But that was out of naivety, or fear. Either I was naive about the existence of the issue, or I felt like "I need this job too bad to be too demanding." As I've gotten older and more comfortable in my skin, and more confident in the value I can provide, I don't worry about that as much. I can walk away from a job offer, knowing there will be others.
And even if I didn't discuss these issues with potential employers, they have certainly been factors. I was invited to an interview with $BIGCORP once, went in, did the first round of interviews, and then got a phone call asking me to come back in. I politely declined. Why? I saw that all of their developers were in a big cattle shed full of low-walled cubicles - an environment that I consider "optimized for maximum distractions" and fairly inhumane. I decided they weren't a good fit for me based on that factor alone. Doesn't mean they were wrong and I was write, or vice versa, it just wasn't a fit that would have worked.
- w-ll 14y agoYou lost me in caring about what the office looked like and what hardware you got. Who cares? I don't! I can hack on whatever; whenever; with whatever! PERIOD! edw519's questions provoke conversation, where yours provoke sales talk.
- reledi 14y ago> I can hack on whatever; whenever; with whatever! So can everyone else, it's just not enjoyable for some people if they're stuck in a shitty office space with shitty hardware. Who wants to work at a place where they don't enjoy working?
- lsc 14y agoMore to the point, if you are paying someone six figures to write code, trying to save a few hundred bucks a year by giving them hardware they don't like is just plain stupid. I mean, as an employee, I don't care that much 'cause i'll bring in my own stuff if you don't provide me with hardware I like... but my experience? employers get itchy if you do this with more than, say, a keyboard. Most places don't want me supplying my own workstation/laptop, which is fine, so long as they buy me reasonable hardware to work on. I'm reminded of one place I contracted at where they gave me a P3 windows box (this was in the mid-oughts) - I mean, they were paying me like $70/hr. They wouldn't let me bring my own hardware, either. I go to put linux on the thing, you know, make it usable; and the IT guy finds out (well, I ask him for a blank DVD) Anyhow, he goes all 'Mordak' on me and tells me that I should just sit there in front of my useless computer and "think about what I did" or something like that. I mean, I understand that some places want me to use their hardware, and let their IT people handle it... which is fine, if they are wiling to do a competent job of it.
- greenyoda 14y ago"More to the point, if you are paying someone six figures to write code, trying to save a few hundred bucks a year by giving them hardware they don't like is just plain stupid." And if the company is stupid about something as fundamental as creating a productive working environment, you can be sure they'll be stupid about lots of other things as well.
- MojoJolo 14y agoI disagree. I once tried coding an iOS app in a Windows 7 laptop using a hacked VMWare to run Mac OS X. And I will not do it again. The amount of time beach ball of death shows is greater than the time I saw the normal cursor. It's so damn hard! So if you want me to code something for you, supply me the required hardware for it. And no, you can't hack on whatever hardware.