Tech/code question
May. 27th, 2025 07:37 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elisheva_m posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
little_detailsI'm trying to write a scene where two co-workers are trouble-shooting a new custom security or encryption routine. Someone else (who isn't present) wrote the code and he will have been careful to ensure it works before sending it to them. So maybe something in the implementation of it?
The scene is dual purpose, showing their interaction growing closer while also hiding something else in plain sight. The tech part of it can be whatever is plausible and easy to convey without bogging it down in details. I am so out of touch with that sort of thing I don't know what's plausible any more.
What could go wrong with uploading the new code into their office network or onto their phones which would need a bit of trouble-shooting? The kind of thing one person might overlook and another catch. Preferably with them being literally close while they do this. And again - easy to convey without bogging it down in details. Jargon is fine.
Edit: Turns out jargon is not fine. Well it would be in the sense I meant, but that's not how it was taken. Am overwhelmed by how much I can't understand well enough to follow here, let alone distill into a few phrases. I know the readers for my lakorn-novel are non-existent but I can't swamp them with details.
Edit 2: Sorry to have bothered everyone. I'm just going to trash this. It was a stupid idea in the first place. Thank you for your time.
The scene is dual purpose, showing their interaction growing closer while also hiding something else in plain sight. The tech part of it can be whatever is plausible and easy to convey without bogging it down in details. I am so out of touch with that sort of thing I don't know what's plausible any more.
What could go wrong with uploading the new code into their office network or onto their phones which would need a bit of trouble-shooting? The kind of thing one person might overlook and another catch. Preferably with them being literally close while they do this. And again - easy to convey without bogging it down in details. Jargon is fine.
Edit: Turns out jargon is not fine. Well it would be in the sense I meant, but that's not how it was taken. Am overwhelmed by how much I can't understand well enough to follow here, let alone distill into a few phrases. I know the readers for my lakorn-novel are non-existent but I can't swamp them with details.
Edit 2: Sorry to have bothered everyone. I'm just going to trash this. It was a stupid idea in the first place. Thank you for your time.
(no subject)
Date: 2025-05-27 08:00 pm (UTC)I'd write the scene without worrying about the jargon first. What do you want to happen between the two characters? If you're looking for a fixable error, it could be something as simple as left-handed vs right-handed. On a phone screen, would something be 'awkward' if the one user is left-handed?
Do you want things to go wrong? That's kind of a different thing to write?
Whether the implementation goes right or wrong, I'm suspecting that if you write the scene as you want it to happen and put in XXX - a placeholder -- for jargon that you may or may not need will keep you moving forward.
Good luck!