black3r

you can keep them on a VPN and connect to that VPN yourself from anywhere, without exposing them to the possibility of anyone connecting to them directly from the internet.

the company I work for is literally pushing one new feature behind another, the whole product is a mess now thanks to it, all of the features just get developed, hyped by marketing team, and then abandoned and we work on new ones... the features we developed 2 years ago untouched are beaten by competition, nobody cares, cause only thing we care about is user acquisition...

and of course we have no long term plans and vision, cause we just jump on hype waves and if something is marketable we need to develop it ASAP without really thinking it through to get as much new users as possible...

I hate it here, the only reason why I haven't quit yet is I'm scared of finding a new job given the current state of job market.

I'm in Slovakia. We have 4 networks here and they basically have hidden non-compete agreements where no-one launches new tech for masses without at least one other providing it launching it too, sometimes they even coordinate the launch so that all 4 of them launch at the same time...

This same shit happened with launches of 5G NSA, eSIM, Apple Watch eSIM, RCS, and lots of other telco technologies...

At this point all the operators have 5G SA networks up and running for parts of Slovakia (Telekom even claims it covers 99% of Slovak population with 5G SA), but it's only available for business customers in private networks...

They all claim the same stupid reason for this - "most customer phones don't support it, and there are additional benefits for businesses"...

And there are rumors from all of them that they plan to launch it for regular customers by the end of this year...

I mean come on... In a fair market competition the first one to upgrade its network would launch first and heavily claim that they're the fastest innovator in marketing...

And when the network is up and running, why not open it up to regular people? And why it's always the same bullshit type of excuse that's basically trying to say "people don't want/need this"?

yes, and the fact that it runs a phone chip is the reason why it only has one 10Gbps USB-C port and the other only supports USB 2.0 speeds...

my first iPhone was the original SE (which was essentially iPhone 4 expanded to 16:9 screen) and I'd say it was the perfect size of a phone, the reason why I opted for a larger screen even though my hands are kinda small for a man is that website and application design has completely shifted towards those large screens and small screens are unusable (and for me this has been true since 2019 when I switched to a larger screen)

it is kinda annoying, but apparently the consensus of modern design includes both lots of useless horizontal margins (lots of them just for the sake of visible rounded corners) and lots of vertical space taken by ads (iPhone 17 is actually 19.5:9, not 16:9, so ads take less vertical space on such a screen)...

and after a few months of using a larger screen I learned how to use it with one hand so it is possible - I rest my phone on 4 fingers and use thumb to interact, I only use two hands when typing (well two thumbs, but whatever)... but I still agree that the bigger the phone the more I'm worried it will fall down from my hand when operating it with one hand... the Max versions of iPhone do seem too large for me...

> 3. End with one concrete next step.

I mean maybe I have ADHD idk i'm not diagnosed, I don't generally have issues understanding Claude's output (even though I do think it's unnecessarily verbose), but I think this one is a general good advice which Claude ignores for some reason, and is especially annoying during debugging sessions, where it asks for 3 outputs, I paste one for it to process while getting the others, and then it immediately forgets it wanted the 2 others, and starts cooking up some wrong conclusions...

commits are local, so they're okay to me, I draw the line at pushing them... I either want to check its work while it's working, or let it finish and then check it all at once -> if it splits it work into smaller commits its easier for me to review it before pushing than if it was just uncommitted hundreds (or thousands) of lines of code all across the codebase.

I never want Claude or any AI to post messages as myself..., if I'd wanted Claude to send a message to Slack, I'd want him to identify as Claude, or use some bot token, where it's clearly visible I'm not the one posting it (while I can still instruct Claude to say that the message was prompted by me).

Honestly, the worst thing about App Store rating system is that the ratings and reviews users see are country specific. So if you are in a small country and you try to use an app that is not really popular in your country, you see very few reviews, even if the app has thousands of reviews on the USA App Store.

Apps can only show you the Apple's dialog for rating three times a year. Many apps first show you their own popup/dialog asking stuff like "Do you like this app?" and only if you click "yes" there then they show you Apple's dialog. And they can show you their own dialog as many times as they like...

washing is okay but dropping it in a pool destroyed my charging port on iPhone 14... the phone kept working and was rechargeable wirelessly though...

my first apple watch (6th gen) died when I was using it on a water slide ending in a pool on a holiday... since then I'm wary of using it in water...

So much this. When coding I use my LLM to hone the code to perfection before sending it to review, including running AI reviews on it multiple times and fixing obvious bugs so that reviewers have less work to do. I also test all my code manually (LLM can be helpful by giving me a list of test scenarios to consider). When reviewing PRs I carefully read the AI reviewer output, consider which points are relevant, which are irrelevant and only post the relevant issues when requesting changes.

I have coworkers who routinely post PRs with comments stating "all tests green, ready to review" and then I actually start the application, test it manually and it doesn't work. And don't get me started on reviewers who post the raw AI output of their "reviewing skill" and then I have to read through 30 paragraphs of "findings" most of which are irrelevant (just today I got the "valuable" feedback of "View is @api_view(["POST"]); no test asserts GET/PUT/PATCH/DELETE → 405")...

How LLM usage affects your thinking process entirely depends on the workflow you use with them.

I can honestly say that while using LLM my thoughts are as sharp and as fast as they were before, if not sharper and faster. But my workflow is that I watch the LLM as it rips, have verbose output turned on so I also read Claude's thinking process (and lots of interesting information is hidden there).

This helps me learn new stuff I wouldn't think of. Helps me stop Claude if he's veering off track. Makes it easier to proofread what's Claude doing and why step-by-step and easier to spot any mistakes (because they often come from wrong assumptions you wouldn't see if you didn't see the thinking process).

If you just let your agent write thousands of lines of code, reviewing them is painful. If you also run multiple agents for multiple tasks at the same time, your focus is divided, so you aren't spending all your brain power on the task at hand.

I have one like that and so do my parents. But they're much less effective than classic split AC with an outside unit. A regular split can cool a bigger room to 24 even when it's 38 outside and is basically completely quiet. A portable AC cools down smaller rooms to ~27 when it's 38 outside and is noisy (50-60 dB).