Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Years ago, freshly out of school, I ended up in a job at a french small shop that required me to learn a lot of things.

They had a brillant sysadmin, that I bothered to explain them to me. Sometimes, he'll come to my desk, looking at my screen, typing the solution while explaining the problem to me with simple words.

Standing up, typing with one hand, and working on what was supposed to be my specialty, he was doing a better job than I was, despite me interrupting his workflow.

I left the job, and levelled up. One day, I read an article about docker, and the name of the dev caught my eyes: it was the friendly former sysadmin colleague, Jérôme Petazzoni, who went on becomming docker's biggest evangelist.

Thank you Jérôme, for making sure I started my carrer by not being the smartest guy in the room. I kept it as a habit.

Or I'm just dumb :)


> for making sure I started my carrer by not being the smartest guy in the room

That's indeed invaluable. That should be the first advice to anyone starting out: if you find yourself being the smartest in a room, go find a new room. Right now.


I left the company I was part-timing at because after college I realized I was the smartest one in the room; my boss thought some of the code I wrote was "brilliant" and for this reason did not let me improve/fix any of it, which led to the company shipping a broken product to some very annoyed customers.

If you are ever managing someone who is "your best employee" and they want to do something you think is useless, please ask them why and what the expected results will be. Also when you get that data, listen a little? If priorities clash do a balancing act: "If you can do X in Y time, do it. But if day D comes along, switch over to my priority".


I graduated college and started working at a local tractor manufacturer. In hindsight, this company had no idea how to make software.

For instance, they required that all "software engineers" were from an accredited engineering program--at the time, none of the universities in the area had an accredited software engineering program, so they would hire electrical engineering majors who had no desire to write software but were looking for a way to get their foot in the door. Most of the EE majors had a single semester of C and that was their entire software qualification; however, I double majored in EE and CS and my passion was software. That said, when I graduated I didn't understand any of this--I just figured there was this successful company and there was so much I didn't know about software, so I thought I would learn loads there--and I did learn loads, but it was mostly about what not to do.

One of my first projects was to take over an embedded C++/Qt project that had been bid out to some contractors in the Ukraine. The software was super buggy and the code was immensely convoluted. Test coverage was part of the contract, so it had tests, but even still, no one could change anything without breaking everything. It took me weeks of plotting the code paths to figure out that there were many paths through the code that were only exercised by tests--literally they were just trying to boost their code coverage metrics by adding code that was unreachable at production. I guess it didn't occur to me that professional software engineers would be so bad at writing code, and that a large and well-known software company would hire them.

Thankfully, after eventually gaining my entirely-nontechnical manager's trust, we were able to bring in a consultancy who helped me demonstrate that it would be no more than half the cost to rewrite the code rather than try to fix all of the existing bugs even if we never found other bugs or introduced a single bug of our own. We did the rewrite and it was successful, but I was beginning to realize that in some overly simplistic sense, I was the "smartest" one in the room as it pertained to software development anyway.

Ten years later, when I talk to my peers who stayed, many of them have been writing embedded C programs and various MatLab models and they still don't understand pointers or dynamic memory or git or anything outside of their very local niche. Which would be fine if they were happy, but now many want to move to another company but they lack the skills and confidence to get anything more than an entry level job at many other software companies--so much of their compensation is derived from their knowledge of their employer's business and processes rather than their technical acumen, so they would likely have to take a significant pay cut to move to another employer.

Anyway, this is already a very long post despite oversimplifying many things, but I hope this illustrates what it looks like to be the smartest person in the room and why it's not good.


Once, I was working on an intranet web tool generating .odt documents for the user to print.

It worked perfectly, except on one machine, where the document could be downloaded but LibreOffice raised an error when opening it.

At first I though I had a bug. Checked my code, nope.

Then I though maybe there is a problem with LO, but no, same version, nothing special. It worked with a document I brough from an USB disk.

After an afternoon of frustration I noted Kaspersky running in the task bar, and did one last desperate attempt at finding the solution by disabling it.

It worked.

Inspecting the file revealed some parts were missing, Kaspersky assumed it was a malware, and not only intercepted the download, but removed silently part of the data on the fly.

No alarm, no pop up, just a broken file.

Disabling the antivirus was not acceptable for the client, so I created a self signed certificate, and turned https on.

The virtual vigilante couldn't spy on the wire anymore, and the user could download her files, unharmed.


I had a development machine once that had the weirdest problem building one particular C# project. Always complaining that one particular Microsoft DLL was missing. Double check references and Nuget, everything looks right, do a full package restore, no joy. Antivirus was eating this particular DLL every time it was downloaded.

I copied a bit-for-bit identical version of the file from a different machine into the correct directory, and bizarrely that worked fine.


