lijok

16 ms·

271.
by lijok 2y ago
He did all but the Twitter takeover prior to turning shitheel. And I wouldn't consider Twitter reformed, so much as its goals have changed.
272.
by lijok 2y ago
Most of the issue exemplified in the article arise due to a lack of domain expertise, not ego. Parochialism, maybe, as it relates to lack of expertise. We fear what we do not understand, which translates into domain ownership and controls o
273.
by lijok 2y ago
There is currently literally 1 comment disagreeing with some of the points in the article. Are you saying you wouldn't want to work with anyone that agrees with the points in the article? If so, it would be interesting to hear your tho
274.
by lijok 2y ago
Interesting, could you elaborate? I'm unfamiliar with that usecase
275.
by lijok 2y ago
Reading "rewrite history" sets off so many red flags for me I struggle to take this seriously. What are you trying to do? Are you embarrassed that you arrived at an end goal via a suboptimal sequence of steps, and are trying to pr
276.
by lijok 2y ago
The discomfort needs to be alleviated by learning a new language. E.g. moving to the country where the language is spoken, as an extreme example.
277.
by lijok 2y ago
Speaks volumes to the maturity of our work that a 3000 LOC PR is seen not only as acceptable, but expected. Raising a planning change equivalent to a 3000 LOC PR in a civil engineering firm would get your assignment swiftly handed over to s
278.
by lijok 2y ago
Isn't adding dependencies, groups or not, as simple as opening up the pyproject.toml file and adding it to one of the lists?
279.
by lijok 2y ago
What does this have to do with work device management? Are you seriously suggesting using a personal device for work, despite the asset leakage risk, and relying on "it doesn't matter" as recourse if that risk were to materia
280.
by lijok 2y ago
> When it comes to "assets", companies make a big fuss about leaking them, but in reality, it's totally irrelevant There’s no milder way to put this; you’re delusional.
281.
by lijok 2y ago
Personal machine as in a machine that you use for anything other than work for that particular client. The same goes for putting anything personal on a company issued device, such as signing into your private email. It is a problem in all c
282.
by lijok 2y ago
I always strongly advise consultants to use a separate machine for work, or at the very least a separate OS user. You’re risking putting yourself in a whole lot of trouble by using a personal machine for work.
283.
by lijok 2y ago
> Yeah, I'm not going to change a job just because one of my superiors is insecure You likely are, willingly or not.
284.
by lijok 2y ago
> You're assuming that the subordinate's feedback is sufficiently important to the business. That's for the superior to evaluate impartially, and if the feedback was not important, feed that back to the subordinate. Are yo
285.
by lijok 2y ago
Are you suggesting that functions overseen by those unable to process no-fluff information, are often successful and do not sink?
286.
by lijok 2y ago
Fully agreed. I would consider not pointing at people's faults in a public setting to be basic etiquette.
287.
by lijok 2y ago
> Sounds good on paper. Maybe true, oh 5 years ago. In this job market, polishing the resume is nice but you might have to deal with irrational superiors for a little longer. That's what the article is about. Wouldn't it be bet
288.
by lijok 2y ago
> My no-fluff feedback for you: Your comment would've been far stronger if you simply specified these unnamed handbooks, and summarized their argument, as opposed to fulminating + offering a handwavey argument-from-authority. I know
289.
by lijok 2y ago
Half baked thought; what about a linkedin style connection graph where your feed is only populated by those in your network, and it is trivial to see and disconnect from whoever introduced the bot into your network. Would a community self r
290.
by lijok 2y ago
Astonishing. Completely backwards. This article describes how to give feedback to your subordinates, not to your superiors. If your superiors are unable to process no-fluff information, regardless of whether it's feedback or updates, t
291.
by lijok 2y ago
People still use S3 because doing business with Cloudflare is a liability.
292.
by lijok 2y ago
How unfortunate that line lengths ended up being a source code concern instead of a text editor concern.
293.
by lijok 2y ago
Very few professionals do this. Most people writing code are not professionals.
294.
by lijok 2y ago
That would sell like hot cakes to the public sector.
295.
by lijok 2y ago
Very handwavy. Just like the aforementioned zealots, idiots and assholes.
296.
by lijok 2y ago
No, because the fact that a neurosurgeon with 15 years of experience is not in jail means they know what they're doing. Not the case for devs unfortunately.
297.
by lijok 2y ago
> When was the last time you had to debug an ancient codebase without documentation or help from a team? > This is like asking a Ruby developer to debug PHP as a test of flexibility > If the job requires specific tech skills, test
298.
by lijok 2y ago
Given the scale at which python is run, how much energy are we saving by improving its performance by 1%?
299.
by lijok 2y ago
Would love to understand more, care to elaborate?
300.
by lijok 2y ago
> for the photon he’s talking about the photons frame of reference

More ›