skysight-inc/HackerNews huggingface dataset:
1.5x the features, 3x the code would roughly result in 1/3 development velocity, 3x bugs, and 3x incidents going forward.

Even assuming all your developers are magically given a solid understanding of the new code, all remaining velocity will be entirely consumed by bugs and incidents. No more feature development will occur.

You could try to grow to outrun the code debt you've just acquired - but that's what literally every start up tries to do, and less than 10% succeed.

The most likely outcome is that the company would enjoy a one-time massive feature feast before slowly dying over the course of 5-10 years or so.

Great if you're a founder looking for a quick exit or some other position that is super focused on short term growth, I suppose.
> how should I demonstrate skills?

Your list is correct. Any/all. Open source everything and if you make a game engine, make games in it.

> is engine programming less exploitative?

Depends on how you mean. Working in the games industry usually involves dealing with the same handful of warts regardless of where you go and what your title is. The exception is depending on your seniority/role/specialization, those warts may manifest differently. As a junior engine programmer, you're still going to have to deal with the same things any lower ranking games industry person is going to have to deal with.

With time though, engine programmer becomes one of those specs where the money is insane and the job security is better than usual.
Seniors and the disabled don't have to pay property taxes in California if they don't want to. The California Tax Postponement Program protects them. It's a fine policy.
Tiny Birds in Japan Look Like Fluffy Little Cotton Balls
Can you explain in what way is that different from e.g. C++, where a compiler will take "-std=<C++ revision>" parameter which chooses the "edition" of the language?

And even link different versions together?

Because it sounds like Rust uses the same approach with the benefit of not hitting all the problems this causes... yet.
It would be easier and make more sense to just enact a road tax on tires.
Maybe isolation would be another variable that correlates to extreme altitude regions
They need to grow up, especially Elon. What happened to dealing with things rationally?
Similarly:

"We are spending 50$ per month just for one test in our code. We could cut it down to 10$ if we wanted."

"How many hours would it take to reduce the spend? If it's more than a couple of hours for a senior engineer, then it's not worth it."

We kept spending money on this inefficient test and it was the right choice.
I think that taking the bargain would depend on the project... If it was software for a product that was on the market and had a lot of competitors, then it's a good deal as it would allow you to get ahead of the competition. Or, say, it was a new market and the features allow you to establish a strong lead. I'd definitely take the deal and then set up a team to do a refactor/rewrite or something.

If the deal was used on internal software that already did it's job relatively well, then it's probably not worth the long-term trade off.

I think that your larger point still stands, that most business people don't care about software engineering issues, but just want features, or solutions to problems, or whatever. Negotiating those issues in a business can be tough.
NEORL - python library for large-scale optimization problems
very common with flash based doodads. check out what cable tuners are drawing when 'off'.
I love repurposing thin clients.

There were a few gens of HP thin clients that always seemed to have their mass storage devices die, and end up on eBay for peanuts.

I picked up a handful of the 64-bit CPU ones and set them up to boot diskless with LibreELEC to act as Kodi stations for eg. media streaming and distributed video players on TVs on my network.

They boot quickly enough to not need to think about them too much, and it was easy to NFS mount my media library from my main servers.

Kodi controller apps from my phone and things like AirPlay/TuneBlade to cast arbitrary stuff to them has been a real quality of life improvement for my family.
There's no type checking on function dispatch unless guards are explicitly added. The arity dispatch for functions captured into first class is done at compile time and require explicitness. That said, I think you can create your own dispatch macro that's probably as efficient as possible for doing what you proposed.
FYI they're not hiring in the EU (or Europe?) due to the time zone difference.
This. I saw the post and had a mildly customized Jitsi running on my docker host on Hetzner within 2 hours. I'm amazed at the performance and stability of the Jitsi.
Yeah, yet it doesn't matter to me, I don't even know what they are about.

Likewise, despite crates.io, Rust is missing lots of stuff I miss from Java, C# and C++.

Plenty of stuff isn't there yet.
Stupid and Funny products make the most money
Are you having trouble marketing your product? Make it funny. Doge is funny. That's why Musk loves it. Here's an example of a product I recently launched that got a few hundred pre-orders. It's funny, a bit stupid, but also quite useful, especially for females.

PeeSport pee bottle helps you pee anywhere. The attachment works for men and women. It's especially useful for camping, road trips, hikes, festivals, etc.
I have spent a lot of time thinking how to respond to this.

I don't have an adequate answer.
Ads appeared when I used your/that channel before the video started, sometimes, there are some that you dont have control over
Power utility bill as well for home charging.
Sadly I did read it.
I would argue that we don't know yet whether the system has worked or failed here. No amount of high idealism written on parchment paper can keep small people given power from using it corruptly. What matters is what happens then. If everyone were to shrug this off and say "well of course, that's just the way things go in America", then yep, I'm totally with you that this is really upsetting.

