auxfil

The opposite of artificial is natural

What does "carefully analyzed" mean in this context? Who analyzed it?

“Sorry but”? “Respectfully”?

Don’t care how many years you’ve been “doing this” for, you clearly haven’t spent enough time sorting your own shit out.

More capturing of personal data and more shoving subscriptions down our throats. Nope. Sod off GM.

You should really avoid getting entangled in this kind of humor.

You already live in that world.

Haha, yeah, ok buddy.

“Life experience and common sense”. You’re a waste of time.

Thank you for calling it by it’s proper name and not “Anime Homing Missiles”

Anyone else clicked here out of a personal development interest rather than machine learning?

Ah yes, academics, the most unbiased angels of us all…

There are good arguments in this article, buried in a mire of self righteous indignation.

Better education on viewing any output by a model with more critical eyes - which really is today a basic requirement for parsing any online information - is a fine bill to die on.

That then goes in hand with viewing with suspicious eyes the motivations of companies that are commercialising this technology, which is nowhere near a new sentiment.

However better recognition needs to be given to what obviously fuels the hype being railed against: the utility of this tool, even if it fails to work adequately most of the time. YMMV depending on your personal experience on the queried topics.

The article does indeed sound like it’s just preaching to the choir.

Sorry to burst your bubble, but legal philosophy is real, and has a direct impact on what you are here calling "legal".

Heckin people speaking their mind freely on such matters. Double Unbelieavable.

This is a “deepity”. We already do this. We constantly do this in programming:

“The idea is that as you start to find patterns in your application, you can encode them in a little language—this language would then allow you to express these patterns in a more compact manner than would be possible by other means of abstraction. Not only could this buck the trend of ever-growing applications, it would actually allow the code base to shrink during the course of development!”

Functions, frameworks, little languages. It’s all abstractions on top of abstractions. You are shifting the knowledge of the abstraction for the more fundamental knowledge underneath that does the actual work.

You end up just sweeping the codebase growth under some other layer’s rug and blissfully forget about the woes of future maintainers. The code is still there, abstracted and exposed by the “little language”. Hiding this behind a cute moniker doesn’t seduce.

This isn’t the future of programming. This is already programming.

Rationalise your loss of freedom to family life as much as you need to.

Go back to the shrink and get the diagnosis and the meds. You have ADHD.

The planet's overpopulated. Help people die if they choose to do so. It's a lot less messy that way, for everyone.

I take it you think people that get life insurance are suckers?

Because its the world they live in, and its real to them. Why the fuck would they go out of their way to avoid what is probably a mundane fact for them. Why did "you" have to specify that your "non-PoC" friend got busted. Just because someone calls out a specific attribute of a story doesn't automatically make it an agenda.

God there are so red flags here in terms of how you're being managed and on-boarded, and also unhelpful behaviours on your part. Let's begin...

These are all the things that stick out as red flags to me, in terms of your company - all based purely on what information you've provided, with speculation: - No onboarding process - No documentation to help someone getting started on the project - Giving a junior dev a task nobody has tried to do before is generally a bad idea. Giving a task that is unknown to the junior, but something that a senior can cover for or at the very least assist in is sane. - Shit code review; you fucking up twice so bad that a release gets delayed by a month means there's a systemic failure in how your code is reviewed, and QA tested, before being released. That's not just on you (because we all make mistakes), that's on your company for not making their integration and delivery more protected from mistakes like that, or being able to quickly roll them back or fix them. - YOUR manager has been gone since December. You're a junior. Just lol, if you aren't laughing - you should be crying. The most critical person in your start at this job is missing, and very obviously not being replaced by anyone competent enough to manage you (otherwise they'd be or soon will be a manager). - Senior telling you that they shouldn't be helping you with certain things at this point: Yeah look, I can understand what the guy is saying, you've been there for 8 months...but you weren't on-boarded properly by the sounds of it, your manager is fucking GONE, and you were giving shit tasks to learn with seemingly with no support...according to how you tell the story. 8 months is well past most probation periods. You may be sorry that you're still asking these questions, but if there was a way for you to learn it and not have to ask, that would be a lot more helpful - go with that.

Here are your unhelpful behaviours, especially as a junior: - Not asking questions often enough and soon enough - Not following up on questions already asked, to get answers (probably to avoid being a bother)

Really that's it - that's kinda all you gotta make sure as a junior that you absolutely do not fuck up, is ask questions like your life depends on it. I bet a lot of your slowdowns are due to you trying to bust trough the wall with your head with certain issues, rather than asking, because now you've stigmatised yourself about asking questions given ""how long"" you've been there for, and what that one guy said.

Please make sure you are asking questions AFTER you tried to figure it out yourself - maybe it's about how you've been asking questions, you know? There's nothing more annoying than someone asking you a question and just expecting a full answer handed to them on a silver platter, especially if its about something that's involved and would take time working out yourself, or something that is known to be able to be easily looked up. That being said - look up your own answers, and try your own solutions. Time box them to 5, 10, 15, 30 minutes...depending on how big the thing you're working on is, and then ask the question...telling the person what you've tried, where you've looked, and what you think the answer might be. Show that you put some effort into it...but don't do what you HAVE been doing, waiting too long to ask!

I know I should just focus on improvement, but I am not sure how

The answer to that questions has been missing, apparently since December. Seriously - this is what the fuck your manager is supposed to help you figure out. If you do get performance managed, that may be a blessing in disguise because it would mean knowing where you are lacking and forming a plan to bridge that gap and then review it after a certain amount of time. Don't view the PIP as some dreaded thing -- it is meant to make you productive and effective. Yeah it sucks in essence that "it got that bad", but given the circumstances BESIDE you, it IS that bad.

Should I be writing reminders to myself to always double check everything?

Writing down your own version of whatever process you need to do when you're submitting a change, or doing whatever at your company would be super helpful...ESPECIALLY if they don't have any such documentation that everyone can read already (which should be a fucking crime).

Should I write down the steps to every process?

Every process sure, but in varying detail. Some things you may want to write down step by step. Some things you may just want to write down the most important thing to remember/check. It all depends. Either way...write down whatever you KNOW you will not retain in memory AND that cannot be easily accessed online or through your company's documents and documentation.

Its hard for me to know whats a junior engineer error and whats an error I shouldn't be making at all.

You're a junior. You're meant to be making all of the errors - but you aren't meant to be allowed for those errors to proceed to consequences. Thats literally what the work processes and all the fucking DevOps and systems infrastructure is meant to be there for...to stop errors, both machine and human, from making it into production. Writing shit code is on you...but letting shit code into production is on whoever created (or didnt safeguard from) a system that lets that actually be deployed...so...the team, the rest of the company.

Writing shit code and having your team review it and the company's pipelines alerting you to errors is how you learn that it was indeed shit code, and then, through the grace of professionalism, are shown the right way, or at least given the opportunity to figure out how to fix it.

I don't know just how "bad" you may actually be (if I was to just believe you - pretty terrible; that's how you feel about you). I am only reading your "take" on it...no idea what your team actually thinks. Maybe you're overreacting, or maybe they are just incompetent assholes...hell, maybe its both.

