Looks like a 3rd now. Unfortunate. Top contributors. I'd like some more details too but in general I don't get why people find the need to be so abrasive (my guess to what happened). It's just code.
Yeah heard that was good too. Thanks for the tip. I feel like that would give you the real details that one would need to know for a situation like that.
I think you could argue it's created a class of wealthy and super wealth admins who don't add value. From what I've read several studies have shown the vast increase in college expense has been sucked up by administrators and non teaching staff. I was looking at my college's (midwest state school) payroll and the various provost were making $600k. Kinda wondering what in god's name these people do.
Anyone have an example of using window functions in a non time series data set? Kinda seems like a bit of a flag in my head that if I'm asked to do some analysis w/ time series data (depending on the question) a window function might be a good the tool. Reading this you can tell I'm not particularly fluent in them. We use them at work and I was asked during my interview about them (did not know but got job anyway).
I've personally seen and done both. At one job (first actual dev job) it was a lot of complex business queries for analytics. I put these into their own python module as string "constants" and imported them (I would not do this again). At my current job we put them in .sql files and have a 3 line function that opens and reads them into a string. I sometimes write them inline. I've come to only one real conclusion though is that unless it's super trivial I put the SQL outside of where they are being invoked and name the .sql something that makes sense. It's just noise in my code and I want to see the logical steps.
Take my upvote. This has helped us a ton. So nice that it resolves dependencies. Only issue we're running into is that we don't use it to manage our dependencies for our internal packages (only using it at the application level). I've been advocating we change so that we simply read in the generated requirements.txt/requirements-dev.txt in setup.py
> Yet an underlying concern is that pilot programs like these could alienate riders from taking public transportation entirely.
I thought this was the best line of the whole thing. If you can't pay for it then how can you be alienated? If you are paying for it then isn't the so called "hostile" design no longer hostile?
I would think more than 2 layers of inheritance is a major code smell in any language let alone Python. There is surely a way that inheritance chain could be broken down to make more sense.
This also would require that devs who are on the PR reviews ACTUALLY look at the code. In about every job I've worked at in my short career there are people I work with that I don't trust them to actually review my code. I've come to accept that. I instead make sure the people I know will do a decent job are on the PR. Some people will just look at the diff and an even smaller few will actually pull the branch locally so they can see the entire context. That being said I always do my best to review other peoples code regardless of whether or not they will review mine.
One thing I didn't realize till I talked to someone who works in IT procurement for a populous county in KC was that they can capitalize buying servers, and finance via bonds, vs. using cloud providers, which comes out of their operational budget.
Yeah I can understand the ethos of that but don't you think that part of the goal should be to allow them to build up the capital to expand out of the space? Do you have some type of progression to get them to scale up and out? It seems like it would be a tricky thing to navigate. You wouldn't want to artificially restrict them from growing. Then they'd end up staying in the space taking up room that could be used by one or more up and comers.