But I don't think that's what's happening here at all. I have seen this story all over the place in national news. And what I think is that the mere fact that any of us living nowhere near this little town are aware this happened means that the people responsible for it are in deep sh*t. I think they'll be made an example of. I think the state and federal justice systems will be racing each other to make an example of them.

And if I'm right about that, it's not an upsetting indictment of the system, it's an affirmation of its success.
Calendly Sued in CIPA Class Action for Using Heap Tech
Abusing GOAT mobile API for data scraping
This is basic editing functionality, a core part of the purpose of the application. You can call being able to edit a score "a feature," but it's hard to imagine what is more fundamental to it.
I used to work in the transit industry. I can describe the problem and the solution with enough paper and a couple hours. But to actually perform route scheduling, we used a whole bunch of iron @ AWS.
Doesn't this depend heavily on the scale of the company you're at?

At Google taking this is a no-brainer since for a myriad of reasons, feature development is slow.

At a 6-mo startup this much tech debt this early on might just kill it.
Microsoft Edge for Business FAQ
He didn't found Tesla. He didn't invent the EV.

SpaceX is doing great work. That same talent would have been available in the market for hire by anyone if SpaceX hadn't been around.

He didn't invent satellite Internet connectivity.

I don't understand this hero worship that goes on in the tech sphere for a known grifter who thrives on Daddy's money and taxpayer subsidies.
If you can convince someone to go back to 1960's models and pay for software development where planning is literally measured in years for what gets done in a few months today, more power to you.

I don't mean to be completely snarky, but that's the reality of it.. most software isn't a skyscraper, or even a medical device of vehicle.. most software is CRUD with some business rules thrown in. A given system goes down it's an inconvenience but nobody actually dies. You aren't going to hire a team of architects to design and review a dog house.

And if you think the latter can't apply to physical things, look at some of the case reviews from Gamer's Nexus... many are literally unfit for their own duty. A recent NAS case review on a different channel showed it had to be Dremel modified in order to even work. Similar for the NAS case recently used by DeBauer. It actually happens plenty with physical goods.

The comparison really bugs me. It does indeed bug me when there's a direct connection from the entertainment system in a car and the drive train, for example... that isn't abstracted away via physical device + api. Similar can be said for some decisions with Aerospace equipment. In the end, can you name the engineer that is never working again because the accelerator in some car models tended to get stuck? I can't.
That anecdote about the Japanese 747 near miss that required a dive so hard it sent a drink cart through the ceiling and injured nearly a quarter of the crew and passengers is also shocking. That's the reason you keep your seatbelt on even when the captain turns off the sign.
It's not taboo to say so, even within the Rust community. It's something that will happen eventually. You might be interested in reading https://without.boats/blog/revisiting-a-smaller-rust/
By the same logic, fare evasion is "metro company's problem to deal with".

It technically is, but if someone makes a programmer's salary and still jumps over turnstiles, I consider it a big red flag over their personality.
> So, as long as you write Go in malloc-less C-style (which, admittedly, is a non-insignificant restriction), your program will be able to run just fine forever.

What happens if you write your Go functions in this malloc-less C style and they have to grow their stack? Doesn't this mean the old stack is now leaked memory?
"1000 songs in your pocket" is not a spec. It was a selling point. Songs, of course, are variable length things, so it's a marketing statement, not a spec. At the time the only way to get this many songs in your pocket was with massive pockets to hold a MP3 CD jewel case. Jobs didn't just build a faster horse when it came to the iPod. It was engineered purposefully to satisfy that desire.
When I worked as a lifeguard in high school (2003-2006) at the high school indoor pool we had an AED that hung in a box attached to the wall.

If I recall, I think we practiced with a dummy one during lifeguard training, but they are more ore less automated and a voice walks you through the process. I think most people would be able to use one successfully, without any prior training.
I always thought a 7-bag where you reset the bag when nearly empty was a good compromise (where "nearly" can be selected for how much randomness you want).

Droughts are technically not prevented, but odds of them do go down quite a bit.
That system already exists in Hawaii actually. There’s lots of land you can’t own as a non-native.
All bag-of-words models use some kind of word vector - for a normal logistic regression / naive bayes, say "spam" and "spammer" are first and second indexed words in the vectorizer, then their word vectors are like [1, 0, 0, ....] and [0, 1, 0, ....] (length = vocab size). For both logistic regression and fasttext you get the 'document vector' by adding up their respective word vectors before applying a final linear projection + softmax to get the class predictions [1]

The insight of fasttext is to notice that these high dimension, unit vector word embeddings aren't an ideal way to learn - since they are orthogonal, during training time, a datapoint giving signal between the "spam" word vector and the label gives you no information about "spammer", or indeed any other word. Explicitly modelling and learning word vectors helps with this as now these are two points in a vector space that can be moved relative to one another.

