Yeah there are plenty of companies that don't do code reviews still to this day. I worked for an ad agency for a bit and we were still using SVN (afaik they are still using SVN for many projects today). Everyone would just push code straight to trunk with no review process.
I created a cool little easer egg where if you clicked in the bottom left corner of the browser window and dragged in a circle, the site would flip upside down. A coworker and I also photoshopped some of the client's imagery that was used on the site and hosted it on another domain. If you typed a variation of the Konami code while on the site, the images would be replaced with our meme-ified versions of their imagery. Even if we had a code review process, none of my coworkers would have even noticed that little bit of extra code in the mess of jQuery spaghetti that was their codebase.
The only difference between the two in my mind is that the output from a transpiler is likely going to have a ton of bloat, require additional transforming, and be a much larger amount of code than the sum of the inputs. Whereas something like the Closure Compiler actually optimizes and eliminates dead code. They are the same thing though from an ideological standpoint though.
I mean, early PCC didn't have data flow analysis, or eliminate dead code, and was known for head scratching levels of stuff like spilling registers on the stack that didn't need to be spilled. Was the c compiler of the 1980s a transpiler?
The latest MacBook is essentially mobile hardware with desktop peripherals and software. Seems like the right way to go rather than bloating a smartphone with desktop software given that the amount of people who want their smartphone to be their only interface to everything is likely a very small minority.
It's not in the best interest of the wineries or the distributors to advertise that unless legally obligated to do so, which is why it isn't really common knowledge. The whole "natural/organic/non-gmo/no-pesticides-added" labels common in the food and beverage industry would likely cause unwanted contrast to wines labeled as "from concentrate".
To be clear, there is nothing wrong from being "from concentrate", other than probably a huge PR campaign by major OJ companies to make you think juice "not from concentrate" is somehow more healthier or something. Fun fact is those are the same PR companies that Kellogs used to coin "breakfast is the most important meal of the day" which still as of today many doctors argue that actually your last meal is the most important because as you sleep your body regenerates and besides it will be left for the time of your sleep (8 hours?) without food or water.
Anyways there is nothing wrong with orange juice from concentrate. Its always been like this: 60% OJ concentrate, rest water. As that a good healthy ration. "Not from concentrate" is a PR gimmick. Think for yourself: A glass of "not from concentrate" orange juice would have 4-6 grown oranges squeeze to fill it in. What was the last time you ate 4-6 grown oranges at one sitting, and do you really believe thats healthy? If anything it makes your liver works super hard to put all that extra vitamin C into your bladder so you can rush to tha bathroom.
Does the from concentrate stuff have anything different other than some water removed? One you add water back in isn't it the same as the not from concentrate stuff? I.e. Still the same 4-6 oranges no matter what?
It's the same 4-6 oranges if you consider having a sterilized orange juice concentrate spend 6 months to a year in storage and lose all of it's flavor "the same" as a freshly squeezed orange.
For most commercial orange juices, all the flavor is engineered with artificial ingredients. I'm pretty sure that the only reason they still bother with oranges is legal requirements.
2) Don't even try to talk about project management frameworks because you don't understand them
3) Don't ask me if I have experience in something that isn't on my resume
4) I don't want your 3 month .NET contract in Cleveland even if it "may have the opportunity to go full-time"
5) Get both my and the employer's salary requirements up front so I don't call out of work to spend the day interviewing, being told by the company that they absolutely wanted to move forward, and then find out that my salary was way out of their range.
6) If you name drop a renown company and then start talking about how I should instead interview at some startup for helping people put their mom in a nursing home, the conversation is over.
7) APIs isn't a skill
8) Save the corporate kool-aid for the product owner candidates
9) Just because you got my phone number because some job board sold my info to you doesn't mean you can call me
10) My resume, LinkedIn, and any other job board profiles have my location listed. Don't call me at 6am PST!!!
11) Stop hoping that I am well. I'd be much more well if I wasn't woken up at 6am by your ass.
12) Who do you honestly think is going to work for a company that requires .NET, Java, Python, Angular, React, and "bonus points for Rust experience"?
I created a cool little easer egg where if you clicked in the bottom left corner of the browser window and dragged in a circle, the site would flip upside down. A coworker and I also photoshopped some of the client's imagery that was used on the site and hosted it on another domain. If you typed a variation of the Konami code while on the site, the images would be replaced with our meme-ified versions of their imagery. Even if we had a code review process, none of my coworkers would have even noticed that little bit of extra code in the mess of jQuery spaghetti that was their codebase.