Early Macs are not really multitasking in the sense that newer machines are. Each running application has to hand back control to the operating system as a part of its main loop (think like video game main loop if you are familiar with that)
In the same way, disk operations themselves are generally blocking and will hand back control to the OS and apps during their read/write cycles so that other things can happen on the computer.
Neat idea, I wonder how it’s handling communications under the hood. Tcp/ip stack? Serial? It will be interesting to toy with if the author decides to release it and the source code
Nice work! If DeskHop could be made to work with a Bluetooth mouse, it would be even better. FWIW I was looking for a similar solution recently. I've got a magic trackpad, keyboard, bluetooth mouse, and monitor. I'd like to swap between 2 computers somewhat easily.
I'm in a similar position: I'm on Windows and have a mouse that supports multiple Bluetooth connections and can be made to switch between computers with the Mouse and Keyboard Center but the keyboard only connects to one computer at a time so I'm stuck using two identical keyboards and moving them around physically.
Also another pet peeve with M&KC is that it will also switch when the other computer is off, which happens more often than I'd like and leaves the mouse "stranded" (forcing me to turn it over and press the Bluetooth button to cycle through the three channels).
In Toyota's hybrid synergy drive, the electric motor system is inputting to the same transmission as the ICE engine, and is an integral part of the casing. You can see a cutaway of it here to get an idea of what it looks like in practice: https://en.wikipedia.org/wiki/Hybrid_vehicle_drivetrain#/med... What you're describing is indeed how the E-Four system works for the rear wheels on the AWD versions of the Prius
I've held various roles over the years and personally believe that public contributions and innovative open source projects will often impress potential employers. Despite not coding much professionally anymore, I engage in fun personal open-source coding to maintain my skills. This strategy even played a part in securing my latest, predominantly non-coding role.
After reading your post, I reviewed your GitHub profile. You're certainly on the right track, but there's room for improvement. Here are my personal observations and opinions:
- You have numerous small projects, but they lack detailed descriptions and the README files don't tell me much about their purpose. Why are you building these? How can they be run? What functionality do they offer?
- Many projects have minimal activity, suggesting they might be incomplete or abandoned.
- There are several boilerplate projects like "calculator", "todo", and "tutorial".
- Your commit messages in most repos are quite short, often just one or two words. This practice might not be accepted in a professional team setting. I've been guilty of this with my personal projects at times too.
- Your project https://github.com/prakhar897/workaround-gpt shows promise in terms of community interest and the start of what could be a well-constructed README. Perhaps you should consider continuing with this project or developing a similar, well-structured project. Just a thought.
So, it sounds like having a Github could be a net negative. I don't treat personal projects like I treat production code at work. I experiment, don't write a lot of unit tests, use bad practices because they're easier, and I get bored and abandon things because after all, it's not like I'm being paid for any of this.
If that's going to be seen as a red flag, then I'm not going to share any of that.
I certainly didn't mean to suggest that having a GitHub profile could be a negative. My point isn't about identifying red flags, but about pointing out areas that could be improved to make one's profile stand out - especially in the case of the person I was responding to. As someone who reviews numerous resumes, I'm providing insight into what I typically look for when I peruse a candidate's GitHub account, based on my personal experience. I don't disqualify someone based on their GitHub activity, but I do use it as an additional datapoint to help identify those who might stand out from their peers.
I've some GH repos whose quality I'm ashamed of today. But it's clear they were developed by a person with 12 years less experience than me today. It's clear it was just a hobby-project or clear that it wasn't ever meant to be continued this long. A line like "The code in X is a mess and needs a refactoring" is enough.
It is to me, when I researched candidates. When a ticket, todo or note shows that the author is clearly aware of the problems, and shows she/he can weigh off why (not) to fix that today, it tells -me- they are good in what they do.
A dev who shows to make decisions about quality, effort, workflows, based on experience and reasoning, to me, is worth a hundred devs that blindly follow The Sacrosanct Rule Of The Latest Cargo Cult Religion™.
A dev who shows she/he grew over time, by showing "terrible" code in the past, to me, is worth a hundred devs that have been doing the exact same rituals for years or decades.
So, yes: by all means, show your worst stuff. But be sure it's clear that you know its "bad" and why.
My buddy has an 89 Prelude that got stolen a couple of times. It basically got driven around and left with an empty tank around town both times and no signs of break in. I think the keys are relatively common for those so maybe the thief has one.
Anyways, I installed a switch up under his dash the disconnects the fuel pump +12v wire. It takes just a moment to flick the switch if you know where it is, and afterwards, the engine will crank and crank and crank and sort of sound like it wants to start at first, but never do anything. It would probably take several minutes to find it if you had to look for the switch, especially if it were at night and you were trying to steal the car. Seems like a good lower tech deterrent to me! The car has not been stolen since.
> I think the keys are relatively common for those so maybe the thief has one.
I have a buddy who had an old Ford in San Francisco. Once in a while he'd get in the car in the morning and notice that it felt .... strange. He couldn't put a finger on it. Then one day he had to get to work a little early and showed up at his car much earlier than normal. He found a guy sleeping in his drivers seat. Needless to say, both were startled and the homeless dude ran off, leaving a big bunch of keys behind in a keychain. Those were "master" keys to get into a whole slew of older vehicles.
I remember (in the late '70's or maybe early '80's) a friend's car where he added (it was not unusual at the time to add "accessories" to cars, like fog lights or rear lights ) a number (four or five) lever switches (connected in serie) that acted like a dip-switch, you had to set them in a given pattern (like up-down-up-up) to be able to start the car.
In the same way, disk operations themselves are generally blocking and will hand back control to the OS and apps during their read/write cycles so that other things can happen on the computer.