I had a very similar issue with BitDefender recently. When downloading the WebRTC C++ library, one of the submodules is harfbuzz, which contains some maliciously crafted font files used by the test suite. BitDefender automatically deletes those test files. That means git sees the repository as dirty, since files are deleted. That means WebRTC's fetch script can't run the 'git checkout' commands it expects to be able to run, and the whole download fails.

While my summary here is brief, debugging this whole mess took a while.


> Prudence is certainly a choice one can make, but in no way should it be recommended or required.

risk = probability X severity.

If something is a big deal to you, take precautions, even if it's unlikely, because the severity is high. This is why we take huge precaution with nuclear plants, because the likelyhood of an accident is low, but the severity is high.

If you have nude on your phone, severity is high. The probability that googles will mess with you is low, but it's good advice to tell you to protect yourself.


> If you have nude on your phone, severity is high.

Incorrect, for societal reasons.

For women, the severity of nudes being stolen is very high, regardless of social stature. The majority of nudes published without consent are of women, and the majority of 'revenge porn' nudes published explicitly to demean are of women, and the majority of societal outrage excluding public figures is directed at women. The long-term impacts of nudes being published without consent never fade, and is nearly as likely to result in loss of employment and social stature years later.

For men, the severity of nudes being stolen directly correlates with whether they perceive their career or social stature to be at risk if nudes are stolen are shared, as in the majority of cases men are blackmailed for payment before stolen nudes are published. The long-term impacts of nudes being published without consent fades rapidly for private individuals, hinges on their career and social profiles rather than being effectively universal across their gender, and is often disregarded altogether.

For public figures, the employment and societal circumstances vary wildly, and the overall risk of permanent harm to men increases considerably; however, the risk of permanent harm to women decreases only slightly, and typically only for women who already publish nudity of their own accord, and thus have already factored in the societal harm of doing so.

My time is limited, so here's one contributing citation only:

Intimate image abuse in adults and under 18s (2019) https://swgfl.org.uk/assets/documents/intimate-image-abuse-i...


Trust, but goes with Pareto precautions.

Arabs have a wonderful proverb for that: "trust in God, yet tie your camel"


It still works.

I would blame the mechanic, sue if necessary, but it's still good advice not to let any valuable in your car if you lend it to a 3rd party.


I've lost a laptop in an airport shuttle with intimate pics on it once, and got worried sick.

After that life lession, I always made sure to have a veracrypt partition for this stuff. But a separate, offline device is better of course.


Modern Android actually does support disk encryption. And the Pixels even have TPMs that should (?) safeguard the key, preventing offline brute forcing the unlock pattern. I wonder what happened here that this did not work...


Someone else here mentioned that the the reddit comments (now deleted) said that the phone had no passcode on it, so anyone would be able to unlock it.


Ah, that's it then. I figured they would likely have a passcode, since the "someone steals my phone on public transport" threat vector is a pretty obvious one even for non-tech users. Unfortunately the thread got nuked before I got to read it more...


I wonder what kinds of tickets, if any, justify them asking you for your unlock pattern.


This week I was in a chat with the REAL support of a crypto currency.

Unable to help me with my problem at first (we eventually figured it out), they felt they hit a dead end and said: "ok, just send us your wallet.dat, we'll fix it".

I know those guy were the real deal. I knew they would not try to steal the money I had on this wallet, because it was so little it was not even worth the time.

Yet, the fact they asked that proves how much support can badly educate their users.

Of course, I didn't send my wallet, and found another solution since I'm tech saavy. But still...


I once got my screen replaced at one of the phone fix-it places. It's a decent sized chain, not just some rando. On the form you fill out during drop-off it asks you for your unlock code.


What did they say when you didn't include the passcode?


I wiped the phone before I brought it to them, so I just gave them the passcode.


none since they can wipe the phone without a passcode. This is true for both iphone and android phones. I'm not familiar with off-brand OS phones though.


Seems OP never had a password lock to begin with


Would windows Bitlocker work too? My issue is that Veracrypt requires you to mount a drive, while Bitlocke provides protection over the whole drive (barring your adversaries being Microsoft and/or the NSA).


I just tried Bitlocker for the first time a few days ago. I enabled it, and next time I booted it up, it never asked for my password. It turns out it only protects the drive if it's removed from the computer.

I just used VeraCrypt instead.


Really? My Bitlocker setup requires me to enter in a password to unlock the drive.


Maybe I did something wrong, but when I looked it up online when that happened, that's what I read.


It's not blame, it's advice.

Advice that is strongly needed, because most people think "they have nothing to hide" until they discover than:

- they do

- they can't


You’re right, everyone has a need for privacy, and there is almost always private info on devices people use. So why is “advice” to avoid repair and eat the costs considered a tenable solution?

