373 karma · joined July 15, 2019
Once they lock down the authorization permissions they ought to reconsider whether they really need to be displaying that data all over the place.
Have you ever had someone join your team and immediately start lecturing you about this best practice and that design pattern and how the current codebase falls so far short of them? I don’t want to be that guy.
But that makes me hesitant to talk about whatever cool new thing(TM) I’ve just stumbled upon. If I mention pyo3 offhandedly (I.e. “I thought this was cool what do you think?”) will people think that _I think_ that we should rewrite everything in rust (and then port it back to Python…)? That’s a sort of paranoid thought pattern but - unfortunately- it is one that I observe myself falling into.
Their Twitter [1] seems like a generic crypto outfit.
Wonder if Bloomberg just loved the irony of the name? I did.
If the only function of this is that I feel socially pressured to _not_ be on a group chat or programming, then this does the trick.
Disclaimer: will try during the work day tomorrow. Have not tried the site itself.
If you do ask these questions, at what point in the interview process (or within a given interview) do you ask them?
It also provided some interesting background on how this level of nepotism might have come about:
> Ms. Jones, Mr. Lloyd’s [The author] lawyer, argued that Google’s relationship with ASG [contracting agency] allowed members of the Fellowship to join the company without being properly vetted. “This is one of the methods the Fellowship used in the Kelly case,” she said. “They can get through the door without the normal scrutiny.”
[1] https://www.nytimes.com/2022/06/16/technology/google-fellows...
I understand that this is a marketing gimmick. It just didn’t quite land for me.
Second this. I use sublime text almost exclusively for this purpose. I have one file called daily_notes.md that has everything from meeting notes to formal writing to pasted error messages and code.
Each day gets an h1 but that is the extent of formal organization. I’m actually decently organized (at work, at least) but the simplicity is all about lowering the overhead of jotting stuff down. Keeping everything in one doc makes for very easy search.
Otherwise, I try to write reminders right away with whatever is handy. Mainly: Post-its, slack reminders, and Gmail scheduled sends to myself.
Products with (really) rough edges is part of working at a startup. You may be dissatisfied with what you’re shipping but it is all about how much it is solving your customers’ problems.
> Unethical practices.
This should definitely inform whether you stay or go as well as how much trust you can place in mgmt/co-workers.
Unethical practices by no means imply that a firm will fail. For that matter, dysfunctional firms don’t always fail either.
This sounds rather annoying but I don’t think that it is a sign of a failing startup. I’m extrapolating a bit here but: Your manager and PR reviewers may understand the technical aspects of the code but may not understand the big picture “why” of it. If you’re working on something, then someone within the firm - a product/project manager, a salesperson, the CEO - must be advocating for it to be done. Seek them out and build up a direct line of communication. You aren’t usurping your manager by doing this, you’re understanding pain points better and helping to build team cohesion. (That sounds like word salad but I mean it.)
> there were also laws passed that seem to be our current business model.
This is concerning. But - then again - maybe you’re misreading the law. If you don’t have the means to bring this up comfortably in an all-hands or 1:1 context, then this is yet another reason to build relationships with other employees outside of your direct chain of command. Sales and product people should definitely be knowledgeable of this sort of thing. Find a way to bring it up in conversation on a call (“I saw this article in the paper the other day...”).
> Application error: a client-side exception has occurred.
But from the other comments I get the impression that “button syndrome” has something to do with UX/accessibility. Tad ironic.
As someone who doesn’t specialize in security, one claim that has stood out to me for not using fingerprints is that you can't run bcrypt (or some other salting algorithm) on fingerprints [1].
I don’t see any discussion of that here thus far. Is that still the case? I feel like I would have heard about developments in this area if something had changed. But perhaps I've always misunderstood the criticism?
[1] https://www.rsaweb.co.za/fingerprint-security-fingerprints-a...
This tidbit suggests to me that it might be useful to delineate between the two archetypal tech contractors:
1. Less experienced workers who are having trouble breaking into FTE world. They have to work through agencies (who take the other 75%, which is perhaps high but not by much).
2. Experienced engineers who maybe have niche expertise or just a strong track record.
When you talk about FAANG comparisons, I think you’re mostly talking about the latter group.
There are gains for the employers potentially. But these folks also tend to have more bargaining power. At a certain point, working for a “cool company” may not be all that exciting. Instead, they just want to consult.
(Also, I think other have made good comments re:benefits.)
- It was given away for free for years. During that time people wrote _reliable_ numerical packages that other people glommed onto.
- matlab users aren’t programmers, they are [engineers/mathematicians/etc.] who need to write some code to do their job. One aspect of this fact is that they generally aren’t on the hunt for a new “framework” to do this stuff. They also aren’t thinking much about long-term maintainability: they ran it once and got the answers they needed.
- Academics (and students who can use university licenses) are price insensitive.
- Engineering disciplines where errors can’t happen (civil, aerospace, etc.) come to rely on aforementioned reliable numerical packages, which eventually required proprietary licenses.
In other words: I don’t need a rule per se, just an argument. I’ll work out the contingencies on my own.
> The Amazon webpage linked above says Sidewalk "is currently only available in the US."
As I understand it, this is exactly what new pharmaceutical sales reps are asked to do?