Maybe it's a customised windows 11 for surface pro. I usually have maybe 5 seconds for login ? and I can remember windows xp having to wait for 2 or 3 min to login.
Can you check if there are any startup scripts within windows or there is some sort of event registry, right ? I've not experimented that much but - there would be logs.
Not sure, think it's the default Windows 11, haven't noticed any differences. Usually login takes sub-second, just after this specific update that it took long time. After logging in once after the update, subsequent logins are as fast as before.
I have no custom startup scripts what so ever. Everything works just fine during normal operations, just that Windows updates suck and wasting my time, just like macOS.
That's a good suggestion for small to medium codebase. In huge codebase, it's not feasible but explaining to others (like colleagues or interns or friends(oss repos not proprietary stuff)) usually helps me a lot.
Most colleagues (even developers) walk away in boredom as soon as the discussion gets too deep. I do understand though as they are happy to help me, but when it gets too deep they feel they are doing the work for me
Maybe linux is light weight and is more modularised than Windows or macOS ? Was it the same behaviour using SSD vs HDD to account for disk fragmentation ?
Maybe somehow windows / macOS updates are linked to something in BIOS (Idk either) ?
I haven't used a HDD for the OS drive for many many years now on any of the OSes, so shouldn't matter.
It's possible I guess that both Windows and macOS upgrades something regarding the boot process, one of the Windows machine (which today went through the ~25 minute upgrade I described in the OP) is a Surface Pro 8, and all the macOS machines are obviously Apple hardware, so very likely there are firmware upgrades happening as well. It's a good guess.
What do you mean by moving and inter-dependent parts ?
I read doc (if any), talk with different people, although it's none in my team (T_T), then identify different services or processes, read their logs a lot, then glance through code structure + file names, then put thread dumps, then somehow found it.
Then explore around something, add more logs or use a debugger - run it locally or on cluster, then speak with people - share my findings, then they'll ask few more questions or explore on their own - this will happen for a week.
This way you'll exponentially (whether you remember that info is a different topic) gain knowledge + faster turn-around time for any poc or incremental feature change.
Ultimately, everything is a kernel process with some threads running in it. So, yeah attack codebase in anyway possible.
By moving parts I mean components in a system which change state, and communicate with other components. Anyway, yes, reading docs I guess is useful, usually out of date though. Yeah, good tips on trying to read the logs, to understand how the parts interact and get a mental model. Thanks for the tips
Tree structure ? json, xml, protobuf, classes, functional programming, databases with foreign key, database internals, etc ?
Oh I forgot you also serialize and deserialize data - did you forget how that works ? Tree traversal again.
Do you know how organizationl hierarchy is structure ? It's a tree.
Do you know various maps and their usages ? We use them daily - it's very very important to know their internals. Hashing vs Trees vs Linked hash vs etc.
Google maps ? n-d trees ? Comparing data - merkel trees ? etc.
Every dev out there has common work with mine. But you won't be able to solve the problems that I face on a daily basis without thinking hard & without this dsa + concurrency knowledge.
Now, is it reasonable to ask these questions ? Heck yes.
You are just ignorant. You should read about distributed systems. Google around for Zookeeper and it's zab paper.
Every (recently with raft protocol) multi master distributed system out there interacts with Zookeeper for assigning leader and maintain configuration.
Do you know how the syntax or api calls look like ? They are node path in a tree. You want to store something ? That's a tree path again. You want to listen to some change ? It's tree path again.
As I said, most people are ignorant here and don't do "true" computer science engineering in daily life.
Most devs simply convert business logic into bunch of apis + adhoc implementation.
Did you ever work at a banking firm ? I've read their codebase - they are structured as trees, every damn thing is tree. It's a headache to navigate, code, heck even the objects are literal trees.
As I said, people are ignorant and think world revolves around them.
Just because you haven't worked in a team that requires those skills doesn't mean they aren't valuable.
In my old team, I had to come up with a coupon distribution logic based on count, percentage, time, then generating reproducable random values that required to deep dive (algorithm) into library code & explicitly storing state in redis, then an application of dynamic programming in building as custom platform, atomic token validation, custom rate limiter algo, state machine, scheduler, distributed circuit breaker, etc.
In my current team, I had to read raft paper, zab paper, look into their implementation, make a poc with raft protocol, then autoscaling algorithms, scheduler algo's, different data structures, heck even the oss engine itself is DAG, heavy threads + concurrency stuff. Even now I come across new data structures and algorithms.
Clearly you don't know the entire industry, just because you haven't worked in such teams, doesn't mean these aren't important.
You are experienced in a bubble. The hiring bar for our team is higher than other teams and heck even for SDE3 - the requirement is higher. You would be very much surprised to know that even the senior members have research publications and deal with complex stuff.
Core teams like in AWS or GCP or Azure solve these sort of problems.
Who do you think will solve autoscaling (that's what I'm doing now) or managed scaling or network or security or any infra problems in these cloud platforms ?
As experience increases, we expect more knowledge & insights - doesn't mean to ignore basic coding stuff like arrays or linked lists or trees or graphs or simple message queues or etc.
If companies are paying competitive TC and there are multiple candidates, why not hire a smart person ? What's so special about doing regular normal stuff ? That's just a normal dev right ?
So if you are just doing normal stuff, then why should anyone pay competitive TC ? That's just a normal dev, right ? What's so special or talented about you ?
Companies that pay huge TC want to hire smart people not just an average joe. Sure, you can live satisfying career and that's your pov.
What about a company's pov ? Did you ever think about it ?
Can you check if there are any startup scripts within windows or there is some sort of event registry, right ? I've not experimented that much but - there would be logs.