thomaslevesque posted:

@JamesNK could you explain the reasons behind this design? It seems pretty strange to me that a string value should arbitrarily be interpreted as a date just because it looks like a date...

JamesNK posted:

Because JSON doesn't have a date format.

jit bull transpile posted:

I have an actual product idea but it would be subscription based and I'd want to HQ in Milwaukee instead of the stupid sf bay so it's doomed from the start probably.

Doom Mathematic posted:

Sounds to me like the tests are working correctly? You almost shipped a breaking API change, well caught.

CPColin posted:

I recently discovered the joy of injecting mock services into other services for the purposes of testing. I was all groaning about setting up a user just right so the call to PermissionService.hasBoner() would return true when ButtService.getAvailableButtTypes() called it. Then I just mocked PermissionService so hasBoner() would return what I wanted and injected that into ButtService. It was good poo poo.

My controllers still have too much stuff going on, though, with little coverage.

Finster Dexter posted:

That has almost nothing to do with why this is horrible.

Finster Dexter posted:

Was he using SCM at all?

Shaggar posted:

git is trash.

Shaggar posted:

gits branching model is using the interns computer to store the backups

prisoner of waffles posted:

git: ensuring your work is stored somewhere other than your machine takes at least one extra step compared to most old-rear end vcses

contractor who lost all his poo poo didn't listen to someone trying to ensure that his work would be retained (and person trying to help took "no" for an answer, allowing the work to be lost)

prisoner of waffles posted:

I don't doubt that you have helped others learn stuff and that you offered help to this guy. e: also I get it-- organizationally speaking, this person is Not Your Responsibility and you are a good teammate for looking out for them, period

Perhaps not at all relevant to your experience, but my tactic when leaning on people to do the right thing (and not leave work in a losable state) re: version control is basically just to keep on repeating, "the way it is right now, we could lose this work that you have done" between talking about how easy it will be to actually keep the work and/or how it's okay if not everything is perfect or complete, "this is just a branch"

Doom Mathematic posted:

I'm more interested in how this person was allowed to work for two or three straight weeks in a row, by himself, with nothing to show for it. Every morning, "Nope, still haven't done any work"?

CRIP EATIN BREAD posted:

windows is a fine OS if you are chronically poor or incapable of using a computer that's connected to the internet. it works well if you treat it like a video game console, its a toy for novel purposes, and the people who spend the majority of using it are pathetic and useless.

Luigi Thirty posted:

they tried using all of azure but find->replace on every racial slur would have taken until the heat death of the universe

toiletbrush posted:

I don't know if it's still the case, but the commonly suggested JSON library for .NET used to spot 'date like' strings in JSON requests and reformat them into it's own format, even if the field being deserialised is a string, making validation that a date was provided in a certain format a massive pain in the rear end/impossible. The author still insists this is the correct behaviour.

ThePeavstenator posted:

lol, spent 3 hours in our dumbest and most simple API that literally just does CRUD operations trying to figure out why a consumer storing an ISO date string "2018-07-23T16:20:00Z" was getting back "7/23/2018 4:20:00 PM". The API isn't supposed to parse the string at all and the only transformation any data undergoes involves mapping the API data model to a DB data model before storing it in Cosmos DB. Weirdly, the string was actually correctly stored as an ISO string in Cosmos DB as well.

Turns out that Newtonsoft.Json, dependency of several Microsoft packages, including the Cosmos DB one has a really cool feature: It parses ISO date strings from JSON as DateTimes by default even though JSON has no concept of a Date type.

ThePeavstenator posted:

best part of that 2 y/o (and still recently active) github issue:

thomaslevesque posted:

@JamesNK could you explain the reasons behind this design? It seems pretty strange to me that a string value should arbitrarily be interpreted as a date just because it looks like a date...

JamesNK posted:

Because JSON doesn't have a date format.

ratbert90 posted:

Heh, so my ex-co-worker was asked to ask me if I would be willing to talk to the CEO for some potential work.

I was thinking some 1099 stuff that I could sub-contract so I said sure.

I got an SMS a few hours ago with a "Hey, ex-coworker said you were curious about the embedded position opening up on our Design team in 2019. We are open to considering you as a candidate based on your history with ${product you made by yourself}. So I have to ask - after your first experience with ${company}, and your satisfaction with your current position, why would you be interested in re-joining us?"

To which I replied "I'm not, I am happy with my current position, but I have noticed that ${company} has had my old job posted since I left 6 months ago. If you are interested in me doing some 1099 work, I will gladly consider it! My rate is $150/hr 10 hours minimum."

No response back.

The loving hubris of these jackwagons is astonishing.

floatman posted:

Oh yeahhhhh
first, imagine a class called Result. You can create a new result, and the constructor has an argument where you can shove in a constant. So you can do:
new Result(TypeFailed), new Result(TypePassed).
This result has a getType function to retrieve the result as well.
Now, imagine someone creates a class called ResultPassed, which inherits from Result. It also has a constructor where you can specify the constant. So although it is meant to represent a passed result, nobody is stopping you from doing new ResultPassed(TypeFailed).

In the codebase, sometimes a passed result is checked by calling ResultPassed.getType(). Other times, a passed result is check by checking if the result object is of type ResultPassed. There is no consistency, and I've lost my will to live.

toiletbrush posted:

He also banned UI chat from demos for the same reason.

Oneiros posted:

if you are using github or gitlab or some other managed git service i highly recommend using their protected branches features to prevent this sort of thing from happening in the future.

gonadic io posted:

it's right though, any enforcing of protected branches immediately causes a dozen issues/emails/whatever to be raised complaining about not being able to push to master to enforce an urgent hotfix right now now now

Boiled Water posted:

gonadic io posted:

lol branch names that reliably have ticket numbers? must be nice

DONT THREAD ON ME posted:

why do you care?

i mean i delete my branches because it's nice to keep things clean but there are few actually compelling reasons to delete a branch and plenty of reasons not to so I don't see why it's worth being bothered by.

Chalks posted:

there's a guy on our team who runs a script to list branches each time we do a release and asks anyone who's got a branch wtf is going on with it. the idea is to avoid accidentally missing features that are meant to be in the release but didn't get merged, but it also means we have very few stale branches

kinda gotta do that from the start though!

ratbert90 posted:

Versions are: YYYY.MM-Release

It took around eight months to get everything into an excellent order like that, but in the end, it makes everything much more comfortable.

I don't know if this is all gold practice, but it seems to work well for is.

ratbert90 posted:

Ex coworker hit me up on hangouts yesterday. The marketing director was put in charge of engineering.
When that happened, he quit so hard he didn’t just quit, he quit, packed his bags, and moved to Seattle with his wife without even telling anybody he quit. He doesn’t even have a job yet in Seattle.

This leaves the Ex company without any programmers and nobody to pass documentation on to. I expect the company to not last more than a year.

I got him an interview with my current company.