Many of us have been duped into working at companies that are painful to write code for.
What things would you like to know about a company's development environment/philosophies before even considering a job?
1–10 of 15 posts
Many of us have been duped into working at companies that are painful to write code for.
What things would you like to know about a company's development environment/philosophies before even considering a job?
- Iterations: how often do they ship/what does QA cycle look like
- Pair Programming/Code Review: how does the company keep everyone in the loop?
- Project Management (Agile?)
- Testing (Process, Tools)
- Code Reviews
- Current Libraries
How important testing is to them. Many "agile" companies don't actually incorporate testing in any meaningful way.
- Deployment Process - Project Management (Agile?) - Testing (Process, Tools) - Code Reviews - Current Libraries
- Links to public software contributions - API Documentation
- Delivery/Deployment methodology (shrink wrap, separate releng process, continuous delivery)
- Who is on call for production, process or code issues?
- What software code metrics are tracked/graphed?
- What process metrics are tracked/graphed?
- What is the companies take on security?
- How are tasks assigned to engineers?
- Do you have a separate tools/devops/process team?
- Is there a separate project management department?
- Does the company contribute to meetups, local communities?
- Who goes to conferences, career training sessions?
- Is there internet access at the office?
- What is the office setup like? cubes, desks, offices? standing desks?
- What are the office amenities? snacks, dinner, drinks, showers, gym, yoga, surf, video games?