Live data from Hacker News

What sucks about your company's dev environment/philosophies?

news.ycombinator.com

1–10 of 15 posts

What sucks about your company's dev environment/philosophies?

#1
Our company, Kareer.me, helps companies showcase their culture, workspace, team, opportunities, and more. We're looking to add something new just for developers.

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?

Re: What sucks about your company's dev environment/philosophies?

#4
Code Quality (How horrible is your code?), Will my attempt to push initiatives be welcomed or rejected?, Frameworks in Use, Architecture, use of OOP / OOD, Scaling considerations, Direction of the company (This can influence the way we build things, Some stake holders do not see this, through thier push to iterate), will it be fun to work there? and is there Redbull?

Re: What sucks about your company's dev environment/philosophies?

#7
post #3

How important testing is to them. Many "agile" companies don't actually incorporate testing in any meaningful way.

Awesome input. I think a lot of companies overlook testing as a valuable part of their overall development plan. Most just want product pushed out the door. I'm curious as to how we might be able to get an objective measure of this from the company. Perhaps asking for specific methodology, tools, etc?

Re: What sucks about your company's dev environment/philosophies?

#8
post #5

- Deployment Process - Project Management (Agile?) - Testing (Process, Tools) - Code Reviews - Current Libraries

Thanks! I wonder if companies would be willing to share their use of APIs as well. A few of our developers are nuts for API integration. Libraries might be a sensitive subject for companies to display, but would definitely be cool to know.

Re: What sucks about your company's dev environment/philosophies?

#10
- Open Source Stance

- 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?

Post reply on HN