944 karma · joined November 24, 2014
Usually, but not always. I’ve seen them collocated more frequently of late and almost made the same mistake before comparing price. The text was so small I would not have noticed without price setting me off. It clearly can be deceptively packaged and I would imagine many marketing departments will try if they think it’ll make them money.
For the uniformed, like me, here's a meteor RPC - https://guide.meteor.com/methods.html
While today I might re-use _some_ code, like helpers or TypeScript types for API responses, by and large I feel like that dream is unrealized and probably a never great dream in the first place. In practice there just weren't a ton of wins from doing so, as there were not many cases where you needed the same code in frontend and backend.
I know sweating isn't perfect, for the reasons you mentioned, but do we see nature evolving any better solutions at a mammalian level?
My armchair understanding is sweating is a natural marvel with nothing else like it seen in creatures as large as us. That it truly is a differentiator between humans and other animals (or mammals at least). Sweating is the foundation of humans ability to engage in long-distance endurance running which is one of our unique features, also called persistence hunting[0]. You can easily draw a line between this sweating and our ability to travel large distances and hunt the way we did, which in turn can be connected to humanity's success as a species on earth.
Sure, but saying "open this file" and having the response "nothing here, boss" is not exceptional. It's pretty normal. Isn't that just one of the two obvious options when you try and open a file? To me, exceptional would be something like "this file was open and now it's deleted."
I haven't opened the YouTube video as I'm on data right now.
I forget when, but in last ~3-5yrs, I've noticed iOS seems to handle this. If you leave a device plugged in for a long period you eventually getting a notification saying it's not gonna charge as much, and it caps the max battery to 80%.
Just wondering if your story is before or after that feature.
edit: I googled, it was iOS13, so 2019 - https://support.apple.com/en-ca/HT210512
I mean, you made up international federations of managers "out of thin air" too. That's how conversations work, people introduce things, if you have issue with a particular point you can discuss that.
>and b) If an IC "is combative and fighting with their manager at every turn.", then holy hell, is it not an interpersonal conflict, it's even more of a management failure.
It's possible some people are just combative and unprofessional, and should never have been hired in the first place (or changed over time). I agree that a manager has more responsibility for a relationship with their reports than vice versa. But, I also think it's entirely possible for an employee/contractor to just be too combative and hostile, and it not necessarily reflect on the manager too.
>A lot of this entire thread sounds like "perfect victim" blaming. Only the perfect victims are allowed to point out abuse in the system, if you have some prior criminal history or you've made some sexual missteps in the past, then you "deserve" the police brutality/sexual harassment that was put upon you.
I'm seeing the view that everyone always remain professional at work - even if other people are not. I don't think that means you "have to" disregard someone's opinion. But it means if you're not professional there can be consequences. If someone is insubordinate at work (disobeying a manager, creating sarcastic/mocking backlog issues) its common grounds for termination and blacklisting. I'm not saying this to support the status quo, I'm saying this as advice for people reading these threads and trying to navigate professional waters. It would be bad advice to suggest otherwise.
Ultimately, businesses generally function by paying you for your time. If they pay for your time, but you're not doing what they want with it, they're going to stop paying you for your time. If you have a bad manager, you need to frame it in terms of how it's detrimental to the whole business.
I disagree this has anything to do with police brutality or that those parallels are helpful. I have no requirement to be professional to the police (although, for better or worse, it's often unwise to be an asshole to cops, it is legal). Whereas I do have a requirement to be professional at work. I see the point you're trying to make, how often people who suffer police brutality are maligned due to unrelated crimes they may have commited. And that's fair, that's just personality assassination. But I would say the issues have to be taken separately - the police abuse is clearly heinous and should be stopped, but also the crimes should be treated in isolation (as they likely had been in the past). Returning to our manager/IC discussion, I'd say the unprofessional behaviour of both parties would lead to both parties getting terminated. But in reality, companies will protect management more readily than IC contractors, so I'd advise anyone in the IC's waters to tread carefully.
> An interpersonal conflict is when there is genuine differences of opinion that come from honest differences in values. Not when one or both sides are clearly wrong.
That's a good point, I agree with your framing.
I'm a fullstack dev who is often our devops/kubernetes lead. I'd say over 50% of my day is around DevOps tasks, but I'm likely to write an API or hone a frontend animation as well. I contribute on all parts of our microservice based kubernetes government application, but do skew to the devops side where the rest of my teams' experience is lighter. I can write iptables or webpack configs, I can implement OAuth or modify bezier curves for animations, and frequently do it all at my job. I have just over 10 years of professional experience but have been programming longer.
Everyone has to be mature and professional at work. Yes, management might be held to slightly higher standards, but being combative and fighting with your manager at every turn is below the standard for anyone.
Totally agree, but I think that would be fascinating to see. It's essentially the end-goal of a lot of the political/national security growing concern over semiconductor capacity. I could imagine it being pretty subsidized and even a token inclusion at first just due to outside pressures and incentives, but I'm just speculating.
I do not believe that is the aim of Archive.org. That sounds more like Wikileaks territory.
The goal is to hold the company accountable, but it sounds like they just created legalized paid-fall guys.
If the government wants to pierce the limited liability veil, they should either go after the persons in the company either directly or ultimately responsible (eg the direct manager, or the C-suite). Letting the company decide who takes the fall just means they're going to foist it on some uniformed schmuck.
You get paid more for being on-call - now wait until you see the legaly-liable-for-the-entire-company bonus!
So from your post it follows that if a developer can reason about the state changes of their app without redux, they should do so if there are performance concerns. Right?
I say this as a webdev who has written pure vanilla Js SPAs a decade ago, and someone who often uses Redux now on most projects today. So I know it’s totally possible to have performant mutable state management on a project that isn’t a mess - that’s how we always did stuff before redux.
As a semiconductor lay-person, my expectation is that this course would really just be an organized curriculum around semiconductors, and if you completed it you'd be hopefully competitive getting a job at Intel/Qualcom/etc. I am not expecting them to be providing any fundamentally novel approaches to semiconductor theory or design. To me it makes sense that the same type of knowledge may have been at the graduate (or more advanced) level before.
So to my (ignorant, layperson) perspective, I see the value of this making semiconductor study more accessible. It's no longer something you have to do for a (for example) PhD, but rather a structured program that should lead to an increase in semiconductor experts.
Am I off base? When you say you feel like you are "missing what's different here", what would you expect? Is it typical for new academic physics programs to provide truly novel techniques?
Unfortunately if this is the case, I imagine it would still be the case even if food truck vendors were forced to submit a form testifying they had proper disposal arranged. As a thought-experiment, I imagine if this food truck was dumping his garbage in the mayor's garbage-bins, that they would find a way to make him stop with existing laws on the books.
There are usually laws on the books that could be used that simply are not enforced. Many jurisdictions have (by)laws about citizens being allowed the "private enjoyment" of their property, and you could easily claim that's infringed on here for the reasons you laid out. Public nuisance laws are also, by design, incredibly broad.
My point is that I believe it's a problem of enforcement and political will; not of letter of the law.
Where I am from (Canada), the correct remediation would be to take your landlord to the tenancy courts where you could represent yourself (i.e. not need a lawyer), but that's still undeniably a huge pain for a rough situation. I'm glad you're in a better spot now.
edit: CRUD means Create-Read-Update-Delete. It's a basic programmer term for a simple application, or those simple parts of it at least. Even something big like Wikipedia, at it's core is a CRUD site. Most things are, with business logic sprinkled in; but some things aren't CRUD at all (eg a video game).
For example, if you're a car dealership your LOB CRUD API would handle stuff like submitting new cars, or staffs, or associating a sale of a specific car with a specific salesman or whatever other biz logic you have. This could be in contrast with, say, your Document Storage CRUD API which handles integrations with your document storage (eg storing things on a SharePoint, or Ceph, or S3, etc).
LOB has no inherent value with regards to microservice vs. monolith, it's simply another way to refer to the business specific logic. The term LOB is common across business as a whole, whereas "business logic" is generally a phrase used by programmers about programs.
[0] https://twitter.com/cajundiscordian/status/15357826682476462...
As an outsider, the only real issue I'm aware of is the refusal to prosecute theft under $1k (edit: $950), which seems like something that is completely out of the police's hands.
For one, healthcare is purely the purview of the province. The federal government has no ability to force provinces to treat drug use as a healthcare issue.
Secondly, enforcement of laws in BC is a mix of both provincial and federal and this gives the provincial government leeway. In BC, the RCMP is responsible for both provincial and federal enforcement. One of the earlier marijuana legalization efforts in British Columbia, which was supported by mayors and previous provincial ministers, hinged on enforcement. The plan was effectively to order law enforcement to not enforce marijuana laws. The province itself couldn't strike the law, but they could effectively not comply. Admittedly this is a grey area, which theoretically would require the courts to sort out, but in practice it shows some viability of the approach.
In general, Canada's governments skews heavily towards provinces rather than federal (unlike the USA which has a very big federal government, most Canadian gov employees are provincial). Provinces have had the upper hand since Confederation and have been unwilling to give up much power. As such, I doubt how much approval the province needs from the federal for an action like this.
The poster child of gradual typing has to be TypeScript, and it's been a wild success. TypeScript allows gradual implementation to any JavaScript project and there's almost a million small different gradients you can use. From simply using a js file, to noImplicitAny, to simple types, to using complicated built-in types (eg Partials).
With TypeScript, you never lose the speed of dynamic typing. The whole point of gradual typing is you can jump between more and less types, so at no point are you restricted from reverting to full dynamic typing. And it is true, you can't rely on all types being checked, but the point is you add it to the important/stable bits. And having your largely stable important bits being typed while your more experimental unstable code can be dynamic (while still getting the benefit of consuming the stable types) is a nice place to be.
As I said, it is what you make of it. If you spend all your time typing the unstable bits and leave the stable core bits untyped, well, you've just wasted your time and would get the worst of both worlds.
I think another way of thinking about this is hire "former DBAs."
Most of the developers I know who had really solid SQL, the greybeards I learned from, were either former DBAs or former sysadmins who had become full-stack developers.
edit: Another was a junior developer who interned two years as a DBA role. He was desperate to lose the DBA title, and I always respected that, but damn if his SQL wasn't better than mine.
I've found these technical discussions, pair-programming, mentoring, architectural consensus building, are all much easier to do "remotely" than typical management-style discussions. Our project's technical team size fits into the "two pizza" rule, although just barely probably, so it's not like we're super tiny.
Pair-programming is great online. Better than in-person in my experience. Simply share your screen, and I can put it up on my second monitor. We've successfully mentored numerous junior-ish devs during COVID, with heavy use of remote pair-programming.
Architecture type discussions main drawback is missing a whiteboard, but there are a plethora of online tools of varying quality. In practice we often use draw.io and show a bit more finished copies than pure whiteboarding, but we've used other more simpler solutions for whiteboarding here too.
Design discussions/architectural consensus take place fine online, we just haven't had any issues. Just like pair-programming or architecture, we might screenshare but mostly we talk. And we find we don't lose anything from this. Sure, you don't get body-language, but that isn't needed for discussing bearer tokens.
In summary, while I agree that technical discussion is necessary at all stages, I believe that technical discussions is far less negatively impacted by remote when compared to non-technical discussions (i.e. managerial).
Essentially, a determined malevolent actor who controls the client could exfiltrate your keys easily. Maybe it's intentionally introducing a subtle vulnerability and then exploiting it server-side[0], or it's just simply doing a file upload of the keys. Basically, you can't be certain there isn't a backdoor from a malevolent actor.
[0] IIRC, there was some vulnerability in the Linux Kernel a few years ago that was basically there due to an errant space. Some people theorized that this could have actually been intentionally introduced by sophisticated actors, to hide in plain-sight open source code.