unlikelytomato

From where I sit, I welcome the opinionated approach. I don't need my presentation layer to be industry defining. Htmx allows me to quickly make pages in a way that has never been simple for me using other frameworks. I am primarily a backend engineer though. Maybe there is some glaring weakness that I am missing, but I have yet to find something simpler for my needs.

After so many times being the youngster advocating for things like this to the 20-30 year experience crowd, I am not sure I agree that age or experience are really major factors in this context.

I am not sure how this is unique to a merge commit. The commit with the dependency change still exists in the main branch. The commit should never have gotten into main branch of it failed tests. If I take a positive action to rebase, I am accepting my fate from master anyway. If I merge into my working branch instead of rebase, that historical context issue only useful for that moment in time of reconstructing history and is not useful anymore. Once a branch goes into master, I want commits to main to have a 1:1 ratio of committed code for a task to positive action taken by a human.

It's a similar situation for me. I want to make things easier for my in-laws who strongly prefer speaking Korean at home. No kids for me yet but I plan to learn it with them someday. It's a fun experience because of how excited 장모님 is after hearing me say a single word.

I read this justification in nearly every thread that pops up git rebase. I feel like a full because I cannot think of a real world example when this information crosses from signal to noise. Generally, branches that are not ready to merge tend to have enormous amounts of noise commits. Is there a blog post or some concrete examples I could work through that illustrate these benefits? I feel like workflows dramatically different from mine are likely the source of my struggle.

What motivates you to learn Korean? I have been doing this recently too. I find it very slow to learn for me in my 30's

Perhaps they should also only allow users to plug in an external mouse if you buy the pro or Max chip.

I might argue that what you are describing is exactly why it's a bit absurd. It would be surprising to me as a user to discover such a limitation. If I didn't read about it here, I would probably find out after the return window and then be pissed that they took a stand on this particular artificial market segmentation.

My favorite is when I see a photo posted to Google maps "1653 days 5 hours ago"

The hardware and the software go hand in hand. Both hardware and software from non-apple products is inferior. I wish it were not the case, but here we are. I run Linux on my server & Windows on my desktop. The windows desktop has destroyed itself multiple times on forced updates. All my Android phones fall apart or have major features stop working around the 20 month mark. All my apple devices have lasted, never crashed, and never suddenly make me think about something other than what I picked up the device for. Installing Linux is trivial. It has it's own problems. Ultimately, that is why I've landed where I've landed. Sadly, Apple is the least terrible experience of all those options.

Are we to suggest buying Microsoft instead? Windows login and forced Microsoft accounts are a thing. I try to justify buying anything but apple for every purchase. Unfortunately, everyone else insists on making their products worse at a faster rate than apple.

I can understand what you are getting at. However, a more real world example should clear this up slightly. Both the variable name and method name are not conveying meaning in the above example.

  val underperformingEmployee = selectLowestPerformingEmployee();

which can be reduced to

  selectLowestPerformingEmployee().terminateEmployment();

But there are already a lot of strange state management issues with this code style. I would expect something more like this in the wild

  terminateWorstEmployee(){
    var employee = hrService.lookupEmployeeByLowestPerformanceReview();
    employeeTerminationService.initiateTermination(employee.id);
  }

When things are named and abstracted properly, it should be very clear what is happening. var conventions won't save you here.

Assignment from method calls seems to be the most likely place where this could POSSIBLY cause confusion. Maybe we can compromise on variable assignment directly from constructors? That seems to be the clearest example where the extra text is purely noise. It also causes a lot of line wrapping which indirectly causes even more noise.

I wish I could get a strong sense of the hype around null safety. Sure, I would like to have the extra expressive option. However, optional has been fine for me. I still barely use it. It has to be at least 3-4 years since I last encountered a null pointer exception in my daily java programming. I feel like there are plenty of other things that pain me on a daily basis that rank far higher on my asks for the language. Collection and stream ergonomics cause constant pain, for example.

This is a good point. I searched for "rename" today and the top result switched it to "name" instead. The TOP result completely changed the query. Infuriating.

I also love when my search is narrow enough that Google instead starts to return more generic pages for totally different programming languages instead of the smaller result set that matches exactly. It is very easy to observe as you explore a topic. At some point, you got a wall where any increase in search specificity seems to yield worse results than queries that helped you get to that point.

