bl4ckm0r3

lot of people here are criticising the set of features stuck together or "janky crap"...I don't know where you work, but I have seen a lot of that in all my career, and still do... and it was done by humans. The difference is that ai is doing it faster and can also quickly change it in the future, so not really sure it's the same level of problems. This is a big change in how we think about software development, bugs, and features tbh in terms of speed of reaction, identifying problems and caring about janky code or performance, because solving those problems, if they present themselves, is cheaper than before.

that's an authentic photo, not the subject/image, the photo is authentic.

imo basic android tv os works better, i have a nvidia shield and it's good too (despite being old now).

you are amazing thanks!

this is great thanks a lot! on a similar theme...would anyone happen to know a public db like this but for workout exercises (with images/videos)?

I thought exactly the same things about the illumination, i feel like it's too much "look how cool rtx is" and not enough "this should be scary and dark". In this, and other demos, i also felt like refractions are exaggerated, like floors that seem like mirrors is not really realistic to the end user. Sometimes it reminds me of when hdr pics came out and everyone was overdoing it. (But it should be a settings problem more than anything else!)

If one was a coder once, they don't need to keep coding to understand what a coder does. Plus it's a bit hard to be a manager of different profiles and different stacks and understand what everyone does from a coding point of view (different stack, different frameworks and abstractions etc) especially while time passes and tech changes so much, so quickly.

I do agree that it's important for a coder to keep coding but mostly for the manager itself as it's removes some of the old biases and it's a continuous learning process on something that, technically speaking, they should be passionate about. Plus it does help to have conversations with other developers and don't sound like a person who only listens to vivaldi at a dnb concert.

I have wrote an article a year ago about this. https://medium.com/fever-engineering/on-hiring-great-talent-...

tbh it's very hard, in general, to assess someone skills in ~1 hour, with the diverse set of problems we face everyday and people/companies often focus too much on "previous relevant experience" (do you know this?) instead of thought process and depth of understanding (how much have you understood what you have done) which, to me, gives more insights on someone personality and attitude and ability to learn new things and becomes harder to cheat on (you can memorize "cracking the code interview" and be a hero on leetcode and still have no idea about how to write good software, take decisions or work in a team :)

I'll have to correct you here, while i am sure you can find (as i found) real parmigiano or in general good cheese in the states (by paying a lot of money for it) the law allows for additives to be added to it. In europe this is illegal, you cannot have additives in parmigiano (solid or grated), and if found normally the product is retired from the market.

In general the FDA in the US is much more liberal in favour of the industry, sacrificing quality and this apply to several products.

