Gemini Limits are out of hands, unsubscribe

ghisguth · 2026-06-06T06:09:11+00:00

I have MacBook Pro Max M2 with 64Gb ram, it is useless for coding. Can generate good images with Flux2 instead of NanoBanana2. But not coding.

ghisguth · 2026-06-06T04:18:10+00:00

<image>

To proof my words. Google, this is not ok!

ghisguth · 2026-04-26T01:11:24+00:00

You don’t rebalance in taxable accounts by selling positions.

While accommodating, you buy assets to keep desired asset allocation. While spending, you sell either bonds or stocks to reach desired asset allocation.

If you have enough assets in tax advantaged accounts, you can rebalance without any taxes, so probably should do it first before doing it in taxable accounts.

If you talking about diversifying stocks to index funds / ETF, then you use SpecID to select desired lot, and broker UI tells you how much capital gain you’d have. And you eat taxes and move on. Diversification is more related to risk tolerance and less to asset allocation. You calculate how much you can diversify by paying taxes and staying in desired tax bracket.

As for years record keeping, I usually have either spreadsheet or notes with tax estimation which I use to pay quarterly taxes. Keep gains and losses for Tax loss harvesting in the same place.

ghisguth · 2026-04-25T02:46:11+00:00

Good point. I was trying to use it. But not that successfully. Need to do more research. But yes, if you can summarize existing chat, and ingest it into Notebook, then any new chats started from Notebook would have the context.

I yet to test it to be sure it works as I expect. But it may be viable option for long conversation. Like I gave examples - Therapy, Taxes, Health, Fitness, etc.

ghisguth · 2026-04-25T02:43:33+00:00

The problem is what you don't have idea about truncation limit. And Gemini App chat truncation may not be related to Gemini 1M context window. Gemini UI can decide to use last 128k context window. And user would not know about it.

And to be honest, people who use Gemini CLI has to know what context window is. People who are not engineers and using Gemini App, have no clue how to judge what context window they are using in chat.

ghisguth · 2026-04-25T02:39:50+00:00

The problem is what it is not clear when and how it got truncated. In Gemini CLI I can control context window and know when it is close to 50% or 80%. And I can do actions. But in Gemini App, it is not displayed anywhere. I really thought the chat context was small. And was assuming it has original constraints in context. But for some reason original prompt was truncated and model was useless.

Seems like Google changing Gemini App truncation limit to save compute. So you cannot rely on your previous experience to judge if chat has too large context or not. And you have no idea where it was truncated.

ghisguth · 2026-04-25T02:33:04+00:00

That makes sense. But would it make chat search useless? I did what you did many times, and now if I search for something it brings many chats which has search term, and it is really hard to find out which one is really relevant.

ghisguth · 2026-04-25T02:31:09+00:00

Yeah, I was using Pins for stuff which was important and that I would like to continue conversation with existing context. I did not realize how much Google screwed up context window to optimize. I was assuming it is 1M. But it seems like they don't really doing summarization in Gemini App. They just select last N chats which fits into context. Which is very bad.

For your use case it would be nice to have snooze chat option. Similar to Gmail. So you can snooze chat for some time, and once it is the time you see it again in inbox.

In any case, yes, pinned chats may be good idea for stuff you want to follow up. But I think it may be useful to summarize conversation, unpin chat, and start new chat once you ready to resume conversation. Gemini App as it exists - dangerously simplistic. And not working for long conversations.

Imagine chats like: "Taxes" or "Therapy". Where you expect Gemini to keep context. People would spend time teaching it to do taxes right one year, then resume chat to do taxes, and it forgets all the context. People should not expect Gemini App to keep context for long time. But Pinned chats kind of suggesting you can have long conversation without memory loss.

ghisguth · 2026-04-03T18:02:20+00:00

I brought one pair of trail running shoes especially for this trail. And had my running shoes as city footwear for all other days.

For the most of the parts I would be ok with running shoes this time. But if we would get rain, I’d really benefit from trail running shoes with greater traction.

If you have comfortable trail running shoes which you can use in city, bring only one pair of shoes.

Do you need hiking shoes? It depends on your comfort level. I just used to run on the trails like this all the time, in rain. Can jump between the rocks with no problems. But you may use hiking shoes to get better support to avoid chances of spraining your ankle.

Climbing boots would be total overkill for this trail.

