Novashi

If you could build your own hello world WinForms program with some interactions, you had a reasonable chance of getting a junior position if you had some education.

I knew a guy who worked on a pharmacy application that calculated IV drug mixes that was a Visual Basic WinForms app and written with basically no knowledge of re-use or architecture. Kind of like web development where CSS was only applied via id's and so there was a lot of code repetition.

This is a tooling problem imo, and whatever tool that is should just output javascript that works on a canvas. There's no reason to cram another programming language like ActionScript into browsers by default.

Anything that installs and runs like Flash/AS is going to raise security concerns though. Please let's not repeat all that bullshit.

That's really more for market leaders. If someone stops by your site and starts comparing it to other businesses and their features, you're not likely to shift the market soon. Even if you do shift the market, you might not get the growth as your well-funded competitors copy your features. It'd have to be some ground-breaking technology that essentially propels you to market leader overnight.

What advantage does this give when we have SASS and other systems that support variables?

This is a spec going through draft-review-deployment so we can type 3 less characters?

Until people figure out how to hack them for profit. An AI with permissions to spend money on the company's behalf is going to fuck up eventually (and eventually in a major way).

Then it's back to human bureaucracy.

>The cold seems to fill me with vigor; love it.

Wouldn't that just be a "you're-about-to-die-adrenaline" kind of response?

Plus if you try to rename a dotfile through explorer, it won't let you

Then if you try to make a dotfile through powershell, it has a different text encoding than *nix, which some programs (git) rely on

Crypto itself isn't a scam, but its strengths also helps scammers thrive because a financial institution can't reverse malicious activity. This can be thought of as the same risk of loss as any investment. "If I convert to crypto, there's a non-zero chance my money could just disappear". This is (usually) necessary to take this risk into account when valuing crypto assets, so in a sense, scamming is part of crypto as long as crypto wants to be exchanged for fiat currency.

It's better following individual journalists via twitter or whatever instead of the organization itself for quality content for subjects you like to read about.

Personally, I use the main site just to scan headlines and see if there's anything interesting.

Everyone's biased, but I don't think I'm more of an objective thinker than a trained journalist who's taken classes to study it and write about it specifically. I don't believe many people can spot bias as well as they think they can just from a reporter's writing.

And yeah, they aren't experts at everything they cover. It's not a scientific journal. They should use sources for that stuff and if they don't, you should move on. Remember they also don't write specifically for experts so details get left out.

You can get your job done well but still be toxic and cause harm in other ways.

If they lie to you about that, can you do anything though?

>So, devil's advocate here: why not just require your ToS to state that if the user is from the state of California, that they are to not use the service and find a local alternative?

Silently redirect them to a similar-enough site run by a partner company that's based in another state/country.

"Process PII" is incredibly vague. You could define that in a hilarious amount of ways with the amount of complexity we introduce to our software products, especially with code we don't even write ourselves that widens your security surface.

This is especially true if you use a service that allows others to inject code into your code base. If NPM has a security failure that leads to a breach at a company, who is at fault? Both? Or only the company that chose to use the code? An NPM package might be processing PII after all. Does that mean NPM can never be held responsible for security breaches?

Secondly, your example would be backed up by historical cases and this law is brand new, so it is not clear. I'm not even sure how you guys can confidently argue that the new law ISN'T outright vague.

>You on the other hand are hosting a website with some sort of form that people input PII into.

That's what cloud providers do! If there's a spirit-of-the-law that is supposed to protect them, this would be a good time to write that in!

>You are still processing that data. Part of processing that data involves you shipping it off...

>The data is moving through your servers.

So if a random company gets breached, everyone involved from cloud providers to ISPs are also responsible because they facilitated moving and storing the data and they are just hosting code?

This is problematic. Cloud providers give you permission to publish code. I could position myself to allow another company to publish code on my popular website to collect data and my role is basically no different than a cloud provider. We don't have to agree that is what it's specifically for, I just need to give them access to upload their own code for whatever expensive fee.

>Process personal information of >50k consumers, households or devices

>Derive >50% of revenue from selling PII

So if I forward all of the data to another company outside of CA, does my company count as processing data?

What if the code that forwards that data is written by another company and I'm just hosting it on my site? Everything goes through their code and I'm paid to just setup a website to host their code.

Maybe I do collect info in CA but I sell the data for $1, but the company also buys some consulting services for the actual price of that data that I'm selling them?

>The government is desperate for people who can code.

Not desperate enough to teach people to code who want to learn though.

