We have a modular sofa system that has moved with us two times already and there are no connector or stability issues at all. Same for a large dining table and various bed frames.
Everything that has metal connectors with fasteners on both sides still works well on 2nd or 3rd assembly in my experience.
> I have to wonder what the difference is between a Tacoma sport and an AWD vehicle, I think it’s 2WD mode and maybe clearance
As a long-time AWD driver who entertains the idea of getting an offroad vehicle at one point, this is my current understanding:
AWD: If one wheel slips and starts spinning, all other wheels stop turning. You are stuck. Clever electronics applying the brakes on the spinning wheel can help to redistribute the torque to other wheels, you might get unstuck.
4WD: If one wheel starts spinning, only the other wheel on the same axle stops turning. The transfer case is locked, and the other axle still receives torque. If both axles have one spinning wheel, you are stuck.
4WD with one locker: If one wheel on the axle with a locker starts spinning, the other wheel on the same axle still receives torque. If both axles each have one spinning wheel, you can still move the vehicle with one wheel still receiving torque.
4WD with locker on both axles: If you manage to get stuck with all 4 wheels spinning you should reflect on how the heck you ended up in that situation.
The problem with reducing AWD to all open Diffs. Subuaru, Mitishbishi, Honda (Acura), Toyato have all sold AWD system with various levels of limited slip and/or locking diffs which are much more complicated than just applying brakes.
There is already a lot of illegal logging in Romania. Timber is a very valuable resource, and capitalism doesn't care if something is legal or not. As long as there are no revenue streams with less risk available, everyone local will have an incentive to exploit this resource.
I had high hopes for WSA as an enterprise platform, not as a consumer platform. Give enterprises an easy way to build one custom workflow app for mobile incl. offline support and syncing, then use the same app on your desktop. There is already great tooling for work profiles and mobile device management. Too bad this didn't get enough traction.
When you are comfortable approaching a stranger in a parking lot with a quarter in your hand, saying "Hey, I'll take that cart, no need for you to return it".
An even better sign is when that stranger declines to take the money and just asks you to pay it forward.
I've done both several times, in rural areas and big cities and have seen others doing the same.
People already thought about that problem when the World Wide Web was invented and they came up with Server Side Includes [0], a scripting standard that predates the Apache HTTP Server.
Looks like this inside the HTML document:
<!--#include file="header.html" -->
<!--#include file="footer.html" -->
Not many people use this anymore, but it is easy to share common markup and very accessible for people with just basic HTML knowledge. Major web servers of today still support it.
Because it's not about the lifetime of the person creating the software, it's about the lifetime of the software created during employment. The created asset can be used indefinitely after the employee has left. The salary is now considered the capital investment to create the asset.
At least that's now how the IRS sees it. Similar to buying machines to create a physical product.
Maybe they read all these articles about developers working in a feature factory.
The IRS should do a code review and see. That script you wrote at 3:00AM after waking up to your pager? That thing is going to be around forever and will have to be amortized over the next 2000 years. 5 years, you're getting off easy ;)
I expect that there will be some sort of code reviews by software experts in the future during a large scale tax audit. Because there is a distinction between regular software maintenance (including diagnosing and debugging) and an actual upgrade or enhancement. So it's not like you just capitalize 100% of the salary, unless it is clearly a support role. But even for testing and quality control, they make a distinction between before and after putting the software into service.