(For example i found out that in the US the minimum amount of chocolate that has to be present in a chocolate product is like 10% and in europe is 25% (if i am not wrong) and the amount of max sugar is also different.

Said this, you can eat all the cellulose you feel like eating, but I think it's wrong to 1) charge for it as if it was parmigiano and 2) sell it as an italian product.

ps regarding your humidity comment

"Alaska is one of the most humid states! In fact, Alaska reports an average RH of 77%, with the next highest state, Florida, reporting a 74% average. Despite Florida being hot and balmy, Alaska has high humidity levels because of its milder, lower temperatures."

https://www.currentresults.com/Weather/Italy/humidity-annual...

Procedures and ingredients quality are not respected in counterfeit products (for example it's acceptable, in the us, for grated parmesan to have cellulose/wood pulp in it) and they still sell you the stuff at a high price. i don't think anyone died because of these products but if you take fake parmigiano it's a $2B market.

https://www.foodandwine.com/news/amount-wood-pulp-grated-par...

https://www.cnet.com/home/kitchen-and-household/parmesan-che...

https://www.forbes.com/sites/larryolmsted/2012/11/19/the-dar...

in the same society there are people that don't follow the bad habit advertised by society and with the amount of information and alternatives present today, I am sorry, but it's too easy to blame "society" and wait for someone else to do something. It's up to them. The solution won't come from anywhere else and yes, we can simply be better.

priority matters though, if you want to go full Apple with UI/UX then you need to lock the UI/UX for years, like Apple does, and refine every little thing to bring a fully ecstatic UX to the user. Or accept that most users won't notice that or wouldn't mind it behaving like that and build new features that will bring useful behaviours to the app (and revenue to the company). If you have to spend 50 hours to explain why it's a bug, most likely only you care about it. In some cases it may matter to be THAT precise with UI/UX and it's cool, not saying i don't appreciate quality but you can't have everything. One thing I'd like to point out is that most of the time it isn't even a matter of priority, lots of dev energy gets wasted in useless refactors and picking "the right library/framework" and building the "next outdated design library", instead of being used to improve things ;)

it's not magic, processed food is something recent, sugary food/drinks is something recent, bad habits and lazy sedentary life is something recent. if you don't see this then I don't know how to explain it to you. It's habit related and habit can be fixed, pills are not the best solution in my opinion.

there's studied that say between 1 and 2 years, that sounds like short time to me.

1% of people have that root cause. The stuff I have seen in the united states is not root cause it's just bad habits. happy for them to get any pills, injection or whatever they think they need to feel good and better. Lazy people, lazy solution. We'll see long term how that works out, as much as anything diet related the usa has implemented in the past 50 years.

yeah the reality is that people are going to take it in waves to "fix the mistakes they did in the past 6 months".

it's not unfair, the whole history of scientific progress is to cure unsolvable things with science. this seems pretty solvable to me ;) it's pretty much the same as giving everyone anti anxiety pills cause it's less effort than fixing the root causes.

that's great, but it's not proper training, it's a hike, fantastic activity but (especially growing older) our life is mostly sedentary and it helps a lot to do a proper sport or intense activity at least 3 times a week (i personally workout every day, but sat and sun, for 1 hour with a high intensity sport, not weightlifting). The older you grow the harder it is for the system to process the amount of stuff we eat (especially high calories, highly processed food that is available nowadays) and doing a high intensity activity (heartrate up, muscular stress etcetc) is, in my opinion, fundamental and often ignored by people.

This approach will definitely save someone's life (and probably already is) but there's no golden pill that will, long term, give a healthy, in shape, body to people without effort.

Eating disorders are a thing and often have to do with the mind or genetics, but there are so many people just letting go to cravings and having terrible habits when it comes to eating, don't want to do any sacrifice and just let themselves go for so long than it becomes a serious health issues for them.

I see plenty of parents feeding the kids like they are going to do foie gras out of them... People eating pastries like it's chewing gum, bagels like it's a snack... some of my American colleagues have never drunk just plain water...only sodas...and a lot of it.

I really feel like this is just the trick the food (and healthcare) industry was waiting for to allow those people to eat as much as they want and don't get fat (and possibly get ill later), and the fashion industry to push for a "cheap way" to reach beauty standards (which is why this practice has mostly became popular thanks to famous people using it).

Plus there are pretty common side effects (1 out of 10 experiences them) and it fundamentally creates a dependency to a drug, because without changing habits, if a patient stops using the drug, they'll regain the weight in a short time...

Most people think they have a condition but in reality it's just them not trying to solve the problem and complaining about it.

quick question, do you do any physical activity? or if your hormone imbalance did not allow you to do it, now that you have a different medicament, have you started doing sport? Not just a walk in the evening, like minimum 3 times a week 1 hour of high intensity workout, possibly supervised?

finally! now george rr martin can finish his book.

What I love about this is the narrative around loyalty like we are some kind of samurai. A company gets all the benefit to call itself "a family" and to push employees to be loyal to the company as there's a high cost in offboarding and onboarding people (knowledge, morale, the fact that new joiners aren't really contributing at their best capacity for the first 3/6 months at least depending on seniority etc). Even during resume screening there's always a lot of questions on why people "jump" from a place to another if they have changed jobs every two years.

But a company makes mistakes (over hire, product line that don't work, market expansions that don't bring the expected results, overspending etc) and never talk about this openly (the responsibility is always on the market, the situation etc) and often they have obligations towards the investors or the market (if they are public).

There's also a psychological burden in changing jobs (impostor syndrome, fear of something unknown, new domain etcetc) and companies use this to convince people to stay. Most of the job of a people manager is to convince people that they are in the best place they could be and focus them on new challenges so they don't have time to think.

Don't be fooled by any company, if they think they have to fire you because some spreadsheet calculation told them it is the best thing to do, they will.

tldr; Decide what's best for you (and your family if you have one) and never feel bad about it. Loyalty is not a thing in the workplace.

ps i have personally witnessed and went through horrible situations where managers had to openly lie about people performance and fired a bunch because the company made bad predictions over their expected revenue and had to fire people to "prove they were doing something about it" and show some cost reduction to the investors. Once a ceo literally cried on hangouts while communicating the decision to fire a whole department, and the day after (while those people were still part of the company) did a whole motivational speech about how that was going to be the best year for the company and we had a lot to look forward to.

