Reputation: 38 Craftsman
- Active Members
- Active Posts:
- 328 (0.21 per day)
- 21-October 11
- Profile Views:
- Last Active:
- Jan 10 2016 04:42 PM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 10 Jan 2016I suspect that the incidence of ageism is about the same everywhere you go. Might be a little higher in the Bay, just because there's a higher percentage of young and stupid companies there. After all, smart companies don't choose to maximize their costs, which is what these companies are doing in locating in some of the most expensive real estate in the world.
My question is, what are you looking for in going there yourself? What's the appeal of Shallow Alto and Deadwood City, or the ruins of San Francisco?
Thats an interesting perspective.
Well I always wanted to live on the West Coast, and I figured that I should go where my skillset is most likely to be appreciated, ya know? Silicon Valley and Seattle have a lot of tech work.
There's also the boredom factor. I've been working on the east coast, and most of the jobs I see are not utilizing even a fraction of what I learned as a CS major. So far, it feels like college was way more challenging than actual work. I really like the guts of computers and programming, and most of the jobs are just "do this business logic, in java/c#/etc."
I guess part of the appeal is that there seems to be more innovation out there. But if I'm just starting my career and I'm ALREADY too old to be out there, then its just not worth it. I guess ill just be bored and not broke. But hopefully I'm wrong.
Posted 14 Feb 2015Yeah thats what I was trying to figure out whether or not my company is doing agile correctly or not.
I need to emphasize this isnt about me, there are hundreds of teams in my company, and every team ive interacted with has the same issues. Every person has mentioned similar issues as I have here, its just theyre less annoyed with it or theyre just used to it.
Posted 14 Feb 20152 weeks is a small sprint. The other issue I see is, QA should not be dictating requirements, only testing that the code does meet them.
A change in requirement should not mean a complete overhaul of code base either.
You might want to grab a book on software development the agile way and see if you may steer them back on track, or at least so you can educate you and your team on proper strategies.
I think the only reason QA is dictating requirements is because we're going through a phase where we're replacing a big chunk of some older code, and theyre throwing in some stuff that is either neglected in the original design discussion/document or is something that people wanted added in the first place.
the most common form of miscommunication is finding out that our interface agreement should handle something like an array of items instead of just one, but we often find that out a day or two before its completed. I dont know if this is related to agile though, as every team ive talked to is always scrambling to get things done.
Posted 14 Feb 2015The thing is, if agile works and isnt about disorganization then Im not convinced the leaders on my team understand it well enough to do what they need to do to make it work from their perspective.
if agile is something different than what Im being told to do, then I feel like I would need to do everything my own way, which on a development team would be bad without agreement.
Im torn, and thats why I came here. Im trying to figure out if agile is really what im experiencing or if they simply dont get it.
Posted 14 Feb 2015the thing about my company is that we get sent to so many seminars, and have so many meetings that it all kind of gets lost. The company is constantly biting off more than it can chew.
In my experience, Agile mostly means theres sprints (in my case, 2 week sprints) where in the first week we do mostly design, then in the second week we do development. Basically calling shenanigans on the original design document, and allowing the developer to update it. Qa can also come in and tell us to make a change, and the problem is that it can really fly in the face of the code base thats already there, this results in the entire team constantly scrambling to get things to match whatever the requirements are that day and when you have to maintain the code its genuinely bad code that was written to get in done before the end of the week, not to be of decent quality.
It may be a buzzword for your company, but it sounds like you don't understand it either. Agile is preferable to most over waterfall. It acknowledges and allows for changes and gives deliverables at known intervals. I don't know what industry you are in, but change in requirements is a big issue in most. That is where agile is most intuitive.
Of course I dont understand it, why else would I make a post like this? Im trying to see if its Agile thats the problem or the way my company is doing it.
When I say calling shenanigans on the original design document, I only mean that in the case where a design document is done. Which doesnt always happen.
- Member Title:
- D.I.C Regular
- 30 years old
- December 1, 1985
- cs, music, politics, philosophy
- Years Programming:
- Programming Languages:
- c++, java, vb.net
NecroWinter hasn't added any friends yet.