BlahGod420

That's how I read it. NASA: "Yes, there is a non-zero probability."

It's a data problem. Not a language model one.

Wolfram alpha will literally answer.

They almost kind of do...

Me too, but I desperately want real metrics that demonstrate real work being completed against a project. Otherwise, my darker side fears it is the end of the industry as we know it.

Specifically I'd like to see us semantically identifying code objects and rather than doing commits in lines of code or whatever, print things out like "submitted a highly connected object" or "made amendments to some fields on a class" or "updates comments in a text file".

The current GitHub metrics reflect all of these changes as identical little "events of participation" but they're not indicative of the amount of work or effort put in to them.

Imagine getting your ass kicked to "We will rock you."

I'm flattered.

That's a totally meaningless sentence.

Given two functionally equivalent pieces of software, customers will choose the prettier of the two. That's all I want to contribute to the conversation.

It's banana hammocks.

I (respectfully) disagree completely. All source code is knowledge. All the content that goes in to a product when you're shipping it is knowledge. Managing a project is knowledge management. Managing multiple projects is knowledge management. Managing a company is knowledge management.

I've never seen a tool (other than, arguably, an Operating System) that does all of this comfortably.

WHAT THE FUCK AM I DOING EVERYDAY?

Likewise. It works for insane times too; I've woken up in as little as 3 hours when I desperately needed 8 hours. There's a bit of a computational alarm clock in our brains somehow.

All the developers want to be different, while all the end users need it to be the same.

To tell you if you're hot or not.

Is there a Buffalo Burger on Catalina Island?

Their intentions will matter a lot. Are they just collecting accounts or was there intention to move trillion dollar markets/start riots or wars/etc.

> No way will I toil for someone else if I had a choice.

You might collaborate, however.

Even in a first world country: 1. Be homeless. 2. Have diarrhea 3. Try finding a bathroom. Don't forget that many people in populated cities are going to take one look at you and prejudices are going to shoot up.

Now throw in Covid.

Welcome to hell.

Being homeless is excruciating no matter the country.

I am thinking about how a machine might expose a UI to an AR viewer of some kind. So, the scenario is: you throw on a pair of AR glasses and open the network-viewing app. I imagine being able to see UIs for thermostats, media players, audio equipment, etc. I suspect a Windows IoT device might get one closer to such a goal? Maybe not?

Does anyone have more experience with Windows on IoT devices in general? I'm curious about this - it seems like it could be a real game changer in general for IoT. But if it is already available and not actually doing much game changing, I'd be curious to know why.

Microsoft interview. I was just graduating college, and was super anxious walking in to my first interview. The interviewer realized that writing on the whiteboard was going to be awkward for the problem he was asking me to solve so he let me just sit down at his computer while he hung out to to the side and watched me work in notepad. I think that was the best way to do that interview, because the second I started writing code my brain flipped in to code-writing mode and everything relaxed. One of the better interviews in my career.

I think the idea is to determine whether or not it is indeed miniscule. Once people realize it is miniscule, they will probably accept it.

Personally, I think it makes accounting more annoying for businesses. I say leave the penny as it is, and move everyone to plastic.

I go to a major grocery store every day and buy a single diet coke. Self-checkout changed things a bit (less lines, generally).

> our heroes got to where they are by being unlikeable, not likable.

They really didn't though. At the most, their likability is insignificant. I'm reading the Walter Isaacson biography on Steve Jobs and I can tell you: Yes, he was annoying as fuck, but that's not the reason he was successful. If anything, it hindered him repeatedly. He got to where he is because he recognized the genius of Wozniak and knew to push in a way that Wozniak never would have (and not because he didn't possess the talent, but because Wozniak chose not to take leadership roles; it's something his father taught him and something he decided for himself).

Depending on the age of the persons involved, this could actually be healthy. When I first learned about logical fallacies I could not keep my mouth shut. Everyone was a moron and dag nabit I knew exactly why. After a few months of pissing everyone off, I settled down in to a "You can be wrong if you want," kind of mentality.

I'm about a month in. I decided to write a chat server/client to learn Rust by. Multiple side-projects sound like it would also be advantageous. Thanks for your comment.

Thank you for your response. I did figure out the problem after I took the time to slowly and methodically understand what the compiler messages were saying - that being said I was looking for places to ask for help if another week went by and I was still stuck so your resources are in my favorites list now.

As I wrote in another post, I came up with the solution while out walking around and it was like an "Ah Ha!" moment, I think things are finally starting to click a bit more. I purposefully chose to write a chat server/client because it lets me work through language features one at a time. There is some basic printing/reading of console input (though I did go full blown Cursive), some networking, threading, and lots of string manipulations. I am not sure when lifetimes will come in to play, but I have started reading about them and I try to think about the lifetimes of my objects when I write.

Yes, a week (no shame, damnit). The case was that I couldn't understand what the problem even was. I understood that there can be only one owner, but I didn't see how what I was doing was a problem. I literally looked at every error message it gave me and was like "so what?"

I think Rust initially suggested I implement the Copy trait or something, and so I had to brush up on traits and all that (which I did), only to find that my types can't have traits because vec<T> doesn't implement the Copy trait. So I abandoned that.

The problem turned out to be that I needed a minor refactoring. I think the issue eventually turned out to be that I was mutably iterating through a list reading from TCPStreams, and then trying to write back to those streams. So it was like a read_object_from_stream(stream) on each element in a vector, and then the next line was a broadcast_to_all_streams(message) (I'm psuedocoding).

The fix for me (when I finally came to understand what was happening) was to read_object_from_stream(stream) in to an intermediary vector (I named it cache), and THEN iterate through the intermediary and broadcast each item.

In my notes I paraphrased it as "Instead of doing a readwrite, I separated my algorithm in to a READ and then a separate WRITE", because the way things were written I was double borrowing.

You're absolutely right, I think your explanation is well written. I did get past the error that stopped me for a week, and yeah it is a case of tackling the same workload but in a different way (I guess 'the right way'). What surprised me is that the solution came to me while I wasn't looking at the compiler or source or anything, but was more of an "ah ha!" moment while walking around. This indicates to me that maybe I will eventually come to understand the borrow checker. Also that book is fantastic, I find myself regularly reading/re-reading it as well as "Rust By Example". Also the std docs are great to work through when I am trying to figure out a way to accomplish something.

I've been keeping an eye on crates.io stats - it's definitely booming. ~50 new crates a day (some of them are total nonsense/tutorial work/etc.).

I keep wondering about whether the hype is justified - I must be slowing down because I find myself hanging for long periods of time on borrow checker errors. One of the errors has stopped my progress dead for a week now, I swear it worked a week ago and then Rust decided that a borrow I was doing was no good.

I've also heard the borrow-checker is a common hold up for new Rust developers, so I keep slogging on.