But doesn't this seem like the correct approach long term? Basically shelling out to what essentially amounts to a fact table when it gets a factual question
Obviously yes. And how they use these tools is important.
But it's quite interesting to see what these models can do internally and what they can't do yet. It possibly outlines future research areas (beyond " more scale") and opportunities for competitors to enter the market (which is usually better for consumers and society as a whole).
Maybe that's the difference between productization and academic reasearch.
Why do you program? It won't go away, it'll just be different. You probably don't know x86 or arm instruction sets anyway. This will be a much faster, easier way to manipulate symbolic code.
I'm looking forward to being able to work alongside an AI because there are a zillion ideas I have every day that I don't have the time to fully explore. And all I do is work on the backend of a boring-ass webapp all day.
The only worrying thing is how fast this will accelerate everything... I'm worried society will, if not collapse, go for a wild ride.
As for interfaces... I'm looking forward to much better voice assistants. I would love to be able to essentially have conversations with the internet.
Nice. I'm going to dig through these tomorrow. Thanks for posting! The PR review helper looks excellent and I'm excited to try it out. Til about `pandoc` and `glow`.
I whipped up a nice, performant branch picker last night that I'm pretty happy with, hopefully there are some useful tidbits for others. It's similar to your `flog` command but it uses the reflog to find the most recently checked out branches. It filters those which have been deleted using a set structure (well, map of bools), thus requiring BASH 4+. I'll be interested to see the differences in behavior and performance of your approach
I agree this is a stunning clip and a disgusting display of nepotism.
But I wouldn't say this clip is stunning (other than the temporal proximity). Sounds like this dude likes to run his mouth. He's bragging about his 3k sqft loft and these weird loan deals in front of strangers... I have no idea who he is, but if you showed me this clip and asked me to guess what he did when things went down, I'd tell you he said some (probably dumb) off-the-cuff stuff.
I'm glad that energy is becoming more expensive because I suppose things like this will become economical. Running BOINC during the winter is fun, but the impact is trivial.
Why? Do you ever worry about exercising because the air is a finite resource?
In a perfect world electricity would be free. It would be so abundant you wouldn’t have to worry about using it.
Of course, this implies that the energy is 100% green as well. By saying you’re glad energy is more expensive, you’re elucidating the main issue: wasting electricity is bad for the planet in many cases.
The rational reasoning is that the dollar cost of energy isn’t matching the environmental cost. We are destroying the planet for cheap so higher prices encourage less destruction.
Wouldn’t producing energy be the bad thing? If you collect all your energy from solar, I don’t care if you waste it, assuming our access to green energy is infinite.
Immediately I'm very much looking forward to a day where language learning is like this. No Duolingo gamification nonsense... I want something that remembers what words I know, what words I kinda know and what I should know next and has an ongoing conversation with me.
I think this will totally change the way we educate and test. As someone for whom the education system really didn't serve well, I am very excited.
One major problem with LLMs is that they don’t have a long term way of figuring out what your “knowledge space” is so no matter how much good the LLM is at explaining, it won’t be able to give you custom explanations without a model of the human’s knowledge to guide the teaching (basically giving the LLM the knowledge of the learner to guide it)
First of all: If you have the title of "DevOps" what you're doing is "Operations", you aren't practicing DevOps.
Anyway, this company has had incident after incident. This will keep happening every few years for them like it has for the past 10. As will lack of transparency/ outright lying.
Some commenters are saying they wish the company the best. I don't. Use something else. LastPass needs to die.
It's not a job title, it's an engineering practice. People who participate in DevOps include "software engineer", "network engineer", "IT operations engineer", "platform engineer", "cloud engineer", "quality engineer", "security engineer", "manager", etc.
I'm also one of the people who does "operations" but has a DevOps job title. I've grown to accept this as a second definition, it's quite common now.
I do not like the title either, but I do understand the motivation of taking all those "non-software engineering", technical roles and putting them under the same umbrella, due to a lack for a better title, because a company might not afford to have separate roles for each of those areas you have listed above.
"OPERATIONS ENGINEER" might work, but it raises another set of problems, e.g. does it imply operational responsibility (on-duty) work, which I don't think is a given in DevOps jobs nowadays.
Did you even read my comment? None of your provided alternatives solve the issue of the current market being in demand of such a wide set of skills outside of the "normal software development" practice (whatever that even is), that labeling all of those under whatever title will get some people butthurt.
If its a matter of gatekeeping the "developer" status, go read some actual job posts with the title DevOps in them. Its not uncommon to come across proficiency requirements in at least one programming language (e.g. Go/Python/Rust), used in automation libraries, cli tools or whatever, which the applicants are expected to "develop". Or is it just constructions that can be developed?
Is reducing the amount of light that these panels receive likely to increase their effective lifetime? Or: Does total energy absorbed dictate decay of solar panels? Does that affect EROI calculations?
Light-induced degradation of silicon-based solar cells generally saturates above 0.1 suns [1] for the predominant mechanism of boron-oxygen defect formation; thermal degradation is also a factor [2] and likely to be unaffected by this geometry. But ERoEI for solar cells can be high, even in Europe [3] so, considering the roof replacement as a necessary cost regardless, these may still work out favorably, but at this juncture, only for special applications.
The amount of light does decay the solar panels. But it is not the only thing causing degradation. I believe the other large item for degradation is thermal. Operation at higher temperature induces degradation faster and there is some degradation from thermal cycling. So if the covering also keeps it cooler and at a steadier temperature then it is probably good. But the covering might also cause some greenhouse effect that causes it to operate hotter. So...maybe?