The “advice” would also apply if you ever logged into your bank or bought anything, if you ever read your email, if you have any secret keys or certificates for authentication of anything, if you ever visited a web site or searched for something you wouldn’t want someone else to see, if you have a list of contacts, if you have any personally identifiable information, if you ever worked on something considered confidential by your employer, etc., etc., etc.


> So why is “advice” to avoid repair and eat the costs considered a tenable solution?

It's not an "or" proposition.

You can fully push for a society where such behavior is dealt with or inexistant, because that's the right thing to do.

At the same time, you can ackownledge this life is full of terrible unfair things, and preparing for them can spare you a lof of pain.


> It’s not an “or” proposition.

I agree, but I’m confused; I didn’t make an or proposition, and you followed that statement with one. We can realistically deal with privacy problems using laws, and we cannot realistically ever expect people to never repair devices that have private information on them. Right?

There’s also an unfortunate environmental downside to suggesting that people avoid repair.


It's about taking precautions in general, not avoiding repair in particular.

And deal with privacy problems at the society levels, not just using laws in particular.

And it's not "or" them. It's "and".


Sorry, I’m lost about what your point is. What “or” are you still referring to? You seem to be trying to correct something, and I have no idea what it is.

You defended the specific idea of avoiding repair. If we’re talking about other “precautions”, I’m not sure what you mean because you haven’t made it clear.

My point, I guess, is that “advice” about taking “precautions” really does boil down to victim blaming. There are no reasonable precautions that the general public can take when sending a device in for repair; private information will be available to the person with physical access to the device.

We already have some laws protecting against privacy violations, and the issue in this article is likely covered by some of them. The remaining solution is for Google or Google’s subcontractor to be held accountable and pay damages, which is exactly what is needed to address privacy problems at the social level: consequences for breach.

Otherwise, I don’t see how your suggestion to take “precautions” is helpful or realistic.


That sounded like a joke :)


The price of humor on HN is eternal downvotes.


>The price of humor on HN is eternal downvotes.

Not if its funny.


It's important to understand that for every person familiar with the name and the abbreviation there are roughly 22 people who have no idea who she is.


A great comment to refer to the next time some young coder that never lived through IE6 says it's great to have one single engine everywhere.


> A great comment to refer to the next time some young coder that never lived through IE6 says it's great to have one single engine everywhere.

OP is suggesting that Chrome should have spearheaded a spec that no one but Intel and Google ever showed any interest in. How would that not have been literally "they like a standard (or propose one), they implement it, use it on their projects like google doc, and let the competition deal with the mess"[1]?

Instead they're implementing a spec with broad involvement and support across browsers, it's just taking longer. Seems like exactly how we'd want things to go.

[1] https://news.ycombinator.com/item?id=29405716


> they like a standard (or propose one), they implement it, use it on their projects like google doc, and let the competition deal with the mess

Yes. Exactly what they've been doing with plenty of other "standards"


Which is what the OP is suggesting Google should have done in this case


As someone who has lived through the browser wars, I have no idea what you’re trying to say? The situation today is vastly better than it was back then. It’s not hyperbole to say that porting JS from, say, IE to Mozilla took just as much time as it took to write it in the first place. Today, it’s expected (and often the truth) that something you developed in one browser works in the others.

Also, none of specific reasons people opposed Microsoft’s policies with IE, like it’s attempts to lock people into windows-only APIs (ActiveX etc) apply today.


> I have no idea what you’re trying to say?

In this case, google can pull off something like OP says because it's dominating the market.

> Also, none of specific reasons people opposed Microsoft’s policies with IE, like it’s attempts to lock people into windows-only APIs (ActiveX etc) apply today.

Chrome implements plenty of chrome only API. They like a standard (or propose one), they implement it, use it on their projects like google doc, and let the competition deal with the mess.


Sure, there is a long tail of web API's like this but they tend to be very specialized. They are easily avoided and ignored by most web developers, who likely have no need for them in the first place. (Both WebGL and WebGPU are arguably in this category - you are unlikely to need them for your website.)

This is nothing like the situation was with IE6. Back then basic functionality was half-broken and it was hard to get anything done without a pile of hacks.


> This is nothing like the situation was with IE6. Back then basic functionality was half-broken and it was hard to get anything done without a pile of hacks.

Causes are not 1 to 1, but consequences are the same: monopoly leads to abuse, abuse lead to some site not working with Firefox, consommers needs being ignored by google and them abusing their dominant position to pass what they want as standard, or just destroy API they don't like (see the latest adblock scandal).


What's the difference between Kafka, Pulsar, RabbitMQ and Crossbar.io ? They all seem to be hubs for PUB/SUB and RPC.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: