greptilian logo

IRC log for #sourcefu, 2015-12-08

http://sourcefu.com

| Channels | #sourcefu index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
12:57 pdurbin_m joined #sourcefu
12:57 pdurbin_m Technical debt isn?t technical | ample code: https://einarwh.wordpress.com/2015/12/05/technical-debt-isnt-technical/
14:15 dotplus I disagree, technical debt *is* technical and yet it still "stems from project deadlines" and "has probably been written in a hurry because the project leader said so". Almost always IME, technical debt arises because of both a) the people doing the tech work haven't been allowed the time to investigate appropriate solutions to the problems and b) the project team as a whole (tech & non-tech if there are any) haven't been allowed the time to ...
14:15 dotplus ... determine what the goals are
14:18 pdurbin dotplus: so you agree it's a people problem
14:46 dotplus yes, but I maintain the more orthodox idea that we end often up with crappy (poorly scoring in performance/suitability/sec​urity/maintainability/etc) "solutions" usually because the project leader/upper mgmt imposes (accepts?) unworkable time constraints. Sometimes, the tech-folk impose unworkable time constraints upon themselves perhaps (because we/they're conditioned to it?)
14:50 dotplus the other main cause in my mind is changing goals. If you change what you're trying to achieve too rapidly, you end up with something that looks a lot like technical debt as well. If you design/build a project that is intended to fulfill a set of requirements, Z, the suitability of the results of that project to fulfill the set of requirements Z' has an *upper* bound that is dependent on the delta between Z and Z'
15:04 pdurbin dotplus: you sound like the voice of experience :)
19:59 aditsu_ joined #sourcefu

| Channels | #sourcefu index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

http://sourcefu.com