It is, you are putting your own issue in higher regard just because you don't know someone else’s situation.
When working remotely think ahead and assume your issue/question isn’t as important as you think it is. Because most of the time questions for colleagues aren't as urgent for anyone except you.
You don’t prioritize your personal focus, you prioritize an objective. Most often these objectives are very clear to the rest of the team.
Also I can’t believe you “know” something is “important enough to interrupt them”. I work for a place in which the most “junior” dev is worth a quarter of a million dollars a year. I am not going to tell some dude who is probably figuring out a new way to pack data to save us thousands of dollars a day, to take a minute to listen to me. It better be a fire.
> Most often these objectives are very clear to the rest of the team.
> Also I can’t believe you “know” something is “important enough to interrupt them”
> “junior” dev is worth a quarter of a million dollars a year
So the objectives of what you are working on are very clear and yet your very highly paid colleagues aren’t responsible or sensible enough to understand when it’s appropriate to interrupt you?
When the objectives are clear, we understand our priorities, and there is very little reason for interruption. Today for example, outside of meetings, I don’t think I communicated with a single coworker. I had a few 1-1’s for pair programming, and those were scheduled during standup. Is your organization aware of studies on interruption? It seems nobody understand the problem.
the bad eggs can be in the minority as members of the population, but still provide the majority of interruptions: the good eggs know to be judicious about it, but the bad eggs just interrupt and interrupt and interrupt.
Agreed - so why not deal with the bad eggs individually?
Because at the end of the day most managers aren’t really concerned with productivity - it’s far easier and less emotionally draining to just proscribe blanket bans.
That’s one of the main reasons remote working hasn’t taken off more.
Hey Ammon, the idea is good, it's solid. Nothing bad there. I think everyone knows LinkedIn has it's issues. But like come on. Why make everyone's private job search public? by default no less!?
How can we trust triplebite with our career, finance information and personal information when you pull these kinds of moves. Make a good product. If it's actually good people will sign up.
We're not making anyone's job search details pubic. All that the profile will show is that an engineer created a Triplebyte profile at some point in the past, and any badges they earned.
It'd be helpful for you to spell out what exactly will be public. Even the simple fact that a so-and-so has a Triplebyte profile might be an unwelcome involuntary public disclosure to that person, if they're a current user who didn't read your email and fails to opt out. The (possibly unintended) lack of upfront clarity regarding what exactly will be public by default is also not helpful. Software engineers are probably more likely that other members of society to have strong opinions and expectations about their online privacy, and are probably more likely to be upset if they feel those expectations are violated.
“We aren’t making anyone’s subscription status public. All that their profile will show is the fact at some point in time they registered an account on Pornhub with their email address and real name, and any badges they earned.”
> We're not making anyone's job search details pubic. All that the profile will show is that an engineer created a Triplebyte profile at some point in the past, and any badges they earned.
You are totally missing the point. You think the change significantly improves your product, but your users perceive the change as a massive breach of trust. Why? Because the underlying JTBD (job-to-be-done) for a lot of engineers is discreet job searching. IOW, for a lot of people, a public TB profile would be like having a private Ashley Madison profile [0] exposed to the public. Ashley Madison was a major source of embarrassment for many when they suffered a breach.
Rather than double-down, might be time to step back a bit. The aphorism "the market's perception is your reality" is especially instructive.
I had added TripleByte to the list of resources to use on my next job hunt, that was a mistake.
I have made a note of this singular action along with your repeated refusal in this thread to acknowledge the harm you are causing.
People don't want their current employer to know about their job searches, period. There's a difference in magnitude between this and the Ashley Madison leak, but it's the same concept. Having a profile at all is a clear sign to your current employer. It doesn't matter what you were doing with it or when you created the account.
Given your demonstrated propensity for making previously private information public, shouldn't we evaluate your claim as "We're not making anyone's job search details public yet."
I wonder, what future value will you find by giving away more private information? I know by this example that you won't even wait for the consent of your users before you exploit their private information.
The primary reason people sign up with your service is job search. Having a profile most likely indicates job search and will certainly be interpreted as such by many managers and employers, I expect.
It’s like explaining to your spouse of 5 years why you have a profile on a dating site that started 3 years ago.
I wouldn't call it good, but I'm using Pandoc to generate LaTeX. The whole thing is wrapped in Hakyll, which already uses Pandoc to generate the HTML from the source (org/markdown).
With these things the reality of agile is within corporate constraints. The Big managers will want to steer the company and dictate deadlines or goals. While the pure form of agile might work the reality of agile causes a lot of friction.
Keep in mind though problems also show up with waterfall or young small startups. Its just which flavor of friction/pain project issue you are willing to deal with
Good luck! One thing I think has really tripped up past attempts is there are a lot of variables that can make a difference:
What version of macOS are you running? What are your BIOS settings? Does sleep work? Do CPU C-States work or is it always using full power? Do all the ports on your GPU work, or only some?
Somehow, these things all need to be tracked, and users need to be able to see both exact configuration matches and ones that are just similar.
Projects like these are saying just because we figured out how chairs work, everyone should use the same chair.
It just completely misses the point, people like it when they build something themselves it looks how they like it. Want to spend years working on something that looks exactly like everything else?
I agree - this fear of "reinventing the wheel" needs to go away. People gravitate towards products that suit their needs, and if they don't they'll cook something up themselves. It's really not the end of the world if you're writing something that someone else somewhere wrote. Everything has its advantages and drawbacks.
That’s not what this is about at all. This is simply looking around at people using benches, stools, stumps, and piles of rocks and suggesting we come up with a word to describe something constructed that you sit on... then looking at the nicknames currently being used and highlighting the most common. It has nothing to do with prescribing any particular style of chair.
Has it become a mess though? I agree there are tons of frameworks out there but if you focus only on the main ones there are not more than for the trio of windows/linux/macOS. Heck, on windows only you can use half a dozen frameworks without even journeying to more esoteric ones.
Ultimately there are different frameworks precisely because different people have a different idea about how a UI framework should behave.
To many developers, what the software does is several orders of magnitude more important than how it looks.
There are certainly cases where visual design is much more critical to what you're building, but there are plenty where it's little more than an annoying distraction.
to many customers, there’s a handful of different software choices that more or less do the same thing. so interface and design plays a big role in experience
The point of frameworks is to provide a common operating pattern (familiarity). Frameworks often increase work at maintenance time due to being higher level abstractions that dictate conventions and practices that limit expressive independence.
Where do you think 'select' came from? Long ago we had many UI select boxes in many native frameworks...and decided that was too much work so we made tags...then browsers...most of the disconnect comes because UI controls have so many usages that ultimately you always want to bust out some code.
If OpenUI wants to enhance the default behavior of select, input, credit card, etc, cool, if they just want to build anothet framework then I'd rather use svelte or angular or vue. The large libraries already standardize, its just a matter of who 'wins' out, and there are already only a few SPA winners.
If it’s really about what the software does, then the conversation would be about exposing proper APIs that let me view the data, query it, schedule operations on it, etc.
But then offering a shinier/slightly more bespoke way of doing that becomes a competitive advantage for your product, and now you get why everyone wants to build their own custom UI.
The reason why the aforelinked to Open UI project will never be the One and Only way to build UIs on the web is because there’d too much economic value in being able to do precisely what it can’t do!
My uncle used to work as a radio guy. I remember visiting The National Maritime Museum with him and he just walked up to a morse machine and started writing stories.
Last weekend when we talked he mentioned being sad that a lot of this knowledge is getting lost. Must be a strange feeling walking through a museum and it being the tools of your trade.
That's what I experience at the Computer History Museum (near Google). A high percentage of the items behind the glass were part of my daily life decades ago (punchcards, the earliest TI and HP calculators, etc.) I feel like the Highlander walking through that museum.
Theoretically yes, practically no. If coverage is universal and mandatory, companies will invent all sorts of ways to market themselves to a low-risk subset of clients -- car insurers marketing themselves as women's insurers, health insurers advertising their online capabilities to attract younger clientele.
The clean way to do it is to separate insurance (can be very efficient if privately provided) from redistribution (will lead to bad distortion unless done by the state).
When working remotely think ahead and assume your issue/question isn’t as important as you think it is. Because most of the time questions for colleagues aren't as urgent for anyone except you.