But I bet half the need is from mountains of shit code anyway. The contracting and procurement processes are fucked (source: friend who works in gov't IT contracts -- stay far away from any dev positions involving Dept. of VA).

Demand for good devs is going to be won by companies. We clearly can't even fill private sector roles even at these salary levels. I'm not sure how anyone can look at our really picky labor market with the government's lack of salary and perk offerings and think "yeah we can fill these if we just try a bit harder".

Government really needs a different approach to solve their staffing needs in this regard. They aren't competitive.

I hope I’ve got this right, but if the author is comparing typescript to a modern tooling environment, while there are technical differences, I may not trust those maintainers more than Microsoft at language design and support.

I don’t think you can write off the cost of learning all of those different tools in the non-Typescript environment. Typescript at least centralizes everything and I trust Microsoft to do good language development because of C#’s legacy alone.

I dunno if you guys have gotten feedback on this, but the difference between build artifacts, artifact feeds, and the output of some pipelines' tasks in terms of artifacts is really confusing.

I know it's probably getting translated to yaml from the old way which was a bunch of forms with build options, but we had some trouble with this. At the time, yaml releases were also still in development/preview mode.

One thing I'm going to miss is being able to discover things through the build wizard. Now it's just a blank yaml file and I feel that hurts the initial impression. I'd really like an option to build yaml files using the old way, but still get the yaml output for version control, that way I have all of the options and their potential values immediately available and I don't have to memorize and type everything.

There's a bunch I like about Azure DevOps though. Hopefully I haven't missed something really obvious.

Hands are wonderful for decoding thought into action, that's true, but for example, the brain can imagine images way faster than hands can paint them. A lot of people can be limited by their hands in gaming too. This is exchanged for learning some kind of encoding scheme that translates thought into bits. It's also really difficult, for example, to create 3D models on your phone just using your hands.

By sending bits, the interface changes and you aren't really burdened with UI navigation or UI mechanics like touch, drag, etc. Something like a phone would take on more roles that are currently filled by desktops and laptops right now.

But again, output isn't interesting. The low bitrate is just to illustrate that it isn't that interesting compared to the other direction (but I still think there could be useful products if the device is discreet and convenient enough -- I'm definitely not wearing a full EEG headset every day).

A product like that would be a good checkpoint in scientific developments of decoding the brain too. I think it's going to be a necessary step to develop before we get the other direction though.

>It's always a matter of balance

Depends on your language and environment, too.

I'm more comfortable inlining C# web code than unsafe device driver code.

But remember when you inline, you can comment around code and use more expressive variable names too. It's the same logical abstraction and similar levels of readability, just accomplished with different language features.

I think most of the bandwidth would be computer -> brain, not the other way around, assuming it can teach your brain to retain knowledge and show it images/movies. The only exception would be if we could significantly alter the perception of time, but I'm not really betting on that despite how useful it'd be.

Even if I could only accurately sample 1-8 bits/second from the brain, that would be world-changing. There are a lot of clever people who could stuff a lot of utility through 8 bits/second given you are paired with a powerful smartphone and a proper "UX". Clever encoding schemes and signals could be developed. Especially if you go for sequences/chords that are executed over 1-4 seconds.

Plus the brain would likely just act as an index to fetch info that is then replayed to you. I really don't need a terabyte in the form of neuron connections when storage and computing would be ubiquitous.

Brave claim: we won’t actually invent good AI until two-way brain-computer interfaces become useful.

We need to augment human intelligence to handle systems vastly more complex than we can do today. Specifically memory creation and recall, and information assimilation rates.

I want to highlight a third possibility that isn't discussed which is people who can talk about code, but can't deliver (or can't deliver well), but really want to learn how to deliver.

It's fine if you don't want to hire that person, but I'm really annoyed that they often immediately get labeled a bullshit artist in a lot of these threads.

Considering how many shitty positions there are, it's honestly surprising we don't reflexively go "oh, you never learned to do X well because you haven't been with a good company that can teach you to do X well".

>I feel like older user interfaces treated me like an adult.

They did, because usually only adults used PCs.

Now kids through elders use PCs and there's nothing wrong making the UX more friendly to people unaccustomed to working in tech.

It's in your head because I think you're missing the roles PCs now play for everyone in society.

>I always had a bit of a moral dilemma working at Netflix because my goal was to get people to spend more time watching Netflix, which I didn't really think was good for humanity.

Ah, come on. We need entertainment. Netflix is far and above what cable companies have been doing for a long time in terms of effort and not being scummy. Bringing joy to people is good for humanity. Don't let it weight on you.

The US Government is currently dysfunctional, so at least someone is making affordable housing.

I think we’ll see robust shipping routes before completely self-sustaining colonies. To the point where missing 2-3 shipments isn’t a huge deal.

Tell them you have multiple residences and declare one as your primary.

I know that shit works because rich people do it for taxes all the time.

If you gave Gitlab a PO Box address in the Bay Area as your address, wouldn't they have to pay you Bay Area salaries without you paying Bay Area rent?

If not a PO Box, some other proxy by which you aren't genuinely living there. Maybe just a short-term roommate lease situation?