|
Pollyanna posted:We got $1 lottery tickets as Christmas presents. https://www.youtube.com/watch?v=TQXuazYI_YU
|
#
?
Dec 14, 2016 22:01
|
|
|
|
| # ? May 9, 2024 22:44 |
|
|
We got jelly of the month clubbed with a party no one wanted. Drank more than I have in 20 years in recompense. 
|
|
#
?
Dec 15, 2016 01:22
|
|
|
Pollyanna posted:We got $1 lottery tickets as Christmas presents. I think that beats my "best" bonus stories, both from the same company. 1. Everyone got a $100 bill in a Christmas card. The card said "note: this is considered taxable income and a corresponding amount will be withheld from your next paycheck". It's true, but really, that's what you print in the card? Merry loving Christmas lol. The executives were notoriously insensitive and out of touch, so this was par for the course. 2. Topping that, next year everyone got a pair of tickets to the local minor league hockey team. Face value was like $20 total. Also it cost the company nothing because we advertised a ton with the team and an assload of tickets was part of the Gold Sponsor Tier or whatever. (We did also get access to a fancy suite with free food and booze a couple times a year which was fun) Both of those were super cynical. But at least they had guaranteed tangible value. Docjowles fucked around with this message at 02:01 on Dec 15, 2016 |
|
#
?
Dec 15, 2016 01:58
|
|
|
Pollyanna posted:backlog grooming My Rhythmic Crotch fucked around with this message at 05:46 on Dec 15, 2016 |
|
#
?
Dec 15, 2016 05:42
|
|
|
My Rhythmic Crotch posted:I just want to say "STOP" every time I hear new lingo like this. Stop creating 20 dollar words for 50 cent concepts. (I know you didn't create it yourself, just sayin') I wouldn't consider it new lingo. It's been part of agile sprint lingo as long as I've been aware of the system. And honestly the concept needs a term. It's not something you would do in some other methodologies.
|
|
#
?
Dec 15, 2016 08:12
|
|
|
Hughlander posted:I wouldn't consider it new lingo. It's been part of agile sprint lingo as long as I've been aware of the system. And honestly the concept needs a term. It's not something you would do in some other methodologies. What's wrong with calling it 'reorganization'? Hell, you could just call it refactoring and I think most people in this industry would just get it.
|
|
#
?
Dec 15, 2016 15:54
|
|
|
Munkeymon posted:What's wrong with calling it 'reorganization'? Hell, you could just call it refactoring and I think most people in this industry would just get it.
|
|
#
?
Dec 15, 2016 16:15
|
|
|
As was posted on the previous page, it's called refinement now.
|
|
#
?
Dec 15, 2016 16:25
|
|
|
Vulture Culture posted:The first one is inaccurate and the second is completely the wrong concept. Not to me on both counts 
|
|
#
?
Dec 15, 2016 17:09
|
|
|
Munkeymon posted:Not to me on both counts Yes, that's why it's being mentioned. Those terms don't fit at all.
|
|
#
?
Dec 15, 2016 17:13
|
|
|
e: nevermind - semantic arguments over non-formal languages are super pointless
|
|
#
?
Dec 15, 2016 17:32
|
|
|
I wouldn't have the slightest clue what you meant if you told me we were going to refactor the backlog.
|
|
#
?
Dec 15, 2016 19:21
|
|
|
you guys are talking about prioritizing tasks to current goals, up to and including dropping tasks; right? 
|
|
#
?
Dec 15, 2016 20:01
|
|
|
It looks like as a result of our codeathon (more of a talkathon really), our current stories/direction are gonna change completely, so the point might even be moot. I randomly got drafted as our team's "team leader" and tried to coach another lead through exposing a React component as a .js served over a CDN or something, and completely failed because it cannot be done without actually pulling in a React component as an NPM package. It's not a plug-and-play solution and I'm pretty sure I am not good at my job at all gently caress gently caress gently caress.
|
|
#
?
Dec 15, 2016 21:26
|
|
|
Javascript is really stupid and nobody is good at it
|
|
#
?
Dec 15, 2016 21:29
|
|
|
Just kludge something together; chances are nobody's going to give a poo poo until a new dev comes in who will want to rewrite it in the newest framework of the month anyway. Only half joking.
|
|
#
?
Dec 16, 2016 00:22
|
|
|
Pollyanna posted:
Random or dilbert principal?
|
|
#
?
Dec 16, 2016 01:48
|
|
|
Che Delilas posted:Just kludge something together; chances are nobody's going to give a poo poo until a new dev comes in who will want to rewrite it in the newest framework of the month anyway. We aren't using a framework, we're basically taking a microservices approach and dispatching to different web views based on nginx url matching so each team can develop completely independently, and so we can all use different tech that allows us to turn the header, footer, content, calculators, etc. into drop-in components that we can include in pages written through a CMS. Wait, what do you mean that's not what microservices are???? Hughlander posted:Random or dilbert principal? Honestly? Probably.
|
|
#
?
Dec 16, 2016 14:02
|
|
|
We decided on a team name and a team quote. We are Tools, and we Get poo poo Done.
|
|
#
?
Dec 16, 2016 15:09
|
|
|
Pollyanna posted:We aren't using a framework, we're basically taking a microservices approach and dispatching to different web views based on nginx url matching so each team can develop completely independently, and so we can all use different tech that allows us to turn the header, footer, content, calculators, etc. into drop-in components that we can include in pages written through a CMS. find a new job. that sounds horrible
|
|
#
?
Dec 16, 2016 15:19
|
|
|
the talent deficit posted:find a new job. that sounds horrible Yeah no it's a joke. We haven't actually proven we can do it, just that we like the vague idea of it. All of our time spent yesterday was trying to find a piece of tech to work with and we were unable to settle on something. I was the only person that achieved anything of use. Within our work cell, anyway.
|
|
#
?
Dec 16, 2016 15:29
|
|
|
Pollyanna posted:We aren't using a framework, we're basically taking a microservices approach and dispatching to different web views based on nginx url matching so each team can develop completely independently, and so we can all use different tech that allows us to turn the header, footer, content, calculators, etc. into drop-in components that we can include in pages written through a CMS. I'm imagining that one team is building on Jquery, another is using AngularJS, another is using React, and another is using Jquery, but has a completely different way of using it than the first one and so on. Fake edit: Misread the next post, this hasn't happened. Yet.
|
|
#
?
Dec 16, 2016 15:38
|
|
|
Pollyanna posted:We are Tools, and we Get poo poo On By Management.
|
|
#
?
Dec 16, 2016 15:52
|
|
|
HardDiskD posted:I'm imagining that one team is building on Jquery, another is using AngularJS, another is using React, and another is using Jquery, but has a completely different way of using it than the first one and so on. Replace jQuery with xtag, and yes, basically. The way it's been explained to me is that standalone apps are xtag applications that import React components not as Node modules, but as basic JavaScript web components (I don't know what that means) published as HTML files, which caused some confusion when I was asked to create a Node module for a React component and then presented said Node module for a React component.  I don't know. I'm not very convinced of this approach. Maybe it's just how front-end dev is, maybe our approach is flawed, IDK. All I know is that it's probably time to  after I get my yearly bonus.
Pollyanna fucked around with this message at 16:50 on Dec 16, 2016 |
|
#
?
Dec 16, 2016 16:48
|
|
|
Pollyanna posted:and so we can all use different tech that allows us to turn the header, footer, content, calculators, etc. into drop-in components that we can include in pages written through a CMS. So basically you are recreating the asp.net webform paradigm except as a proxy layer between a your web front-end front-end and your web front-end back-end. Look like a very nice clusterfuck to develop. Have a good headache 
|
|
#
?
Dec 16, 2016 18:38
|
|
|
Pollyanna posted:We are Tools, and we GET poo poo dONe
|
|
#
?
Dec 16, 2016 20:19
|
|
|
With that attitude you should actually be Mushrooms, fed poo poo and kept in darkness.
|
|
#
?
Dec 16, 2016 22:08
|
|
|
Maluco Marinero posted:With that attitude you should actually be Mushrooms, fed poo poo and kept in darkness. 
|
|
#
?
Dec 16, 2016 22:29
|
|
|
Pollyanna posted:microservices "I've been learning some things. Your architecture sucks rear end. You need to re-architect everything. <Links to microservice article>" Microservices will totally help with this problem you know nothing about, nailed it!
|
|
#
?
Dec 18, 2016 20:07
|
|
|
I once had a guy, new guy, say that he implemented a solution for a thing over the weekend that was projected to take a month or two to do. When I asked him how it tied into other, important core parts of the app that he was aware of he was like "whats that? nah it doesn't" Ugh, loving guy was like a jehovah witness of "the best way" to do anything. He was puritanical in his proselytization
|
|
#
?
Dec 18, 2016 20:19
|
|
|
KoRMaK posted:I once had a guy, new guy, say that he implemented a solution for a thing over the weekend that was projected to take a month or two to do. This is a big reason why I don't try and implement sweeping changes right out of the gate. There's always something I'm missing. My Rhythmic Crotch posted:I used to work with That Guy (everybody works with That Guy) and I was having some downtime issues with my stuff. He messages me and starts complaining about the downtime (and rightly so, downtime is bad): At least That Guy understood what microservices were Whatever, not my problem.
Pollyanna fucked around with this message at 20:52 on Dec 18, 2016 |
|
#
?
Dec 18, 2016 20:49
|
|
|
I work tangentially with another team a continent away and it's interesting in different approaches we take. Here we have 50 provisioned nodes in AWS for QA and dev. Need to test something, sign out a node, deploy to it and test it. There, one backend serving for all possible branches that design, QA and dev will use. Hope you don't change anything too major!
|
|
#
?
Dec 18, 2016 21:46
|
|
|
KoRMaK posted:I once had a guy, new guy, say that he implemented a solution for a thing over the weekend that was projected to take a month or two to do. We come in Monday morning, and he has implemented his precious protocol on his side, and is now demanding we implement it on our side. My boss and I asked what was so bad about logging to a file? Why send log messages over a TCP loopback? "File logging is lovely, and we are not going to have lovely stuff in this project. My logging protocol has checksums, retries, error correction, etc". Apply your own checksums and retries on a TCP socket looped back to localhost, and then write it to disk. So much better than just writing it to disk to begin with! My Rhythmic Crotch fucked around with this message at 22:09 on Dec 18, 2016 |
|
#
?
Dec 18, 2016 22:04
|
|
|
My Rhythmic Crotch posted:That Guy also did something similar. On a Friday evening, he sent out a "spec" for a custom protocol that would run over TCP, sending log messages from one component to another. Also want to mention that The guy in mine took the opportunity to share what he did in the sprint meeting amidst me talking with the IT Manager about the timeline for this thing and it just had this subtext of him trying to one up me and broadcast it to anyone that would listen. My response was "oh cool, I'd like to take a look at it and see if there's anything that can improve the current implementation"
|
|
#
?
Dec 18, 2016 23:05
|
|
|
The usual problems with file logging aren't bad enough that you should resort to writing your own network-based logging conventions unless you're stupidly using your log as a streamed coredump or a diff of memory contents every microsecond. For application logs, just make sure that it can work with rsyslog or fluentd and that logrotate doesn't barf on it during fairly high write activity to the file and you will be well in the clear.
|
|
#
?
Dec 19, 2016 02:04
|
|
|
necrobobsledder posted:The usual problems with file logging aren't bad enough that you should resort to writing your own network-based logging conventions unless you're stupidly using your log as a streamed coredump or a diff of memory contents every microsecond. For application logs, just make sure that it can work with rsyslog or fluentd and that logrotate doesn't barf on it during fairly high write activity to the file and you will be well in the clear.
|
|
#
?
Dec 19, 2016 03:18
|
|
|
I see you've met my coworker, who views the world in two buckets: 1) things he wrote himself, which are cool and good 2) all other code, which is worthless garbage written by idiots for idiots and you should be fired for using it because it's awful
|
|
#
?
Dec 19, 2016 15:33
|
|
|
Docjowles posted:I see you've met my coworker, who views the world in two buckets: I'm that guy, but in my defense I write javascript for a living.
|
|
#
?
Dec 19, 2016 15:46
|
|
|
Pollyanna posted:
Oh cool it's not often I see someone attain Zen
|
|
#
?
Dec 19, 2016 16:03
|
|
|
|
| # ? May 9, 2024 22:44 |
|
|
What's the deal with microservices? Sounds like a good way to end up with an incoherent, fragmented codebase
|
|
#
?
Dec 19, 2016 16:07
|
|