[1] this remains true for LR if you rescale the vectors using e.g. TFIDF or use the hashing trick (a la vowpalwabbit).
I think the main issue with comparing past principles on governing and current ones, are the technological differences. Communications around the world take an instant. A missile in Wisconson can be sent anywhere in the world to destroy a city within probably a half hour. Past political philosophers have nothing to compare this to. In their time, a revolutionary force really was on an even keel at times with the military of the government, back when the ordinance carried by each was more or less the same, the communications technologies used by each more or less the same, and the resources such as food and firewood to draw upon for supplying a force being more or less the same surrounding villages near the battlefields.

Today, the US military doesn't need to consider anything about the local resources available, they can just airdrop in food and water while you and your band of rebels slowly starves if you can't live off the land. They can out communicate you and coordinate fighting on the land, sea, air, and space, while you might have a short wave radio if you are lucky that they are also probably monitoring. They can of course out gun you, without even sending boots into harms way though probably dozens and dozens of different technologies and permutations of these technologies and strategies.

I don't think Plato could have conceived of a predator drone, or a military satellite, or an aircraft carrier, or a nuclear submarine packed with ICBMs. The balance of power has never been so historically lopsided with who controls the technology of contemporary war.
> Owing to the federal government-prodded transition to electric vehicles (EVs) to combat something called “climate change,” ... In this case, said birds are: getting rid of gas-powered cars, inventing for themselves a brand-new revenue generation scheme, and instituting even more tracking power to make sure the peasants behave themselves.

Lol, wtf is this website?

If you go to read the actual reporting, the Oregon administrators are much more even-keeled about the thing:

> "I understand that concern, but anybody that has a cell phone — the ability is already there for it to be tracked," Lively said. "Your cell phone is probably the most trackable device we own and almost everybody has one. But there are several options. We made options that people could just annually, monthly turn in their mileage. So they can tell us where the mileage started, where the mileage didn't, so that's one way they can report versus reporting from the car — so there's several ways in which people can report their mileage.

> "But the key in doing it automatically is the systems now in place allow us to know whether they're driving on state highways or private roads, because our goal isn't to charge you for driving on private roads but only when they're using the state transportation system."

https://www.kgw.com/article/news/local/the-story/odot-gas-ta...
I randomly caught a serious fire-risk recall on a relative's car a while ago, and afterwards thought... there should be a .gov app for that. Well, there is!

Anton Yelchin was killed by the laxness of a major recall on his Jeep. This is a real issue which can largely be solved by an app like this.
Yeah.

I think a nice little "Hey I saw this that doesn't match this design doc here, but this all looks good regardless." type reminder would be ok. Obviously being diplomatic / soft skills is huge and the google doc addresses that a great deal.

But yeah especially if this is a non-trival change / lotta work ... not time to re-invent the wheel.
Based on the discussions I've seen, Go2 is considered to be the name for the process of extending the language, not an exact release version.

With that said, the label seems to “work” by allowing people to first think of a backwards-incompatible way to solve a problem and then, possibly, arrive at a much more compatible solution in the process of discussion.
It was launched earlier this year. They say that "thousands" of Channels have access to the feature but who knows when the feature will be available to all channels.

https://blog.youtube/news-and-events/multi-language-audio-mr...
Expanding to Italy, Spain, and Belgium, and 13th Gen Intel Core Now in Stock
"connected" vs "compatible with"

Tbf. 25% connected is huge. If you just jump into your car to quickly do groceries or pick up your kids, you may not be interested in connecting your phone to your car, even if you really like that feature. So there could be a natural ceiling for the "connected" number and 25% feels getting close to that ceiling actually.
NZ has the advantage that all vehicle miles travelled are within their jurisdiction. US states, Canadian provinces, and EU countries all have drivers travelling significant distances out of jurisdiction, likely resulting in inefficient taxation. With a simple odometer reading Utah would collect taxes on road miles that took place in Colorado, whereas Colorado has no mechanism to collect taxes on the wear and tear on its road network by Utah citizens.

On the other hand, the idea of having a government tracker in my car all the time is beyond icky. I'd much rather overspend a little via a simple annual odometer reading than have a government agency with access to detailed location logging.

A federal annual odometer reading that then distributes funds to states based on vehicle miles travelled and road network size solves the jurisdiction problem, but would never fly in the US as federal overreach.
If the agency finds something they don't like they'll just come up with a plausible way to arrest you for something unrelated.
> Implicit arguments! I'm more and more convinced that this form of controlled dynamic scoping dynamic scoping should be embraced by more languages.