I am quite sure. The kinds of words in question would not even really make sense for "SEO gaming" to come into play. Typically, it presents with trying to match a word vs a phrase(I don't ever try to match phrases). I try matching smaller and smaller fragments of the word and still... nothing. I remember this working back when it was common for pages on gray websites to stuff giant blobs of text with juicy keywords out of view with janky html. Yet, somehow those pages were ranked very low and results were good. There is a clear degradation in quality.

Actually, it has happened with results that include hacker news discussions. I scrape through and expand EVERY comment on a 6 month old post and still find no partial or exact matches for my search keyword. It is very clear to me that Google has switched behavior. It used to flex on how awesome it was to bring you to an esoteric corner of the internet matching your exact query. Now, it tries to converge your queries into what it thinks you want(not what you asked for) and funnel you into large websites at the expense of utility.

This is not my experience. I search for exact phrases the same way I always have. Three to result does not contain the word I emphasized. This never happened before a few years ago. Now it happens daily.

Directly and indirectly.

Buying decisions from parents was influenced. Advertising influenced people. School lunches. What parents would feed other kids after activities. Habits of people "never giving it a second thought" were still being shaped by these forces. Even if someone only thinks about it a fraction of the time, it moves the needle. If my mom ate 10% more processed carbs than her parents and passed those habits to me, I was impacted. Rinse Repeat for 60 years.

I am not sure why this is a problem. Looking at the organization of the resources directory of every project I've ever worked on, I am not sure I want more opportunity for physical and logical concepts to unnecessarily diverge.

I struggle to understand this Goalpost. Thermals and power go hard in hand. Battery life and noise follow suit. Overheated legs and wrists are not much fun either. In any case, most other laptops in a similar form factor have equal or worse cooling. Thermal throttling shows up on laptop reviews a lot.

You can save on costs by spending less money on on office space in favor of team events.

You can also save money with hiring and retention due to happier employees.

Offshore is a reasonable comparison. Virtually all offshore implementations that I have observed result in at least one employee being forced into becoming an offshore orchestrator. Everyone now has to play telephone with the offshore dev through this channel. Even if they could contact them directly, you have a one day communication lag because you only get one shot a day to have a one hour sync with the offshore team. In bad scenarios, the offshore team has all communication channeled through the local team lead creating yet another layer and further communication lag. The point here is that engineering teams have been communicating how this issue is detrimental for years. We saw WFH work in a forced experiment (and had a lot of data about improved productivity). It is obviously not a direct comparison, but the egregious nature of blind positivity towards offshore and blind negativity towards WFH makes the comparison relevant.

What is the proposed alternative exactly? I like main vs test. I like isolating java files from other languages or templates. I like the src directory bucketing sources from other root project build files and output artifacts. I have a ton of wishes for java improvements but this is functionally not an issue in day to day work.

I am encountering this exact same issue. My instructions are repeatedly ignored and it falls back to a "preferred" approach after a single useful response. I have practically memorized the disclaimers attached to the end of every response.

I see. Is it fair to say that most of the issues area related to jdk included libraries vs language features itself? I also find a lot of the included libraries to be cumbersome, but I see these syntax improvements to be a welcome change in contrast.

What are some examples of these legacy features?

Overwhelmingly, I see complaints that java has been too simple compared to virtually all other languages. I agree that cognitive load is important. However, it feels really strange to me to suggest that java has reached the complexity of other similar languages. What am I missing?

Agreed. Along those same lines, I've ripped out just as much incomprehensible functional scala as I have "enterprisey" java. For every great idea, someone will internalize it as dogma. Dogma releases one of the duties of reflecting on what they are actually doing and if it is the best approach.

java has it's place. many things have a place.

sounds very similar to the arguments made against tests in a work setting.

Test as appropriate for your needs and goals. Adjust over time. There is no need to artificiality skew the balance in either setting.

I am not sure I agree Ocarina of Time falls into the category of "the dumbest stuff"

How could the OP be enjoying the feeling of Witcher 3 if they have childhood blinders on? Someone could draw roots of W3 & BotW back to Ocarina. It is reasonable to wish they made a modern Zelda that went down more of the W3 open world path instead of BotW style.

I don't understand this. Someone expressed feelings about two entries in a franchise with wildly different gameplay designs. The age of the player does not change the content of the game.

I might agree if math analogy was being taught by a mentor as a philosophy of living.

As a simple thought provoking exercise for growth of younger minds, it meets it’s goal. I think that scope is made pretty clear by his label.

If someone has a clean commit that is a district unit of functionally and passes all tests, why would that not have simply been committed as an independent change prior to continuing work? The only way a consistent unit of code would exist to revert is by stacking it on such a change.

I am not sure I have ever encountered a situation where targeting a single commit to revert would have actually worked(from a rebased merge). I would go as far as saying that git revert should be a nuclear option reserved for only the worst of situations(urgent PE hotfix?). If something is worth reverting and was missed by the engineer and the reviewers, it seems the like fix should also atomically contain the explaination with a test to prove the issue was fixed. Because of this mentality, I believe it has been several years since I have seen a 'revert' in the wild.

Maybe I am alone in the industry with my opinion. However, I have seen the same patterns unfold on many teams. ...A lot of concerns with switching to a dead simple git workflow that fade almost immediately after trying it. Just my experience (backend batch jobs, applications, and rest services).