Jan 30, 2020 12:33
@Mohammad_Hosseini you mentioned in another comment that you heard someone talking about bankruptcy. "We'll pay you in 2-3 months" sounds a lot like it really means "we'll pay you if we don't go bankrupt."
 

 Discussion between Warbo and Ewan

Imported from a comment discussion on softwareengineering.stac...
Jun 1, 2018 08:16
How do I get a job working with Warbo and Mr. Mindor?
 
Jan 11, 2018 03:38
This is a software engineering answer rather than a workplace answer but: it sounds like you are overengineering. Design patterns are tools that you use when you actually need them to produce the desired behaviour. This is also usually passive and the design pattern is just a handy descriptive label - you write the code that does the thing you need and, hey, look, it's a factory. If it's not happening organically, it's probably unnecessary. Using a design pattern should make your code simpler, not more complex.
 
Oct 4, 2017 21:57
Eesh, your boss has an attitude problem and your company has a pretty hostile attitude towards its staff. I'd be questioning my position here. Also, not sure why contacting HR is such a big deal - understanding and communicating company policy is a big part of what they exist for.
4
 
Aug 9, 2017 21:11
@2rs2ts I agree - I think it's a sad state of affairs when simple refactoring is inhibited by downstream gates and we accept that that is a normal and healthy process. I think there is a BIG culture divide in this conversation. The grass really is greener.
 
Jun 16, 2017 11:44
Perhaps, but so is being more attractive, taller, or any other number of arbitrary things that get you in the door. - Would have thought being shorter would generally be more helpful on that front.
 
Jun 6, 2017 20:32
Normally I would agree with this but in the context of what is essentially a team stand-up for a team that all sits next to each other I don't think it's particularly unreasonable to expect a more informal attitude towards starting the meeting (i.e. everyone knows roughly when the meeting is and the first person to stand up shouts everyone round). That said there are better ways of promoting this than challenging your boss - e.g. start getting up and shouting everyone round at 1-minute-to-stand-up and letting that culture embed itself.
 
May 12, 2017 19:50
If you're replacing a software component the only thing you should be "copying" from the original is the behaviour with respect to its integration points - beyond that, just code naturally. Most software design is (rightly) a product of the evolutionary process of the software - if you're starting again from a different starting point, it's only natural that the resulting design will be different.
 
May 11, 2017 12:11
This is a real-life funeral and a role-play software job? If your supervisor is your academic supervisor then the context of the role-play is irrelevant here - you're absent as a student, not an employee. If your supervisor is another student trying to maintain "character" while you're experiencing real-life issues, he is way out of line.
2
 
Feb 8, 2017 13:20
The phrase "cloud cuckoo land" comes to mind.
Feb 8, 2017 13:20
This smells like the answer of someone who doesn't really understand software (and - based on the comments - is drawing erroneous comparisons with other technical fields). And whose employees recognise this and are working around the problem by essentially lying about producing no bugs. "There are none if you define and understand the operating parameters completely" - this is essentially an impossible scenario in nearly all software environments.
 
Nov 23, 2016 17:04
Comments lie. Code doesn't.
 
Feb 4, 2015 13:01
if (environment == Environment.Production) EraseDatabase(); Console.Write(projectManager.GetsItYet);