15 ms·
Questions to ask a prospective employer during a job interview
- zamkam 4y agoMost of the questions are valid but first, it's unlikely you'll get honest answers and second I think most (maybe all?) employers would cut the interview short after the third or fourth question.
- orev 4y agoThis list smacks of a developer prima donna mentality and if you think most of those rationale explanations are reasonable, you’re more likely to be a liability to the organization and not a team player. Companies have numerous goals, responsibilities, and compliance requirements that you don’t get to ignore or avoid simply because Steve Ballmer chanted about “developers” on stage that time. What would you think about a business person who thought testing was a waste of time because it slows down releases? Or they don’t want to use an issue tracker because it just easier to tell you something in the hallway? Those thing slow them down, so why bother?
- ThrowawayTestr 4y agoIdk, not having admin rights is super annoying.
- beeforpork 4y agoWell, I kinda like it -- less things to care about, more reason to leave at 5. But it's counterproductive for the company, and some experiments a developer may want to quickly do will never be done at all. It kills a lot of creativity. The same holds, of course, for restricting internet access so a dev might never find out whether an interesting looking github tool really is good (for doing productive work!). Also, the company probably wants their products to run on a diverse zoo of machines and OS versions prior to release. So why a company would take away such access on dev machines is a mystery to me -- probably misguided (and futile) attempts to keep in 'control'.
- thfuran 4y ago>less things to care about, more reason to leave at 5. What do you mean?
- mikewhy 4y agoIf it's not in your power to resolve an issue with your machine by the end of the work day, you should feel no pressure to stay late and fix it.
- ornornor 4y agoEven if it’s in my power to fix, why should I do this overtime? Emergencies can happen where you need to stay an hour or two after EOD, but if it’s more than once a year I’m out, personally, local admin permissions or not.
- Xylakant 4y agoI agree, but having them is also a huge liability. I’m always happy to have less privileges because it limits the damage I can accidentally cause. If someone competently manages my machine so that I can do my work without requiring root privileges, that works for me. The actual question I’d be interested in is how do developer convenience and security stance balance against each other, and how are the inevitable conflicts resolved.
- zamalek 4y ago> This list smacks of a developer prima donna mentality The reality is that the market for good developers is so competitive that they could just walk out and find 10 other places with better answers to these questions. > testing was a waste of time because it slows down releases? Not a single question is anagolous to this. Developers want a fast CI process (and testing can be fast, given adequate time allocated to improving CI) because developers are happiest when they are productive. What type of business person would say "no" to employees who only want to be productive? Apparently, the majority. The problem is when micro-management ends up prioritizing tracking work over doing work. It might help to listen to people who are passionate about shipping product, instead of shipping metrics. Although it is a software concept, these questions guage the degree of accidental vs. essential complexity within an org.
- dasil003 4y ago> The reality is that the market for good developers is so competitive that they could just walk out and find 10 other places with better answers to these questions. Sure, but will that be a better place to work? Ultimately there are many failure modes for software engineering teams, and grilling the interviewer with a series of highly-specific workflow questions is not likely to yield much insight. If the team is really as dysfunctional as the author fears, then you're not likely to get an answer that is on the same wavelength as you anyway. You're better off asking things a little higher level and a little more open-ended and then reading between the lines. So for example, instead of: > Does this team or any of the related teams have a person who actively rejects proposals to improve the code base? You could ask: > What are the biggest problems in the code base currently? You can then engage in a dialogue and probe into details organically. This will yield much more fruit than asking a question to which the obvious answer is "no, of course not".
- zamalek 4y agoI definitely agree with your ideas. I aimed only the refute the concept of "developer prima donna." Just like any codebase will forever contain some amount of accidental complexity, so will any org. It's all about whether it is being tackled or embraced. While these questions may not be perfect, accidental overcomplexity can (probably will) make your job miserable.
- deleted 4y ago[deleted]
- oriolid 4y ago> What would you think about a business person who thought testing was a waste of time because it slows down releases? Or they don’t want to use an issue tracker because it just easier to tell you something in the hallway? Massive red flags, take the job if you have to but keep looking and leave as soon as you can. I have actually worked for this business person, and wouldn't recommend the experience.
- closeparen 4y agoIt's a matching process. If you as the employer feel this way, and the candidate feels these things are important, you're not right for each other. That's an appropriate thing to discover in an interview. Personally, I work at an engineering-first company where management takes fairly seriously its task of providing us with a comfortable and productive environment. In this labor market, I wouldn't work somewhere that wanted me to be a "team player" about a shitty computer or micromanage my tasks. There are things to be a team player about, of course, but not the basic tools and structures for even beginning to get work done.
- deleted 4y ago[deleted]
- skhavari 4y agoI find these much better questions to ask a prospective employer during a job interview: https://github.com/viraptor/reverse-interview https://github.com/viraptor/reverse-interview
- deleted 4y ago[deleted]
- throwyawayyyy 4y agoSorry for being a bit snarky here, but I did chortle when "You might also note that Google does give all their developers root access to their own dev machines" (which is true) is followed by things like "Anything under 10 minutes is good" for running the CI pipeline (not true anywhere I've been at Google) or "The steps should be 'do a git clone...'" (also not true at Google). Being slightly less snarky, this is a very prescriptive list that includes questions which, were I asked them as an interviewer, I'd consider red flags. "Does this team or any of the related teams have a person who actively rejects proposals to improve the code base?" is a BAD question to ask in an interview. What answer could an interviewer give? Yes? No? It depends? An example: a junior engineer comes in, says we should rewrite the server in kotlin, starts working on it, then is shot down by a senior engineer. Is the senior engineer "actively rejecting a proposal to improve the code base"? Arguably, yes. Are they wrong to do so? Again, arguable. It depends. Code health is a means to an end, not the end itself...
- majormajor 4y agoAs a non-Googler I'm very curious how much Google lets you check out onto your dev machine. I'm assuming it's less than "oh, yeah, just clone locally that shard of the prod gmail DB to debug that weird thing," but I would love to know how much less. Some of the companies I've worked that let me do the most with my machine were also the strictest about "real" work and data remaining off of personal machines in favor of remote (and non-admin) access to shared resources. Assuming that developers can never be privacy, confidentiality, or other sorts of information security/compliance risks is silly. I think a much better question would be "how are information security and privacy controls implemented" so you know if it meshes with how you want to work and what you think is appropriate for the sorts of data involved. Super-draconian policies for trivial data would be frustrating - but super-lax ones for sensitive customer personal information would be its own different red flag.
- throwyawayyyy 4y ago> I think a much better question would be "how are information security and privacy controls implemented" Agreed, that's a great question to ask.
- Vaslo 4y agoAs someone who doesn’t work in IT, that question about admin rights is huge. I work in finance - is it common to not be given admin right to your pc as a developer? I always assumed you folks did but maybe the lockdown is just as excessive for you.
- c0nsumer 4y agoIt depends on who in IT. IT is big and broad and depending on the company you can have all sorts of folks -- even developers -- who never have an actual need to change admin-level stuff on their own machines. Not everyone in IT is doing systems-level stuff that needs admin rights. Having as few people in a company with admin rights to their machine is very helpful for securing machines. Sure, some will need it, but limiting it to only those with an actual need, really reduces risk.
- isbvhodnvemrwvn 4y agoAnd there's proactive and reactive approach to it as well. With reactive, you elevate your rights when you feel the need to, and your actions are recorded and then maybe reviewed by someone. It's not much more annoying unless you need admin rights frequently (which should not be the case, really). With proactive, you need a ticket and only then, maybe, you get to use admin mode, or someone else is going to do things for you, maybe correctly.
- c0nsumer 4y agoYep, exactly. Reactive is really not that bad, and most software to manage it can also have a preapproved whitelist of actions that automatically get elevated. It definitely takes planning and management and monitoring, but it can be done, and it very much does help Enterprise-type management.
- topkai22 4y agoAt the large tech company I work at, we get two machines- one for day to day dev work and one for sensitive tasks. I get full admin on the day to day dev box and can do all sorts of email and collaboration on it, but I can’t do certain administrative functions or access some types highly sensitive data. The admin box is severely locked down, uses a different identity, but lets me edit shared services and access sensitive data. It can be annoying, but it feels about the right level of paranoia to me.
- robertlagrant 4y ago> Suppose the team needs to start a new web service like a private Gitlab, add new type of CI to the testing pipeline or something similar. Could you explain the exact steps needed to get it fully operational? Please list all people who need to do work to make this happen (including just giving authorization), and time estimates for each individual step. Time estimates for each step? What on earth?
- siliconpotato 4y agoThis question would be a big red flag for me. I don't wanna hire someone who goes and makes all these skunkworks projects under the radar without following standard good practice. The next thing you know, it's part of the infrastructure, and isn't backed up or documented, or contains private keys and nobody else knew about it
- geofft 4y agoI asked two questions the last time I interviewed which are wholly unrelated to anything on this list, and they found me a place I was happy enough with that I haven't looked again in 5+ years. To engineers - how do you feel about management / the practice of management at this company, especially compared to other places you've worked? I was looking for an answer that indicated that management wasn't just where they put engineers who wanted a promotion, and also that the company's processes realized that management was a skill you could be good or bad at just like engineering. To managers - how is diversity on your team? The answer was universally some variant of "it could be better," but I got a lot of mileage from seeing whether it was a thing they were defensive about and whether they thought they actually could concretely make progress. All the technical stuff follows from whether the company has reliably competent managers who believe both that they ought to make things better and that they are realistically able to. There are other specific questions you can ask to answer it; I just happened to use these two (and I certainly have no idea if they're the best, but they did work). Every bad technical answer can be fixed by people who want to fix it; at the same time, every good technical answer can go bad without people who care to keep things fixed.
- webel0 4y agoI think that some of these questions are quite important. However, I think that all of them could be interpreted as “missing the forest for the trees” sort of questions. Therefore, I don’t tend to ask them in interviews. If you do ask these questions, at what point in the interview process (or within a given interview) do you ask them?
- codingdave 4y agoThis list is asking about specific symptoms of larger problems about which they may be concerned. To which I'd just recommend - don't be coy. If you want to know what the experience is like being a developer there, just ask directly -- Don't symptom-check. If I were asked these questions, I'd cut them off and ask them to tell me what they are afraid of - we all have our own fear and anxieties about starting in new environments, but I'm far more likely to hire someone who can open a dialogue about their concerns than someone who just picks aspects of past experiences and grills me about them. Not only will the interview get more directly to the point, such a conversation will show they are able to talk through whatever problems may arise in the future.
- ok_dad 4y agoAgree, I would just replace all this with, “can you talk about the tech stack, developer experience, etc?” and then explain what I’m looking for in more detail but without the pointed questions or snark. Also, this is a “final interview” question, like the questions you ask once you know you have the nod and are now just trying to ensure it’s a good match.
- hx2a 4y agoI always ask a direct question about ethics. Something like, "tell me about the kinds of ethical problems that this team is faced with and how you handle them." Good answers involve speaking up about the problem right away & not try to hide anything and being transparent with relevant entities. Bad answers are things like "there haven't been any ethical problems," because that most likely signals that ethical problems are being ignored or overlooked.
- sfg 4y agoWhat kinds of ethical problems do teams suffer in your experience?
- aaronbrethorst 4y agoMy go to is always "What are your most and least favorite parts about working here?"
- t8sr 4y agoAs others point out, some of these are quite naive. (E.g. at many companies you have a large monorepo, so the "git clone" comment is silly, etc.) What really gets me, though, is the tone. There's a nice way to probe for organizational problems like too much bureaucracy without coming across like a jerk. If someone showed this lack of self-awareness and basic social skills in an interview, I can promise they'd be a strong no hire.
- civilized 4y agoI agree that the way the answers are evaluated is too narrow and simplistic. That said, > coming across like a jerk... lack of self-awareness and basic social skills I see things very similarly, but from the other side of the table. If an organization is uncomfortable with me asking direct-but-polite questions about potentially negative aspects of working there, and asking such questions gets me labeled as a jerk, that organization is too culturally dysfunctional for me to work for.
- t8sr 4y agoThe issue is not with being direct, but with instructing the interviewer to "please list the exact steps and time estimates for each." It smacks of self-importance and arrogance, and the way it's phrased strongly suggests the author thinks they are the smartest and always right. By the way, I looked this guy up, and his experience looks like it's extremely limited to basically a couple of SMBs and some consulting. I have no idea where he gets the confidence to comment on the industry, having basically never worked in it.
- yibg 4y agoI've had this type of person on my team before. Reading through the questions and rationales I can just picture that person asking the same questions and expecting the same answers. Technically capable and a pain to work with. Everything was their way only, no compromises. If you don't agree, then you're just too dumb or inexperienced. The cost to the rest of the team is simply too high.
- 4y ago
- chopete3 4y agoHeres where you should work based on the favorable/simple answers expected on those 10 questions. 8-10 : Start up 5-7 : Small Company 3-4 : Medium ($5B+) 1-2 : Large ($25B+) 0 : Very Large Otherwise you are interviewing at a wrong company. --- 1. Do developers in your organization have full admin rights on their own computer? 2. Are developers free to choose and install the operating system on their development machines? 3. How long does it take to run the CI for new merge requests? 4. Could you explain the process one needs to follow to get that fixed and how long does it approximately take? 4. Could you explain the procedure needed to get a new USB? 5. Could you explain the exact steps needed to get the code built? 6. Can you build the code and run tests on the local machine as if it was a standard desktop application? 7. Does this team or any of the related teams have a person who actively rejects proposals to improve the code base? 8. How many different IT support organizations do you have. Where are they physically located? 9. Could you explain the exact steps needed to get it fully operational? 10. Do you have a mandatory web proxy that everyone must use and enumerate all pieces of security and tracking software you have installed on employees' computers. </sarcasm>
- dmitrygr 4y agoWhat does “getting a new Universal Serial Bus” even mean?
- schwartzworld 4y agoIf you read the article, you would know he left out the word "hub"
- prmoustache 4y agoThat is such a strange example. Whenever you get a laptop you usually get a docking station which is a hub. Desktops have plenty of ports. OP should have mentionned something like a real world example instead of an example from the late 90's: a ram upgrade, something to improve ergonomics (vertical mouse, special keyboard, chair/desk) or the purchase of a new software do get the job done more effectively. A developer is more likely to wish a 5-10$ per month subscription to a software/service than a specific piece of hardware.
- lmeyerov 4y agoFree drinks and fast CI don't solve a broken company, product, & team. The former you can always fix on your own, but not the latter Two+ years of your life have much more important questions than staging servers, such as: * "Is the company profitably growing at > 50% YoY" <- is it winning? * "What will it take for the next 100X in growth?" <- will it keep winning? * "What happens if the next fundraising round doesn't land?" <- is it a wobbling VC trick? * "For this job, what will I own, and what skills do I need to be successful at that?" <- will you succeed? * "What percent of the team has been there more than 1yr, and more than 2yrs? Why do people stay vs leave?" <- is it a healthy environment?
- rroot 4y agoYou can't fix a broken CI in a broken company, product, & team. But I get what you're saying.
- lmeyerov 4y agoThe good news is you can totally fix a broken CI in a working company, product, & team, so those are the more important things to ask about
- oriolid 4y ago> "Is the company profitably growing at > 50% YoY" <- is it winning? > "What will it take for the next 100X in growth?" <- will it keep winning? How do these exactly affect a software developer? Even if the company is going to grow 100x, you can still be laid off and it's highly unlikely you're ever going to have any part of the money.
- lmeyerov 4y agoif the company keeps growing revenue ahead of hiring, they'll care more about retaining good people than losing them so they can keep growing. in this scenario, hiring a build engineer to fix CI becomes a reasonable thing to do: there's money, it's not a hard problem, and makes everyone else happier & more productive. if the company is setting more and more money on fire, it's a dead company walking. you're hoping for an acquisition or exit before the house of cards collapses. in this scenario, instead of repurposing current hires to getting to profitability, a company that keeps hiring is compounding its risk. each new hire eats the runway that much faster and makes everyone's job that much more precarious. folks are totally free to ignore whether their company is economically viable, and prioritize something like free drinks & CI b/c that makes their week better. but then they shouldn't be surprised when multiple rounds of layoffs happen every few months. Note: it's totally fine if a company is losing money. but then the question is "how many more years of runway are there with the hiring plan?", and if the answer is 6-12mo... well. A scramble will start where stuff like build times won't matter.
- gregmac 4y agoThings like CI times and build process strike me as opportunities. If they're bad, there's a spot you can contribute and make it better. A core piece of that is figuring out if they're open to spending times on improvements like these, and figuring out why they haven't: recognition of a problem? Expertise to fix it? Constant time crunch? No prioritization input from dev team? A question might be something along the lines of "As a team would you spend 3x once to save x time for every subsequent sprint/release after that? What's the last example of where you did this?" This applies to CI/build process, unit testing, other automated testing, deployments, etc.
- Kwpolska 4y ago> Too slow of a CI means that instead of submitting small, isolated commits people start aggregating many changes into a small number of mammoth commits because it is the only way to get things done. I don’t understand the point here. 1. `git commit` and `git push` are two separate steps, you can commit often, but you can push once every few hours, assuming your computer won’t catch fire in the meantime. 2. If your CI builds every single commit pushed to a branch (instead of just building at every push), that’s a very weird CI config. 3. Where is the slowdown? Is it because your commit is waiting in a queue behind other commits?
- kaoD 4y agoI think they mean isolated PRs. Been there, done that.
- roflyear 4y agoMeaning, PRs are generally bad to require to do a build?
- bobthepanda 4y agoIn my experience it is a good idea to try and keep code reviews and pull requests short and sweet. It’s much easier to review small concise code than mega commits, it’s much easier to catch mistakes in them, and being set up to iterate small changes quickly tends to result in faster velocity (as opposed to people trying to avoid reviewing the mammoth, scary block of code that might take a half hour of reading to just read it, rather than review it.)
- rroot 4y agoThe fundamental problem with slow CI is developer's own context switch. If CI notifies me an hour later that my changes fail CI, I have might have to abandon my flow, sort out the failure and commit/push again. Then get back into whatever I was doing. This can be very taxing for developer's time and mental well being.
- exabrial 4y ago“Is this Position a backfill for someone that left? If so, why did they leave?”
- nojito 4y agoThis post should be exhibit A on why software engineering/dev managers get paid so well.
- neilv 4y agoSome of these questions are phrased as expensive compliance interrogations... as if they're coming from the kind of bureaucracy and authoritarianism that the questioning seeks to avoid.
- JustLurking2022 4y agoFull admin is a non-starter for regulatory reasons in some industries (e.g. finance). Also, at Google, developer laptops are essentially untrusted - all code lives in the monorepo target than being cloned locally, so there's nothing of much value on the device.
- P5fRxh5kUvp2th 4y agoThat's not true, what's a non-starter is giving developers direct access to production data and production systems. You can do that without removing LOCAL admin rights.
- JustLurking2022 4y agoNope - even local admin is generally a non-starter as it can serve as a gateway to further attacks (e.g. install a keylogger, wait for a coworker to need to check email and offer to let them borrow your laptop, run pen test tools from with the network to probe for weaknesses). Banks actually have to prove to their regulators that unauthorized software can't be installed.
- deleted 4y ago[deleted]
- twodave 4y agoI have had to answer a lot of these questions before, but not for a potential hire. These are the kinds of questions auditors tend to ask during due diligence of a software org (especially the “give me time estimates” type questions). Usually in an audit type setting these answers aren’t readily available because there are limitless ways to ask these questions and supporting data to request. An organization isn’t typically going to spend that level of effort to satisfy one obviously pretentious candidate.
- nickdothutton 4y ago1. What happens in a day/week in the life of this job? Generally interviewers cant think fast enough to lie convincingly in answer to this question, by giving you a rose-tinted fantasy. Here is where you hear that the _real_ duties dont match the job description they are handing out. 2. What did the last guy die of? Similarly, throws interviewers (assuming this is not a newly created role). They will find it hard to deflect or lie convincingly under pressure. It doesn't matter what they say (to some extent) what matters is how they handle the question. Keep it breezy, smile, don’t be afraid of silence while they sweat.
- greybox 4y agoA lot of these are fine for web development jobs, but for other kinds of software EG AAA Games, Real Time, Control / Monitoring software with specific deployment environments, Payments processing etc.. these won't be applicable. I am someone who's worked in a few of these industries over the years, let me list a few examples of the kind of places where the answers you get to these questions won't indicate goodness or badness of the employer. "Do developers in your organization have full admin rights on their own computer?" For security critical applications, often no. For obvious reasons. For payments software, the company may be compliance mandated to not give you full permissions either. "Are developers free to choose and install the operating system?" For games. Especially PC games, no. If you're developing for windows, you'll develop on windows, often with VC++. (maybe if you're using Unity, you're CI pipeline will produce builds for you) "How long does it take to run the CI for new merge requests?" In game development, it's not unheard of for a full release build to take an entire day. Games are complicated, often requiring a lot of libraries that are cached, but still need to be downloaded onto a fresh instance where a build will take place. This takes a long long time. "How many different IT support organizations do you have. Where are they physically located?" Mastercard has its IT support organization located in the US. Even for it's UK offices. Tickets still get solved quickly even at awkward times in the morning for GMT employees. In short, most of these are only applicable to web development outfits. There's nothing wrong with that, web dev jobs are the majority of jobs. But just be aware that this is baised towards that.
- viraptor 4y agoIf someone clicked looking for a longer / less opinionated list, I'm collecting those at https://github.com/viraptor/reverse-interview https://github.com/viraptor/reverse-interview
- alasdair_ 4y agoReally large tech companies with truly massive codebases (especially monorepos) often need custom tooling to build things, so “ Being able to build the project on your own machine is pretty much mandatory because if you can't build locally then e.g. IDE autocompletions does not work because there is no working compile_commands.json.” isn’t always true. Facebook, for example, uses a highly custom version of VS Code (was: atom) that talks to a server for each developer. The devbox contains the repo and is mostly prebuilt because trying to check out and compile a codebase that is easily 20 times bigger than a linux distro just isn’t feasible on a laptop. So long as there is a well resourced dev productivity team in the company, whatever they use for a huge codebase is likely fine.
- alasdair_ 4y ago> Any other answer means that support requests take forever to get done and are a direct and massive drain on your productivity. Timezones matter more than countries. If I am in London and support is in Dublin, this is usually better than being in NYC with support in SF.
- lucb1e 4y agoI think most of these questions are basically asking the same thing: how bureaucratic is this organisation? Which is not something you can ask directly, so these proxy questions are a good idea. For example, I laugh at the crap my SO has to go through at their (larger) employer for simple things. The "fixing a typo in a log file" question is especially apt: it's essentially impossible for my SO because they're only supposed to work with the software as provided, despite being programmers themselves (they do scripting to add functionality to the software using a custom language, to adapt to customer's needs). My SO would have to answer something involving navigating multiple levels of management in another country. For my own employer, I would answer "the process is git clone, git commit, git push. You can ask someone for feedback on your typo fix if you want I guess?" I'd never think of asking such a simple but effective question. But then there is "Does this team or any of the related teams have a person who actively rejects proposals to improve the code base?" Huh? What do you expect anyone to answer to this, "oh yes we have Steve, he's a real asshole and continuously rejects the best of ideas for no apparent reason"? The author even lists it as "Out of all the questions in this list, this one is the most crucial." I can understand that the author had a bad experience having to work with someone like that, but the odds of getting a real answer here are negligible, especially compared to the odds of the interviewer thinking worse of you for asking to throw someone under the bus before you're even hired. Would not recommend asking this 'most crucial' of questions.
- stormbrew 4y agoAfter working at a few startups and going through some failed ones that went down in unpleasant ways I started asking startup interviewers, when interviewed by a founder or someone else with a high stake in it: "how would you deal with your startup failing". I will never forget the time one of them (the founder of the company) told me he would commit suicide. Let's just say that neither of us wanted to continue that interview series any further.
- ornornor 4y ago> I will never forget the time one of them (the founder of the company) told me he would commit suicide. Wow
- quickthrower2 4y agoThese feel like 'snapshotty' questions, whereas in my experience you want to know things are moving in the right direction. I.e. a company could be doing the right things, but just got taken over and those right things are slowly degrading. Or doing a load of wrong things, but working really hard to change that. It is very hard to tell what it is like working for a company from an interview. And things change, who you speak to there might be fired/leave in 3 months and it's a different scenario. I've seen this. That said real red flags in my opinion: * The company is about to be taken over - generally that is gonna be bad for a software developer or any non-lawyer kind of role really. * The company is struggling with cashflow * The company has fired a lot of people recently. * Unclear job spec. * Disorganised or overly burdensome interview process. * Strong bad gut feel about the people. * Crappy office - for your definition of crap, (even if you are the WFH...) * Secretive companies - avoid the trade-secrets obsessed "need to know basis" kind of affairs. * Sexism, etc.
- closeparen 4y agoA twenty-two-year-old version of this, the Joel Test: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s.... 1. Do you use source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing? It's interesting to reflect on how things have changed. Source control is not even a question anymore. Quiet working conditions, not a chance unless remote. Schedule? Spec? Testers? Never seen 'em. Do new candidates write code during interviews? Oh boy, do they ever.
- netfortius 4y agoJust the first question gives me shivers. The end user device is an entry point into any organization, of extremely high risk. PAM solutions, with proper logging and time bound limits to what needs to be done as root, exist and should be leveraged. Not everybody is Google, for better or worse.
- a-dub 4y agoi'd like to read the code our team is responsible for, can you give me a list of pointers to all of it?
- redditor98654 4y ago> Suppose the team needs to start a new web service like a private Gitlab, add new type of CI to the testing pipeline or something similar. Could you explain the exact steps needed to get it fully operational? What does this question even mean? Like implementing a new CI service? Or creating a new ci/cd piepeline for the new application?