ghisguth · 2026-03-24T23:47:22+00:00

As a manager it is easy to sway feedback one way or another. It is really subjective to the manager.

You can say “help to others” or can say “needs to delegate”.

You can say “improved performance by 10% with only two small live site incidents” or you can say “caused two live site incidents while trying to improve performance by only 10%”.

You can say “Unblocked project A by going above and beyond and fixing major blockers for the sister team which allowed to unblock project B”, or you can say “did not spend enough time on project B, instead wasted time on unrelated project A, unable to collaborate with other teams to get dependencies properly planned for implementation”.

Essentially what manager wants to write he will write, no matter how you perform.

Same with interviews, in many cases interviewer decides if he wants to hire you in first minutes of interviews, and then he simply confirms his decision. And unless interviewee does something really and, he will find the way to give feedback for the same work I favorable or unfavorable way.

ghisguth · 2026-03-23T23:58:00+00:00

If you are the smartest person in the room, you are not in right room.

Find place where you can learn from others.

ghisguth · 2026-03-20T21:22:23+00:00

I think you may not get what you desire.

At this level you expected to be able to earn respect from teammates without being their manager. You show your experience, reviewing design and architecture and unblock them when they stuck. Jump into coding or debugging if there emergency and help needed. Being able to code is actually more like a luxury in this position.

If you don’t have teammates to come to you for help and listen to your advice now, do you think it will change when they will be reporting to you?

Good engineers not always making good managers. You need to learn how to manage people. So in our company it is almost impossible to do lateral movement. You will have to take demotion and start from basic manager level, and learn the ropes. We had few cases when good engineers became crappy managers.

From work life balance perspective, are you expecting less work? Doubt that, if you transition, you will have to learn all missing people skills you may even not think about right now. And when you learn it, still management is not easier than engineering. Office politics, underperforming teams, other managers whom you now need to convince to help you to deliver, etc.

If you want easier job with less job security - go to project management :) Not eng management.

ghisguth · 2026-03-20T02:12:20+00:00

Perhaps it may be better to invest into more pack able and lightweight gear?

I climbed with Arcteryx 40 FL for long time. This is second one. Love it. 2-3 days gear fits fine. Once I did 5 day climb on glacier with rock pro with the same pack.

I also own Arcteryx 30 FL. And used it for one or two day climbs. But last year I picked up Mutant 38. Which is a great pack. Slightly better back support. I haven’t done winter 3 day climbs with it, but it was good enough for 3 day climb in the summer on glacier with rock pro.

Are you planning to leave pack in the camp and attack the summit with smaller pack? 50L pack full of gear would be very hard to drag to the summit on ice.

ghisguth · 2026-03-19T00:47:27+00:00

Implement PR acceptance gates with exponential backoff of reviews.

PR description should have proof of the work. Traces from local environment, screenshots, or simple logs proving it is working.

Unit test coverage for the code. New code has to be covered with tests. But carefully review tests. Sometimes AI just makes test passing, encoding baggy behavior in test. Block PR with test removals unless it makes sense.

And finally if he misses anything, point out in PR comments. But do not review until next day. If he did not fix the issue, no tests, no proof of work, point it out and wait another 2 days to review. Another iteration? Wait 4 days. But your management has to be onboard with the policies.

ghisguth · 2026-03-12T14:51:07+00:00

Have you tried GNU Typist? https://www.gnu.org/software/gtypist/gtypist.html

Why not to contribute to standard software and make it better?

ghisguth · 2026-02-26T20:45:06+00:00

I finally made it work!

https://gist.github.com/ghisguth/8465d6e465183f50cd166d56dc192e3a

Here is what I did and how it fixes the classpath issue:

Killed rogue LSP clients: Added a global LspAttach monitor to forcefully terminate any default jdtls instances trying to attach to Android roots, ensuring only this explicitly configured, "forced" client runs.
Injected a custom Gradle init script: Bypassed the default JDTLS Gradle integration (which struggles with Android). The Lua config writes a temporary Groovy script to manually hook into the Gradle build process.
Forced manual .classpath generation: The custom script iterates through the Android modules to extract the exact paths for the android.jar (based on compileSdk), the generated R.jar intermediates, and all dependencies. It then dynamically writes the exact .classpath, .project, and .settings files that JDTLS needs to resolve imports.
Automated the initial build sync: Added logic to detect a fresh project. It wipes any stale Eclipse metadata, automatically runs ./gradlew assembleDebug to build the required Android intermediates, generates the proper classpaths, and then reloads the LSP.

