|
New Yorp New Yorp posted:Working in Development: You don't have to know about anime to work here, but it helps Working in Development: Pollyanna needs to ask better questions during the interview process
|
#
?
Dec 1, 2017 17:41
|
|
|
|
| # ? May 24, 2024 08:11 |
|
|
From now on, my questions for interviewers will always include "how many of your servers are named after anime characters"
|
|
#
?
Dec 1, 2017 17:46
|
|
|
ChickenWing posted:From now on, my questions for interviewers will always include "how many of your servers are named after anime characters" If you name them the become pets. Servers should be cattle not pets.
|
|
#
?
Dec 1, 2017 18:04
|
|
|
Cancelbot posted:It isn't! It's important to note that the default behavior in ASP .NET land is to apply the transform at build time based on the build configuration, which is awful. You want the transformation happening at deployment time, so you can reuse the same build through a pipeline of environments.
|
|
#
?
Dec 1, 2017 18:21
|
|
|
Pollyanna's poor work place choices are a bright source of comedy in this dry forum. Please never stop posting, friend.
|
|
#
?
Dec 1, 2017 18:35
|
|
|
New Yorp New Yorp posted:It's important to note that the default behavior in ASP .NET land is to apply the transform at build time based on the build configuration, which is awful. You want the transformation happening at deployment time, so you can reuse the same build through a pipeline of environments. Why would I want that? The release build is going to be different than the debug build anyway.
|
|
#
?
Dec 1, 2017 18:46
|
|
|
1) I applied to a job opening for embedded middleware software development. 2) On the phone the job was described as UX design with no programming involved. Odd, but jobs are thin here and I'd done it before, so I didn't bail. 3) At the in person interview I found out they'd had a UX designer for over a year and what they really needed was a senior architect to untangle their spaghetti code. I wasn't thrilled until they offered me a 12% bump over what we'd discussed on the phone. 4) On my first day, they had me work on adding some new UI elements because they had a delivery due at the end of the month. I went along with it because it was a good way for me to find my way around their codebase. 5) 3 days into my new job, the CTO pulled me aside and asked me to work on a super secret project that had not even been mentioned previously. 6) 2 weeks after that I was asked to setup nightly builds even though I was the only person working on the project. Oh, and we don't want to use the AWS service we're already paying for, please use these old computers to setup a server to run the nightly builds on. I wonder what I'll be working on next month.
|
|
#
?
Dec 1, 2017 18:47
|
|
|
A new job
|
|
#
?
Dec 1, 2017 18:50
|
|
|
Sounds like you're the one writing the spaghetti code now since they won't let you finish anything properly?
|
|
#
?
Dec 1, 2017 18:58
|
|
|
Giga Gaia posted:Pollyanna's poor work place choices are a bright source of comedy in this dry forum. Please never stop posting, friend. Lumpy posted:Working in Development: Pollyanna needs to ask better questions during the interview process If anime coming up during an after hours dinner is enough to make a job a bad one, then I suspect there's a looooooooooooot of bad jobs out there. This isn't even close to truly bad.
|
|
#
?
Dec 1, 2017 19:17
|
|
|
someone post the article where people run a restaurant like an agile project i need it for a thing
|
|
#
?
Dec 1, 2017 19:26
|
|
|
https://steemit.com/food/@walden/our-lovely-restaurant-my-experience-with-agile-bureaucracy-and-unnecessary-complication
|
|
#
?
Dec 1, 2017 19:43
|
|
|
Munkeymon posted:Why would I want that? The release build is going to be different than the debug build anyway. I've been bitten by release builds exhibiting bugs that debug builds didn't. All builds in the CD pipeline are release builds unless a debug version is requested, but debug builds never go past lower environments.
|
|
#
?
Dec 1, 2017 20:07
|
|
|
CPColin posted:https://steemit.com/food/@walden/our-lovely-restaurant-my-experience-with-agile-bureaucracy-and-unnecessary-complication that's the one ur gr8
|
|
#
?
Dec 1, 2017 20:09
|
|
|
New Yorp New Yorp posted:It's important to note that the default behavior in ASP .NET land is to apply the transform at build time based on the build configuration, which is awful. You want the transformation happening at deployment time, so you can reuse the same build through a pipeline of environments. I feel as though I need to elaborate more, please take for granted that you may already know this but it's for the benefit of others in the thread: We build everything in release mode using TeamCity with nothing transformed; we preserve the root web.config and every single web.environment.config gets bundled into a zipped artefact. The artefacts are then sent to Octopus deploy. Octopus will then select the correct file to transform the web.config based on the target environment and throw away the non matching transform files. So; - web.config - web.beta.config - web.staging.config - all the other app files Are all together in the MyApp.nupkg file. 1. Octopus will deploy to "beta" first, usually triggered by TeamCity 2. All app files are extracted to the target folder, on the target machine, in the target environment 3. web.beta.config will be applied to web.config via XSLT transformation, so everything that needs to change to work in beta has been changed on the real config. 4. Octopus then deletes all the non-matching transform files (in this case web.staging.config) 5. App is re-registered with load balancer This is a fairly standard pipeline for .NET using TeamCity + Octopus, or so I thought? This has been working this way for years now. Until I created a new staging environment. They either didn't make a web.staging.config file, or made one that was copied from their dev files lazily and then I get blamed for everything breaking. Even though weeks before the project started all the teams were told to do these steps preemptively.
|
|
#
?
Dec 1, 2017 20:12
|
|
|
Pollyanna posted:If anime coming up during an after hours dinner is enough to make a job a bad one, then I suspect there's a looooooooooooot of bad jobs out there. This isn't even close to truly bad. Anime isn't a problem. Anime wallpapers as desktop background isn't a problem. Introducing your anime desktop wallpaper as your wife is a (hilarious) problem.
|
|
#
?
Dec 1, 2017 21:07
|
|
|
Volmarias posted:Anime isn't a problem. Anime wallpapers as desktop background isn't a problem. Opinions may differ on this point
|
|
#
?
Dec 1, 2017 21:09
|
|
|
Volmarias posted:Anime isn't a problem. Anime wallpapers as desktop background isn't a problem. Introducing your anime desktop wallpaper as your wife is a (hilarious) problem. It was also very much in jest, so I really wouldn't take it that seriously.
|
|
#
?
Dec 1, 2017 21:14
|
|
|
Cancelbot posted:This is a fairly standard pipeline for .NET using TeamCity + Octopus, or so I thought? This has been working this way for years now. Until I created a new staging environment. They either didn't make a web.staging.config file, or made one that was copied from their dev files lazily and then I get blamed for everything breaking. Even though weeks before the project started all the teams were told to do these steps preemptively. That's how I've always set it up. I also use variables in Octopus where needed, because they can contain secret values that you don't want floating around in source code. I actually prefer the old XML transforms to how it's commonly done now in ASP.NET Core, where you have the environmental 'transform' files as JSON overrides that get applied on top of the base config.json at runtime. It makes it difficult to know exactly what the settings are, where before you could just look at the transformed XML.
|
|
#
?
Dec 1, 2017 21:17
|
|
|
rt4 posted:Sounds like you're the one writing the spaghetti code now since they won't let you finish anything properly? Probably. I'm very much learning by doing. Right now I'm trying to synchronize ios and android builds by pushing version information from a .txt file into the respective formats' versioning files and doing some sanity checks after the second build finishes. Pretty janky. I should check and see if I can do both in the same Jenkins job. Although that would mean I would only see the first failure. Maybe if I distributed the joint build only on success and then converted the singleton builds I've got now to only send emails on failures.
|
|
#
?
Dec 1, 2017 22:05
|
|
|
Lumpy posted:Working in Development: Pollyanna needs to ask better questions during the interview process Why? She's being matched with the perfect companies for her.
|
|
#
?
Dec 1, 2017 22:08
|
|
|
New Yorp New Yorp posted:I've been bitten by release builds exhibiting bugs that debug builds didn't. All builds in the CD pipeline are release builds unless a debug version is requested, but debug builds never go past lower environments.  you're right, of course there's no loving point in deploying a debug build to QA or Acceptance
|
|
#
?
Dec 1, 2017 22:21
|
|
|
Pollyanna posted:If anime coming up during an after hours dinner is enough to make a job a bad one, then I suspect there's a looooooooooooot of bad jobs out there. This isn't even close to truly bad. anime is probatable in yospos. a good, just and fair ruling
|
|
#
?
Dec 1, 2017 22:45
|
|
|
ChickenWing posted:someone post the article where people run a restaurant like an agile project i need it for a thing spotted at a deli  pretty good use of it actually
|
|
#
?
Dec 1, 2017 22:46
|
|
|
KoRMaK posted:spotted at a deli Oh man I can't wait to get the Zingerman's box a family friend sends us every year at Christmas.
|
|
#
?
Dec 1, 2017 22:51
|
|
|
Why have a desktop background as waifu when you can benchmark with waifu? I'd hire Pollyanna if I was in a place to do so. We seem to participate in all the same threads. Actually I dunno if Pollyanna ever posted in the military history thread. Gotta check that. I'd just be afraid the organization would immediately turn completely crazy.
|
|
#
?
Dec 1, 2017 23:05
|
|
|
Munkeymon posted:Uh? Or, hell, environment variables.
|
|
#
?
Dec 2, 2017 00:42
|
|
|
Rocko Bonaparte posted:Why have a desktop background as waifu when you can benchmark with waifu? Hey, those are actually good utilities.
|
|
#
?
Dec 2, 2017 23:43
|
|
|
Rocko Bonaparte posted:Why have a desktop background as waifu when you can benchmark with waifu? If anime makes things crazy then I don't want to be sane 
|
|
#
?
Dec 3, 2017 00:13
|
|
|
pigdog posted:Hey, those are actually good utilities. Pollyanna posted:If anime makes things crazy then I don't want to be sane Go right ahead, but does having somebody's yamato nadeshiko waifu improve its effectiveness?
|
|
#
?
Dec 3, 2017 06:39
|
|
|
They must have quite bit of faith in their product, to face the ridicule of putting their animu wife in it if the product didn't perform. So it's kind of encouraging to be honest.
|
|
#
?
Dec 4, 2017 11:20
|
|
|
pigdog posted:They must have quite bit of faith in their product, to face the ridicule of putting their animu wife in it if the product didn't perform. So it's kind of encouraging to be honest. I’m unconvinced. 
|
|
#
?
Dec 4, 2017 14:41
|
|
|
I think I just threw up a little in my mouth
|
|
#
?
Dec 4, 2017 14:52
|
|
|
surely there are rules against NMS content in a work chat thread
|
|
#
?
Dec 4, 2017 15:43
|
|
|
I find what’s inside the box to be much more offensive.
|
|
#
?
Dec 4, 2017 15:48
|
|
|
Pollyanna posted:I find what’s inside the box to be much more offensive. You open it up and there's a manila envelope and a sheet of paper, which reads: We just took a picture of you opening up a box with anime waifu all over it. Drop this envelope off to the man sitting at the second bench from the right corner across the street or we will publish the picture all over the Internet." Except there are a few spelling errors that would only be readily done on a Cyrillic keyboard.
|
|
#
?
Dec 4, 2017 18:26
|
|
|
So it finally happened: A live deployment failed as someone duplicated configuration which caused a duplicate key exception and took everything out for us. Easy SQL update and the team have applied a fix that will be promoted up. 3 hours later... During testing of their fix, they ran the breaking SQL against production AGAIN thinking they were connected to test.
|
|
#
?
Dec 4, 2017 19:35
|
|
|
you should store connection info in the environment instead of the repo imo
|
|
#
?
Dec 4, 2017 20:29
|
|
|
I completely agree. There's just years of institutional crap I need to clean up where people just hop onto production SQL for "quick fixes".
|
|
#
?
Dec 4, 2017 22:06
|
|
|
|
| # ? May 24, 2024 08:11 |
|
|
Doing my first ever production deploy tonight which entails changing the primary and foreign keys on ~100 million rows and changing the application services to use the new thing. Fingers crossed.
|
|
#
?
Dec 4, 2017 23:32
|
|