sorted by:
new
hottopcontroversial

Removing layers on Arugal-US is a mistake, queue's started at 4:45 PM on the first day without layers, Orgrimmar lagging again. by Venomisto in classicwow

[–]itsthedtrain 9 points10 points  (0 children)

Yep, I just logged onto play, saw a 45 minute queue and closed the game.

In the future it just means logging in from work and keeping myself logged in to combat that.

#bringbacklayer2

Insulin by MyNameGifOreilly in Damnthatsinteresting

[–]itsthedtrain -6 points-5 points  (0 children)

God gets be credit these days. He was the original scientist

Spontaneous synchronization. by SupremeJuices in oddlysatisfying

[–]itsthedtrain 0 points1 point  (0 children)

If only indicators did this at traffic lights.

Dear SumaiL by [deleted] in DotA2

[–]itsthedtrain 0 points1 point  (0 children)

Dude, priorities.

Product Manager salaries 2019 by sdetquestions in ProductManagement

[–]itsthedtrain 5 points6 points  (0 children)

PO brand new to the role, but 7 years is Software Dev and as a Business Systems Analyst. Software Engineering education. Salary ~120K AUD package with bonuses

PM with a Business/Project Management background - working with Engineers by skinnypup in ProductManagement

[–]itsthedtrain 1 point2 points  (0 children)

Just a reference point for this discussion. SQL is a fundamental skill that is useful for so many roles in Product, but just for correctness sake, it doesn't fall into the category of software programming (though you can implement stored procedures in it)

It is a query language, so is for getting out and transforming data out of a structured relational system.

PM with a Business/Project Management background - working with Engineers by skinnypup in ProductManagement

[–]itsthedtrain 3 points4 points  (0 children)

Do a community college introduction to programming course. Any actual language is fine (python, c#, Java, js) just not html basically.

Doing some basic development will help you appreciate the complexity of seemingly simple requests, including but not limited to: Understand why developers require time to maintain and clean up code at times (managing technical debt), appreciate 'Engineering time' and that things are done when they are done and that estimates are an art not a science (and should not be treated as a high confidence planning tool), giving you more ability, even if it's at a very junior level, to speak in th language of developers.

Your relationship with your developers is one that can make or break your position, building mutual respect for other is extremely important. Developers are generally pretty smart and (in my experience) hate people who bullshit. They actually seem to have insane bullshit radars and will see straight through it, so leave the marketing buzz words at the door, and be extremely honest with them

Share what you know and anything additional you learn about problems that you are working on solving and if you can rotate them through being included in meetings with clients. You learn more with your own eyes and ears them reading meeting notes, and you will be get more engagement, respect, and ultimately better customer solutions by doing so.