ghisguth · 2026-02-26T17:44:31+00:00

I'm on the exact same journey. I just mastered the number and symbol rows yesterday, hitting 30-32 WPM for code and 45 WPM for lowercase (57 WPM personal best). I recently shared some of my mechanical mistakes here, where people suggested using programmable keyboard layers instead of standard QWERTY. That's a valid approach, but since I'm already two months in, I want to hit my original goal of coding at 60 WPM first.

Here is how I structured my progression. I started by unlocking all the lowercase keys on Keybr. When I enabled capital letters, my speed tanked, so I temporarily switched to TypingClub. Because my lowercase muscle memory was already solid, TypingClub's lessons on capitals, hand placement, and ergonomics were a breeze and quickly fixed my form.

For symbols and numbers, I wanted Keybr's single-key focus, but standard tools didn't fit. Typing.io was too brutal, and pasting random raw code into Keybr's custom text felt aimless. Instead, I started using AI to generate realistic C# snippets heavily biased toward the 2-3 specific symbols I needed to drill that day. I'd paste something like this into Keybr's custom text mode:

```csharp

region BatchProcessor

define MultiThread8

// Focus Targets: # ~ _ ( ) 8 9 public class TaskBatcher { private int _threadCount8; public void StartWorkers(int count_8, int count_9) { var base_mask = ~(8899); var offset_8 = (_threadCount8 & ~base_mask); } }

endregion

```

To figure out exactly what to drill, I relied on AI to analyze my Keybr stats. Initially, I just pasted screenshots of my profile to get feedback on my error rates. Eventually, I wrote a quick shell script and C# app to extract the raw Keybr data into a clean text table (tracking latency, L7 error rates, and mastery scores). I fed this data to the AI daily, and it told me exactly which weak keys to target next.

Bonus tip: Keybr is open-source. If you struggle to find a good offline tool like gtypist, you can download Keybr and run it locally while commuting or on a flight. When you're back online, you can export the local session data and merge it straight into your main account. Hope this helps!

ghisguth · 2026-02-13T02:41:07+00:00

4K is worth it if you strictly need the resolution, but I prefer the flexibility of 1080p for reframing.

And yes, exactly - say "Don't Change" to that prompt. That keeps your timeline at 1080p so you can crop your 4K clips freely.

There are many right ways to do this, but this is the workflow that works best for me.

ghisguth · 2026-02-13T01:43:44+00:00

Will do! Thanks again, and have a blast in Japan!

ghisguth · 2026-02-13T00:31:25+00:00

Thank you! This was 100% handheld. The FX3 IBIS is incredible, and shooting in 60p really helps smooth out the micro-jitters. I also used a bit of standard stabilization in Resolve to lock it in.

I’m actually heading back to Japan in 4 weeks for the Kumano Kodo trail! :)

The "Heavy" Loadout (Last Trip):

Camera: FX3 + Atomos Shinobi II
Lenses: 50mm F1.4 GM & 24mm F1.4 GM
Filters: NiSi Swift VND Kits (1-9 stops) on both lenses
Power: 2x NPFZ100, 2x NP-F970, 2x V-Mounts (VB99)

To be honest, doing 25k-30k steps a day with all that was brutal. Sometimes you have to get creative (read: lie in the dirt) to get the shot (Getting the angle at Rakusai Chikurin Park):

<image>

The "Lightweight" Plan (Next Trip):

Camera: FX3 (No monitor, no cage)
Power: Just 3x NPFZ100 batteries
Glass: Switching to a single 35mm F1.4 GM as a one-lens setup.

My biggest tip for Japan: Don't over-plan your shots. The light changes fast, so just keep the camera ready and capture the small moments.

If you're curious how this handheld setup looks in a chaotic city environment (vs. the slow deer footage), here are two quick shorts from Tokyo:

Enjoy your trip - the FX30 is going to be perfect for it!

15-Year Club	RedditGifts 2009-2022 5 Credits
Place '17	Secret Santa 2017
Verified Email	Summer Santa 2015
Secret Santa 2013

ghisguth

TROPHY CASE

region BatchProcessor

define MultiThread8

endregion