> You can disable any chat outside a curated group of friends
IMO public chat should be disabled by default for U13 accounts, not the other way.
651 karma · joined June 7, 2018
IMO public chat should be disabled by default for U13 accounts, not the other way.
Right. Company's finance is based off on 1) letting game devs sell loot boxes freely to children. It's a legal slot machine for kids 2) paying developers with their own currency which then can be converted to tangible currency
These should be illegal
I stopped expecting meaningful career growth at a company. It's easier to grow by jumping ship, plus it widens your perspective.
When I was a bit more junior, I asked if I'm performing at your expectation and what I should be doing if not. If there was a suggestion, it was a typical generic statements that didn't add much value.
Whether a manager "cares" about their reports or the company is going to matter a lot. I find most people don't care much. I had this one manager who cared both. We built the entire platform ecosystem company relies on, and I still chat with him every once in a while :)
I don't think it's all junior engineer's laziness to get things quick out the door. I recently worked with several, and many prefers to "do the right way". However, there are bad managers who wants to get things done quick so they can climb up the ladder. One junior told me his 1-on-1 with manager told him "don't think too much and get it done". The current market is tough for junior devs so they'll do whatever to please their manager. What choice do they have? Rather prefer getting PIP'ed?
And it's funny how the current market is considered "bad" because software companies earnings are clearly not that bad. Perhaps our greed has peaked and the only way to pocket more money is to squeeze every drop of juice out of employees to get the product out ASAP
Getting paid 250k/yr with 20% downpayment isn't enough to afford a house with 2 kids, so providing a "free" or "afforable" housing to those who aren't currently employees is only going to upset those who are working hard
IMO govn't need to relax the regulation to build more houses and drive the cost down
I completely agree with Finland's approach though. Permanent housing is the minimal requirement to reduce homelessness. Without placed to stay, mailing address, security, it's difficult to get out of homelessness
Using the example they provided:
1. Validate payment
2. Check inventory
3. Ship order
4. Notify customer
I'm curious about case when one of the operation times out. The workflow engine needs to then either time out or it may even crash before receving a response
In this scenario, the only option for the workflow is to retry with the same idempotency key it used, but this may re-execute the failed operation which may have been succeeded in the prior run because workflow did not receive the response. The succeeded operations would skip because workflow has run completion record for same idempotency key. Is that correct?
"presumption of innocence"
Otherwise we are no better than a mob
True. Also it should be the managements'/team leads' role to act as a midiators. It's a waste of time to constantly argue over what is "right" when all proposed solutions are functional.
Should we spend more time flushing out the unknowns? Should we launch ASAP and interate fast? Should we automate the process? Do we have data to back our assumptions?
The "culture fit" is not superficial and I've always been advocate of fire fast if one is culturally unfit because it slows down everyone
1. Clients will do whatever they need to do get their job done, even if it's not the publisher's intended way
2. Clients don't read documentation
3. Bugs will become part of API once enough clients rely on their behavior
4. The number of API calls does not necessarily equate to importance.
---
As such, I aim for the following when developing an API
1. Ship the beta API early and see how they use it to minimize the surprise. (This may not always be possible)
2. In most cases, bump up the major version while supporting the previous version. This means you'll need to define SLA for your API
3. Most clients are OK with breakages as long as they are given enough time to migrate, or the API provider gives them a tool to auto-migrate the code (if that's possible in your product)
Isn't live streaming at scale already solved problem by cable companies? I never seen ESPN going down during a critical event
2020: 427,200 2021: 398,300 2022: 474,300 2023: 386,600
[1] https://www.uscis.gov/sites/default/files/document/reports/f...
Title would've been better fit "How I climb the ladder at big tech companies"
Meta should also be forbidden from using any features derived from this data, or open source any trained model from the data. 1.4B settlement is too small compared to the long term gains of a company
Safety
https://raw.githubusercontent.com/meta-llama/llama-models/ma...
> 2. Additional Commercial Terms. If, on the Llama 3.1 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee’s affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights.
It's a very unfair(?) place to be for an app devs to pay the % tax when Google spends one-time fee for reviewing the app + other I/O costs
Hard to say...
You're effectively trusting the liar they wont lie again
Its possible they leak it to high profile customers without publicly announcing it
Business should make decision assuming the data will be leaked eventually regardless of random paid or not
Perhaps only thing business can assume is the data wont be publicly released in short amount of time
- Steve Jobs
My current employer has similar problem. Company hired executives from a certain company about two years ago (hint: nepotism) and shifted towards incentivizing teams who met OKRs and OKRs were only product focused - features.
Though this makes sense on the surface, what it ended up promoting is doing whatever to meet the OKRs. Short-term solution was often acceptable leaving huge tech debts and it is hard to justify doing anything to maintain system complexity in a reasonable bound because they do not directly correlate to an OKR.
Personal developments aren't part of OKR so junior engineers who should be focusing on learning struggled.
Team collaboration became a hostile because dependent teams will call out other teams for blocking a feature releases.
Executives shared during all-hands their intent isn't to neglect personal development or team collaboration but problem was it doesn't matter to employees because those aren't what's incentivized.
Perhaps if the team or personal performance review required feedback from them (360 degree) and takes a non-negligible portion, then things might have been different but it's still all about what I got done
The scene of downtown was something out of a dystopian movie where you see wealthy people walking by a drug addict with needles on the ground and yet everyone appears to conform that this is the norm
I'm definitely oversimplifying the problem here but intuitively shouldn't a city with high income have more money to spend on infrastructure?
Where are the taxpayers money spent on?
I think it'll be very atypical for a companies who doesn't use any of the Oracle product to use proprietary Oracle Java and pay for the support
LC was obviously to prep for interviews which are time boxed. This means for each problem I had to:
- plan, come up with a pesudo-code and verify the correctness *before* implementing it
- write concise and readable code
- make practical tradeoffs
LC isn't fun. Maybe it is for some folks but it was discouraging for me to some extent since it made me compare with folks who can solve these problems when I'm clueless
But this was the eye-opener at the same time. It was shocking to see someone can solve the same problem with less than 10 lines of code when my code is 100+. It taught me what parts of my code was unnecessary and also some neat tricks certain languages provide
This isn't to say I'm LC God. I still suck at LC but what I appreciate is I get better little by little. I tried a medium level question last night after more than a year of break and couldn't solve it haha
I see your point about creativity. I think algorithms are mostly memorization. I'll never be able to come up with KMP algorithm or gift wrapping algorithm from scratch. However, how to apply these algos on a problem or transforming a problem into another problem that can be solved easily is creativity IMO
I do have ADHD as well and my advice is this is something you have to solve with pychaistrists with different meds and therapies.
LC is not fun but necessary to be a good engineer IMO
Count seven of wire fraud in connection with a wire transfer of $99,999,984 on or about Oct. 31, 2014:Guilty.
Count eight of wire fraud in connection with a wire transfer of $5,999,997 on or about Oct. 31, 2014: Guilty.