I think you just found out the roots of every religion.

I think you identified the selling point of OOP, it's easy to reason about it and logically it makes sense to human because we do think in terms of objects (the user, the order, the item etcetc) and responsibility segregation (User->login(), Order->fulfil(), etc). To your example of just launching intellij and using java (or ruby or whatever) to build something, yeah it works and it works fast and it's easy to add new features, and it's also easy to end up with a >3k loc User class in python that no one can touch (true story).

OOP is easy to understand and explain and it makes sense initially, plus a lot of people specialize in languages/frameworks that enforce it, so it becomes easy to get trapped in the OOP world. It also usually comes with DDD (which is a solution to a problem you shouldn't have had in the first place) which is a way to limit the damages of OOP into contextual areas. I also think the blanket statement (OOP is bad) does not apply necessarily everywhere. A good mix of composability and a bit of inheritance where it makes sense is the best way imo.

"Giving the user a choice to pay less and run their own binary of netflix would solve most of those issues" why? netflix works well for what they want and how they want it to work. you can download things to watch offline already and the rest would benefit just a small percentage ot the world, which already has money to pay for the service. I agree that p2p would be a great solution to networking issues, but am not sure about the legal/technical consequences (again) worldwide.

"let me have a copy locally" is a very naive view of the world. 1. netflix works also in places with horrible connections/terrible bandwidth 2. what would you do? preemptively download all the series, movies etc that they think you'll download? (that may work in places with good internet, but even there, how much disk space would you need like on a mobile device?) 3. most behaviour on netflix is "let's try to click on these random series/movies and see if i like it" so you'd be downloading things that you'll never come back to see.

I am not sure i understand your point...plus netflix has the HUGE problem of optimizing the stream as much as possible to give people fluidity in their experience (exactly for the - low bandwidth - connections)

100% agreed, as I mentioned in house knowledge (and engineering size) matters when deciding this. In your example, if you only have recent graduates in your team you have a whole lot of different problems :D In a more common setup (some seniors, some juniors) given they will have to learn something on the road anyway, wouldn't you want to, for example, use managed services instead of "boring" services? Use svelte instead of angular? use flask instead of django? or fastify instead of express? And if you go boring because there's more literature on them, you will soon find out that most of it is confusing as it spans over the years (have you ever used springboot? so many different ways of doing things that evolved in time...) and in the beginning you'll end up using the - by the book- approach which does bring some complex problems (try refactoring the auth module out of an app).

In the end what you are doing is moving the problem of figuring things out later in the future, when things are much more complex and refactoring is much more costly.

But I agree with you in the end it depends on the org, which is why you should not choose boring tech by default, and not choose cool tech by default either and think more about what would really give you speed of execution and maintainability in an always changing business domain AND keep things small enough that can be refactored out in an as-easy-as-possible way.

ps of course this is after like the first year of your startup, there's no point of doing any of this, or even choosing any technology if your company dies in 3 months.

pps i still don't understand why early stage startups don't do everything in javascript (FE+BE) so the same engineers can contribute to both part of the stack and then decide what to change depending on the business needs

I hate this, as usual all blanket statements are false assumptions. The presentation is mainly focused at new paradigms but technology is there to help us fix problems, and I totally agree that jumping on a cutting edge tech is very risky in most of the cases and can end up in wasting a lot of time finding workarounds on either limitations, bugs or immaturity of the chosen tech, BUT my problem with this is "where do you draw the line?". Is an on premise service boring tech? should we use that instead of aws? Is github actions too cutting edge? should we keep using jenkins for ci/cd? etc.

It really depends on so many factors (like in house experience, really understanding the product and engineering needs, costs etc) and it does not take in consideration the "problems" of boring tech and why modern tech has tried to solve or avoid them.

The last director who mentioned that to me and built everything in django and had huge scalability issues and took about 1 year and a half to refactor a part of the app to move away from context and orm.

In my opinion the only thing that matters is "how coupled are you with the tech and how optimized for deletion and change is your code/infra"

what is this giving you more than using svelte or something like lit-html?

https://mickael-kerjean.github.io/example/counter

looking at this example (i personally don't like the template string for dom because it's a bit of a pain to read and you need a lot of manual work later, separated from the definition of the markup, to add eventhandlers etc) you rely a lot on rxjs to handle state and IMO it's a bit hard to follow what is going on, compared to https://svelte.dev/repl/f5acc8113ec14bc7946eff9687916fa1 for example