It doesn't matter. What you gotta do, is start asking questions (more often, sooner), start writing down what you know (so you don't forget, and avoid fucking it up), and talk to someone about these very worries you're having. Is someone replacing your manager currently? Talk to that person. If nobody is, find out who your managers manager is and raise these concerns with them.

Caring about the juniors you hire is on the company. You aren't being hired to be cannon fodder. You're an investment: they get someone who is fresh and can be moulded (on the cheap, relatively), knowing they wont be productive for a good while, but will be able to pick up a lot of the processes specific to that company without "old ways" getting in the way.

Touch grass. JetBrains is trying to be like Borland in the sense that JetBrains is doing with Kotlin what Borland did with Delphi. Create their own all-in-one-place programming ecosystem. You can see it slowly coalescing.

I hope you don't write software with that kind of logic. You cannot follow a law that you are ignorant of. The word you're looking for is "no defence". Even that is debatable, subject to the reading of relevant applicable laws. Let's leave laws to lawyers and judges, shall we?

These actions can be classed as slacktivism and as impotent virtue-signaling, sure, but I believe that the actors of these methods of protest are trying to do what the left calls "creating safe spaces" and genuinely feel that they are "showing their support" and therefore somehow...helping. The thing is, they may be achieving that first part - creating a safe space, perhaps unwittingly marginalising, demonising, and isolating the very people who can affect the most change (i.e. politicians, policemen, russian people, going by the examples of causes in OP's post alone), at a further cost of inconveniencing absolutely everyone - testing the resolve of existing allies, and likely creating new opponents out of those who were on the fence or apathetic.

Let evil live in broad daylight, so that all may see it.

It sounds like this is just an exercise in, not learning, but being forced to say "No" (a lot) out of a need for mental survival...in a work culture where priorities are constantly shifted (and this is the key).

Instead, foster change where you can say "Yes, and" or "Yes, but", where there is a common understanding that sure we can work on it, eventually, as it's going into the backlog, that will need to be prioritised, or it goes at the bottom of the queue as any new thing should - as what is already in the queue, should already be prioritised.

Obviously what is already in the stack can be shifted around as the business needs may necessitate the change in priority...but popping shit at the top of the stack constantly...that's not where you need to learn to say "No"...that's where you need to learn to say "Bye".

We should change that.

Everyone seems to be either just reading the 1st tweet/the title, or using it as a prompt to insert their own gripes about Google's insular technologies.

The bigger takeaway here is that working at a large company, for any length of time, tends to sink you in (rather than lock you in) to their ways of working and it can be rather difficult to step into the wide open source world afterwards. It is not out of laziness, but out of learned ways of working and domain knowledge.

It is difficult to extricate yourself from "The <Company> way"...sometimes with panic and dismay at the sheer amount of options out there, that simply aren't as interoperable as "The <Company> way" was. This is a legitimate and valid pain point that professional software engineers, working in companies, face in their careers.

A smaller but equally important thing to note is mention of the number of people working on the build systems internally, that make and maintain interoperability between both internal and 3rd party libraries and tools, to create a smooth build system.

You're assuming that it's simple, or that it has the desired features.

enjoy living in your brave new world

It's a shill piece.