AboutFather, husband, computer engineer, former chef, and also a political scientist!
SkillsAssembly programming, C/C++, Java, app development, HW/SW interfacing, IoT
LocationWestern New York, USA
Joined devRant on 9/24/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Reworking your compiled C program in assembly is even easier! (and fun too!)
@dontPanic Thank you for the nostalgia from my first-year Physics lab! Damn pendulums.
@CrankyOldDev Maybe someday, but I would much rather build one from scratch; or at least wait until we have a better piece of equipment to fix than a $50 machine from target, but wife never consults me before buying so I need to jump on it now...
:yy (to copy a single line)
:dd (to cut a single line)
:#yy (to copy # lines)
:#dd (to cut # lines)
:p (to paste whatever is on the clipboard AFTER the current line)
Don't forget: As a leader you have to try to get your way. If you run things too democratically your people won't respect you, they'll lose motivation, and it will show in the finished product. But don't be totally authoritarian either: Don't poo-poo other ideas off the bat; take a moment to listen to them, and if it's good then run with it, and if it's bad just politey give. reason why it won't work.
Be prepared to listen to your people, and to formulate a plan that takes into consideration their input and ideas.
Also don't be afraid to coach greatness in them. If someone seems like they're on the right track, push them to develop their ideas a little more.
Really in the end leading people is about planning to execute the orders you were given, then breaking that plan down so that you can delegate each task to the subordinate who is best-suited to take on that task.
And don't waste time in meetings.
@Gerrymandered meters. If you use feet, then change 9.81 to 32
I've gotten jobs and tried out for jobs and promotions that, looking back, were way above my level. Not just in programming but also in cooking (when I was a chef) and in management.
It isn't a foregone conclusion that you will end up in over your head, but don't be afraid to push through your fear of the unknown. You just have to hit the ground running a litte faster when you do get it, and you have to spend more time researching the actual job and planning more, and being open to changing your plans completey if need be.
That said, there are times when you have more than just a gut feeling that you'll be in over your head. You have to be able to tel the difference.
Don't ignore your sensibilities, but do push through your fears.
You hooked up one night, when you were drunk and she looked mighty fine after twelve shots of hard whisky.
Then you wake up next to a haggard wretch, gravelly voice, face worn by years of cigarette smoke and disappointment in men because she gets too clingy too fast. Then she starts talking about your lives together, and you're contemplating taking a header out of the bathroom window in her tenth-story apartment.
All you know for sure is that you'd kill for your old set of issues with any other girl / language.
Those pics sent a shiver up my spine.
Beet of luck with that situation!
At least they don't have some haggard old bitty in the ad... unless it's Grace Hopper, who is neither haggard nor an old bitty... And who would also not lower herself to hawking shitty WYSIWYGs on youtube.
Grace Hopper is the Sean Connery of computers: She can do as she pleases.
In my first year of Computer Engineering, we had to create pong using Java and a game engine they gave us.
So naturally I took it a step further and recreated the original Super Mario Bros.
The code to draw Mario was 1000 lines long. I miss those days when I did things like spaghetti code and didn't think anything of it.
Now I get anxiety if I have a C file with more than 200 lines non-commented.
That reminds me: In a later course I had to recreate qbert in assembly code, using ASCII codes. Ended up with nearly 20000 lines of assembly instructions (one instruction per line)
@sour Ah yes, Microsoft's secret weapon: Licenses.
@RiderExMachina Mind you, this is the one company my wife has ever worked for who DIDN'T insist on using IE, so I assume their IT department is not staffed by incompetent degree-mill "graduates."
@RiderExMachina The breaking point for me was when two different computers running Windows both completey broke off from the hard drive within as many months.
Our household is now under a lifetime Windows embargo.
Wife's work computer still uses W10, and apparently I can't d-boot it because they don't want anyone fucking with their computers.
"but honey, it's not fucking with it if I make it better. Your IT guy will understand. He'll probably thank me and take us out for steak dinners!"
I am currently on God level concentration. I'm in a near-empty library. Someone is reading a book and they are turning the pages kinda loud. Very annoying. Makes me wanna tomahawk a fucker.
I know it's not to do with the rant, but I can't help myself.
@plttn Having a hard-copy of passwords isn't a security issue. It's more of a sanity issue, because they're trying to keep track of a bunch of different passwords that really have nothing inherently secure about them. In other words, they're putting an obnoxious amount of effort into what they think is "security," but the actual password is maybe eight characters and has common, non-alphabet characters mixed in.
Maybe I should write a program that cracks their passwords by brute-force, and when they see how easy it is then they'll listen.
time_to_ground = ( height * 2/9.81 )^(1/2)
In Microsoft, you submit Feature Report / Bug Suggestion
@randomcomma If you're referring to the salesmen who kinda just wander around a random neighborhood hawking cheap cutlery or two-bit term life insurance underwritten by Toothless Joe's Guaranteed Acceptance Underwriters, then yeah: Those unfortunate souls are the bottom-feeders who make other salesmen look bad.
Best one I ever saw was this guy selling door-to-door meat. No shit, he had a cooler full of frozen steak. I told him to get lost.
@randomcomma Let's suppose you have a really solid program for businesses, and you decide to build a startup around it. Who's going to drive your sales?
Yes they can be tenacious at times, and are annoyingly persistent. But when they are selling an actual thing that people need, they play a critical role in helping businesses and individuals succeed. They help bridge the gap between "supply" and "demand," which ultimately benefits everyone.
@DemonFtIllusion Touché sir. Have a ++ and welcome to devRant!
@gitpush Everything worked out in the end. We cut down the housecleaning, then my wife and I went shooting.
First target of the day is shown, hers are the smaller 9mm holes and mine are the bigger .45 cal holes, we both shot from 35 feet. Then I got to work for a few hours on my stuff. Then we had chicken wings for dinner.
@esavier Linux signals, and pipes.
Basically, AI would have a vast and fragile worldwide network of small memory nodes, and a single human mind is a single, albeit MASSIVE contiguous array, with a practically unlimited allocation.
Considering the demands of memory availability and speedy recollection of information, I think humans have an insurmountable advantage over a dispersed network of AI devices.
AI would probably use up half of its available (fragmented) memory simply storing addresses and redundant addresses to the actual information.
Imagine a linked-list where every node contains a lot of pointers to other pointers, and extend that recursively over all the information needed to compete with just one human mind, and each node in that list is not guaranteed to be available to the CPU.
Big problem with AI, at least from a hardware perspective, is that the available memory will be massively and irrecoverably fragmented. (lots of small devices)
When you consider also the massive memory requirements AI will have in order to rival human intelligence, it will be very difficult for AI to allocate memory at a fast-enough rate in order to pose a threat to humans.
Finally, in order to retrieve that memory efficiently enough such that the information can be useful before a situation changes, AI will need to guarantee very fast serial communications AND that the device which contains the critical information is always functioning.
Meanwhile, although humans can't recall information as fast as an SOC microcontroller, we are more adaptive to change and each of us can store far more information in a smaller space.
Rusty Shackleford for me.
First thing first:
list->container = (pid_t*) malloc( list->alloc * 4 )
to prevent overflowing your memory.
Gross pay = base pay * ( 1 + lines_of_compiled_code ) / lines_of_compiled_code