moistoreos

This seems supremely stupid, lazy, and performative. We know how to build custom neural networks to perform much faster with higher accuracy when custom built for a specific task. What was it doing mid-surgery? Googling "brain size of mice"?

GASP!

> develop proprietary software

This is a weird strategy to stake future IP value on in the age of AI. With competent and fully qualified team, anyone should be able to reverse engineer this idea and build a roadmap for their own implementation. Especially in the world of open source.

Aquihiring also requires the personnel hired to... actually stay with the company....

Unless you dangle HEFTY stock options with incremental maturity dates, nothing is else is keeping them from leaving.

Pretty sure the second rectified the first.

PREACH. I have no idea why THIS has become the standard for illustrating model capabilities. It's endlessly frustrating when that was the initial objective for all these models, but, became increasingly clear over time that none of these models were ever capable of getting the desired output for complex software on the initial prompt.

The reality is: - business rules change - ideas for improvement may arise from the initial prompt - updates to submodules/functions/configs/secrets are BLOCKERS ... etc.

One shot prompting for the expecations of complete software is seemingly more and more a show of incompetence of the use of this technology. It's like trying to make my toddler eat a ham sandwich from the peanut butter & jelly I put in front of him.

This sounds like a process + human problem, not a technology problem. To me, it sounds like your team lacks discipline and competence. Sorry bud, going to categorically disagree with your sentiment that git is terrible.

I FEEL this. It's empowered lazy devs to defer thought and accountability. To some degree, I understand. It softens the imposter syndrome feeling one can get. But, I see it as a character barrier; not a moral one.

Ah, yes. California. Where large swathes of costal areas hover between 60ºF and 80ºF. We are talking about Nevada the weather of locality matters and where it can be supremely hot.

Hey bud, do you happen to know when the demand for power is the highest? It happens to be.... gasp.... when the sun is highest in the sky.

Just take a look at ERCOT's website: https://www.ercot.com/gridmktinfo/dashboards/supplyanddemand

Dude, the funding of USAID yielded so much soft power for 0.3% of the federal budget. You indolent, unempathetic monster.

You want to cut the federal debt, where should we look to where the wealth has been hoarded?

Great idea. But, I'm will to wait for the AI sloppified OSS version of this.

You could literally eliminate homelessness, world hunger, and fully pay health care costs in that same timeframe with much less cash.

If you dig elixir's LiveView, you can do something similar:

https://news.ycombinator.com/item?id=36371907

llllllllllllllllllllllllllllllllllllllllllllllllllll

`pass` is an excellent case for storing passwords locally that you don't need to carry with you. I use a lot of login credentials for work on `pass` and it works great. If/when I need to upgrade laptops I can just back it up in git.

I use BW for all my personal stuff because my wife and I use it.

I've been giving some thought to this. I wonder if an iPad would suffice in front of the tv and just ssh into a Mac Mini for dev work. I'd love an iPad but I can't justify it either because of the limitation of hardware capabilities. I also don't really want to purchase two machines just for dev tasks and travel. But, I think having that kind of lifestyle will be expensive no matter the approach.

All this drama over an email. What's categorically worse is Riot forcing kernel level anti-cheat unwittingly to non-technically literate users.

> In Japan, we will implement a next career support program. Details will be communicated separately.

Why not do this for every country? This type of support should be required for mass layoffs.

I understand the strategic impact of such large decisions but I don't understand why these types of programs can't be implemented in the 21st century even if laws need to necessitate such programs existence.

It also doesn't waste an entire evening obsessing over a refactor. A lesson I've learned to do with refactoring my own code.

This experience has zero to do with clean code. The title is very much a misnomer and incredibly misleading.

This is an elaboration on the experience of abhorrent engineering culture at this company. From people who can't professionally speak with one another to a manager who cannot seem to effectively solve the core issues underlying the problems at the company. Instead of a moment of reflection on HOW to improve the root cause of the problem, it feels like they're kicking that can down the road.

Two things I'd like to point out:

1. It's nice to see some form of humbling commentary from the author; albeit, I don't think it targets the right solution to the problem.

2. I still think there's a lesson here for any org to digest and that is communication is such a vital and integral part of "a raising the tide lifts all boats", so to speak.

> “If we even got a couple percent improvement in productivity, this would be worth it. And our goals are actually to do quite a bit better than that.”

So your engineers will get a productivity salary increase, right? RIGHT?!

I wouldn't expect this to ever happen post-Citizens United.

I am reminded of a conversation on Security Now where Steve Gibson recommended that each website that has traffic inside the UK to have a red banner at the top of the page to sentiment of something like, "The UK Government is forcibly watching traffic on this website."

Watch how quickly that turns the conversation around.

This argument lawmakers have here is entirely built upon the straw man. I understand the deep yearning to protect children but all this won't make the criminals stop using the tools that are currently legal. They will continue to use them. Making them "illegal" won't make them stop using them because they can still be acquired.

The mnemonic bindings I get from my config are an integral part of my workflow and super easy to add/update/change. But the primary reason for using Neovim is I don't have to leave the terminal. I switched entirely to the CLI a few years ago and I am more productive here.

If I wanted an IDE, I'd switch to the terminal version of Emacs.

This is less of a problem if there's a culture that provides positive & honest paired programming w/o judgement on a regular basis. I try to do this, not just to glean business context from other engineers, but so I can learn from others.

For this to work well, toxicity needs to be nonexistent. I would even advocate for a "no tolerance" for toxic comments/behavior from peers/colleagues.

The quality of solar tech varies immensely and it will likely take regulation to address some of these issues. But I do not think this is the primary concern here.

We put solar on our house and did some pretty rigorous research into the tech precisely because of this concern. After spending many nights/hours understanding the tech in this industry, I can confidently say it matters less about the current generation of solar tech. But, while the degree of quality in solar products exist, what really matters are the contractors that install it. I did not read the articles and I don't want to claim that there's direct causation by contractors, but if I were a betting man, I'd easily put money on the quality of the installation as opposed to the actual tech provided.

/remindme in 10 years

In all seriousness, YES! File sizes are not getting smaller. If the bottleneck of data transference were my hardware, then we would live in a data utopia.

Imagine the size of files for the last 20 years and you could probably do a relatively close comparison for the next 20. I would say they have future-proofed their system for a long while.

I would also say that with the addition of IoT, there is going to be a LOT more casual traffic across the wire in people's homes/businesses.

> managers use a “keeper test” for each of their people

Gross. Enormous red flag that is indicative of a toxic culture.

I live in the terminal. If that is not open source then I am not using it.

This is a hill I will die on and it sets terrible precedence for other core workflow tools.