This might be an odd comment, but this is sorta similar to React's Context mechanism. For what it's worth, it makes a lot of things easier but it can definitely also add a lot of surface area for complexity. Although it's certainly better than relying on globals all over the place.
Very well said.

I had a similar conversation as a new-ish fractional CTO last year. One team was working on a new CRM product that was effectively alpha-level software used only internally. The team had become terrified of shipping and breaking something and was horrifically risk averse. For a new release that the team was going to delay again at the last minute, I got the CEO on the release call and asked him what would happen if the release completely failed and it took us an entire day to get the product working again. He replied “Not a big deal. The users would just write stuff down like they do today and key it on tomorrow. It’s not like this has enough features to be critical or anything”.

The team was completely stunned. It goes without saying we did the release, found a small mistake, fixed it, and life went on.

Teams really do have understand who her users are and criticality of the software.
Too late.

Now are you willing to abandon the rest of the other companies using your information to train their AI models? (Looking at Google, Microsoft (GitHub), Meta, Instagram, etc)

Now should be the time to self-host then. Whether if it is a GitLab, or Gitea instance for Git, or a typical Mastodon server with a single user that controls the instance for full ownership.
All Gods started out as abstract entities, and had concrete traits grafted on them later. Why isn't anyone doing it with Allah?

But it is just easy to dunk on "sanghi" without any reflection on the double standards and prejudices that permeate the society.
That is not a problem; that is part of the solution.
I really wish TGM3 was more popular, and got a good port to modern consoles. It is so incredibly unique and in my opinion far more enjoyable than modern Tetris. The one thing they need to fix is the completely inscrutable “t-spin” notification that appears
It’s telling you seem to have no consideration for what locals want, but instead only consider the pov of the outsider who feels they have some right to live there for cheap.

By the way, the more you develop it, the less tropical it is.
> why does any language need a breaking change ever

that's easy - because it's impossible to design everything right right away, and for many things also impossible to make it right later without breaking compatibility, while those improvements are valuable

New language for each breaking change also doesn't make sense when there is a lot of continuity
This is backwards and why I think mandatory code review is a waste of everyone's time. Nobody should be writing code with the goal of passing a code review. They should be writing code that solves a problem and adds value to the end product. If you're writing a system that requires 5000 lines of code, it's a waste of your time to figure out how to break it up into 5 or 10 PRs (which might actually make it harder to review, since chunking it up would remove context).

I understand that code review has a place in enforcing code quality and training junior programmers. Here's what I would suggest. When you hire someone, make sure somebody is assigned to reviewing their code for the first few months. Once they've demonstrated their ability to write good code, from that point forward you trust them not to screw things up. In addition, foster a culture where people are open to criticism and proactive about fixing things. If someone sees a problem with someone else's code, they can either let them know informally, or just go in and fix it themselves. I think this approach would lead to much less red tape and much happier and more productive programmers.
> Using a different methodology, a similar, strong positive correlation between altitude and suicide rates has recently been reported by Kim and colleagues, (2011) using all counties in the United States as well as all 233 counties in South Korea.

I assumed culture was a large component to this, but I don't know enough about South Korea to compare its high altitude people to those of the US. Maybe it is something environmental?
> comment on which parts of these work well and which don't?

I don't think there is a visible distinction between those parts that work/doesn't work. In fact, most of the cases each practice has pretty strong rationales. The problem is, when you take everything as whole, its cumulative complexity and cognitive overhead tends to go wild and almost no one can understand the whole stack when its original writers/maintainers leave the team.

In fact, this might play a certain role of the Google graveyard narrative; it's not because its engineering culture is bad, but sometime its standard is too high for many cases so it's nearly impossible to keep it up for newcomers, especially when you have external pressures that you cannot ignore. Even if you make an eng team of 3~4 people for a small product, they'll likely suffer from tens of migration/deprecation/mandates over years.
> If Go 2 won't break Go 1 programs, shouldn't it be Go 1?

Yes, that's what the article is saying.
Test Automation with ChatGPT
Wildfires Kill People
Django isn't just about the ability to programmatically stick together things to make your query or the migrations. It's that, combined with tools that help you debug database issues, and most importantly the patterns that it imposes.

As a Django developer it's straightforward to go from one Django project to another, which isn't the case with other stuff as you don't know where everything is going to be.
Some teams in Cloud suck but the core engineering teams have some top talent and solve some very hard problems. Keep in mind Borg and Spanner are both “cloud”, but so are many field sales teams with an average tenure <2y
K8s,

TPU

Colab

Tensorflow

hmmm.
Most sale prices are bogus, but 1 tweak could help – Futurity
Brooklyn in 1980s was a decrepit criminal hellscape, no wonder prices were so low. I’m quite sure you can afford to buy a place in Detroit or Indianapolis, maybe in 40 years one of these will turn around like NYC did.