This was my immediate reaction as well.
For those who like living a messy life, there’s always Visual Studio (the original beast, not VSCode)
This was my immediate reaction as well.
For those who like living a messy life, there’s always Visual Studio (the original beast, not VSCode)
VSCode supports it also for other shells. This repo is not about vscode, it’s about actual shells. You are the one incorrect in this case
When someone brings points in the discussion, you react like a fan boy student that just bought the new gaming laptop.
Could you please reply about the discussion or go back to school? I am too old for your “no, you shit, you stoopid”
I wonder myself why I keep answering to your comments and that’s why this is my last comment
Unfortunately… That is why I commented above…
Powershell is a shell that pretends to be an OO language and that fails dramatically at both.
It was a design mistake. Much better having a real separation, a real shell and a real OO language. As even Microsoft has recently understood. As you can see also in this case, where Powershell is the last entry
What is a real advantage compared to plain autocomplete? Was it trained to know command flags?
It is anyway nice to see that even in Microsoft the abomination of Powershell is the lowest in the list of shells. It is probably time for them to drop it completely
You can easily build one yourself. Check llamaindex and langchain for prebacked solutions. Otherwise the math is pretty trivial if you are using normalized embeddings. You can quickly do one with numpy.
My suggestion anyway is to start with langchain, full of tutorials executable as jupyter notebook
Source? I’d like to read the story
Edit. https://www.edn.com/1st-fortran-program-runs-september-20-1954/
Magit is super cool but not exactly easy to use :D
For these reasons, I always push for simple and straightforward workflows and many commits and merges. For many people git remains a mistery also after years working on it. I blame the easy-to-use guis, many people learn 2 buttons to press for a workflow, and they never care learning more
Vscode and git lens. If you are older like me, emacs and magit
Never had issues in the past, I actually did the tests for few friends, just for fun. But most of the time they are overkill. Now that I have more experience I realize it takes few very basic questions to understand if one is technically fit for the job.
I don’t know if I would appreciate a complex test now if I was looking for a new position. It feels a bit disrespectful.
I currently struggle accepting all the psychological and hr tests for management positions… They are hr bs. I do them, but they are imho much worse than technical test, because completely useless and arbitrary. Those are really offensive and intrusive
More than 5 years then. The comic was right, with the difference that it took more than 1 single team of researchers to solve it
Sure, there are several. But, for instance, Python is pretty much only sqlalchemy. All others are not really common.
At the end with a single framework one can use several backends. That is pretty convient
How many good orm do you have per language? 1? 2? Orm is practically locked once one chooses the language
Working in a data intensive context, I saw such migrations very often, from and to oracle, ms sql, postgres, sas, exasol, hadoop, parquet, Kafka. Abstraction, even further than orms, is extremely helpful.
Unfortunately in most real case scenarios companies don’t value abstraction, because it takes time that cannot be justified in PI plannings and reviews. So people write it as it is quicker, and migrations are complete re write. A lot of money, time and resources wasted to reinvent the wheel.
Truth is that who pays doesn’t care, otherwise they’d do it differently. They deserve the waste of money and resources.
On the other hand, now that I think of it, I’ve never seen a real impacting OS migration. Max os migration I’ve seen is from centos or suse to rhel… In the field I work on, non unix OSes are always a bad choice anyway
You miss the major reason of an orm, abstract vendor specif syntax, i.e. dialect and derived languages such as pl sql, t-sql, etc.
Orm are supposed to allow you to be vendor agnostic
I am a human, who happened to be browsing lemmy when you answered, and work in ML and with a background in algorithms and HPC. It happened to be a lucky coincidence
Because it cannot be mathematically developed. KPIs as class of algorithm are linear dimensional reductions from a complex hyperspace to a small, arbitrary reference system built on non orthogonal axes, aimed to capture non periodic, non stationary phenomena (i.e. that unpredictably evolve over time).
Mathematically, performance kpi do not make much sense for most jobs, unless the job is so straightforward that the hyperspace has such low complexity that KPIs are meaningful representation. Not even a call center job has such mathematical characteristics…
As a task, AGI is mathematically much simpler task.
However performance kpis are the only thing many have to judge, as they lack technical and personal skills to do otherwise. It’s a tradeoff, but we must recognize that kpi are oversimplifications with extreme loss of information, many time useless
What evidence do one needs other than the opinion of their teammates and lead?
No one should drop players from a team due to statistics. Otherwise you’d have a non functional team of cheap wannabe-Ronaldos unable to function. Which is the reason kpi based approach fails
The real problem is honesty of the users and rewarding system. Why do people copy and paste answers from chatgpt? Or even spend time to create bots? Because there is some kind of reward for them. The reward is what needs to change. The reward is the driving force to “cheat”. Why are these people doing it? What’s the reward they are after? I have no idea. But there is the problem to solve
I create proper libraries. I don’t do snippets because they make code dirty, redundant and difficult to read on the long run.
I actively discourage people in my team to use snippets copy and pasted everywhere themselves. If it’s reusable code, it should be usable by everyone and well tested