nartz

Game would be a lot more fun if it were simplified - the betting / offering market / trades go way too fast, especially with bots

Whats said in this blogpost may be 100% true, and of course red hat does do a lot for the community, but unfortunately the damage is done. Its always going to feel like:

* Red Hat was a bastion of open source

* Red Hat sold out to IBM

* Red Hat stopped being Red Hat, and started being IBM by focusing on $$ over open source

* Red Hat reputation degrades as $$ are put first, killing off centos, now this, just downhill from here. >

The lobby is strong with Comcast.

This. As a non film person, I basically have no clue what this does.

Feels like the person who responded has little or no experience with working together with the media and just freaked out.

Sad Day for Centos 8

TLDR: Cannot prepare internal mirrorlist: No URLs in mirrorlist

https://twitter.com/CentOS/status/1487095713238499328

At your next job offer, yes evaluate the work itself, but after you've qualified it, spend more effort seeing if you can connect with the people. Come for the money, stay for the friends.

Best piece of advice, take a stand. Have a perspective. And stay focused on a small amount of things that you care about. This might start out as one thing - which is completely fine. The rest, make sure you set up a scheme where you are empowering others, and there is someone who is directly in charge of other tasks, and delegate it to someone, or a specific team. The worst is when something is "everyone's job" - but make sure that the person who is in charge knows how to solicit opinion and isn't a dictator. Make sure you can use the team to give you the info you need, so you can make decisions. Making (good informed) decisions is your best point of leverage to keep things flowing, but make sure you are making decision at your level (and not too low, which is micromanagement). Feel free to redirect decisions that are someone else's to make. Don't be a single point of failure, empower others. Default to using questions, as opposed to prescribing answers as a tool for mentoring your direct reports. Make sure you are doing 1-on-1's and anything else that lets you see the truth of the state of things, and also so you can see peoples weaknesses and strengths so you can delegate tasks appropriately and coach up that talent.

Meeting with people, Hiring, setting up correct processes are your main tools.

Very few entrepreneurs understand that sure, market matters, and sure product fit matters, however the variable of time is an interesting one. Most startups growth looks super slow, then ramps up, and then quickly ramps up. This is very similar graph to investing $$ with e.g. a X% annual return. The key similarity is the concept of compounding. Individual features, marketing campaigns, blog articles, monetization channels probably won't have an immediate impact, but over time can compound. Similarly, entrepreneurs often think that developing a feature will immediately cause users to sign up. In reality, all you've done is "invest" your money, but you need time to work it's compounding magix.

Disagree with some of this. There is a need to define what 'management' actually 'is'. Great 'managers' are leaders imho. The difference being, that they help inspire and motivate a team, and help contribute to vision, direction, and clarity which a team can rally around, while encouraging collaboration and excellence, and setting clear and ambitious expectations.

Great ICs actually have a huge advantage here, because the key skill for an IC is often technology skills, whereas the key skill for a great leader/manager is trust with the team. Being able to have a deep technical understanding of the problem space will help to develop trust that much faster. However, the key transition is then to get out of the way, and use your knowledge to help challenge ideas while growing the team. The #1 piece of advice is to hold back from giving answers, and instead, challenge people with questions, to let them do the thinking.

Patents should only be enforceable for:

- companies that have a history of utilizing/operating with the patents subject (e.g. no patent troll legal firms would be able to meet this requirements)

- only be enforceable against competitor companies that are larger than a certain size, e.g. more than 10 million ARR, so smaller companies can still be formed and get off the ground

- be different based off of the domain - e.g. it should be very hard to get a patent for software or related items

Very interesting. I like the idea of "virtualizing" the hard schema with views to abstract away some things.

View performance can be a thing at larger scale for OLTP workloads, also, the solution you propose also adds complexity since you have two schemas now instead of one, and as you rightly point out, complexity with views themselves. The question becomes when is this added complexity worth it?

There may be some high-level validity to using gini splitting as a means for 'general' prioritisation to better understand the data; however, second order effects (e.g. assumptions of non-independence between variables) can often dominate, in which case multi-dimensional clusters tend to be a better mental model for logical groupings. The simplest is like a k-means, or other 'embedding' or latent based models calculated from matrix factorizations (CF, PCA, etc) which seek to summarize data into 'topics' or 'categories'.

EU - bless their souls - as soon as something interesting comes along, they immediately feel the need to regulate it globally, and often, very badly. GDPR-AI here we come.

By speaking out about cancel culture, he is technically defending those who have been cancelled - thus he is only 1 hop away, and by his own equation, should be cancelled.

The key is NOT the phone itself, but the APPS and the Use of the phone.

Author seems to be struggling with the connected-kid culture around apps like Instagram and TikTok - which are transforming the school-based culture to something where to be popular, you have to be connected and posting. This is what needs to be controlled IMHO.

As many mention, there are MANY positive uses where the phone is a 100% better medium to teach or learn than old school books or otherwise.

With my kids, I focus on installing and limiting the games and videos to ones that I find productive and educational.

A lawyer tried to climb everest, and instead ended up in a lawsuit.

Thats why lawyers are lawyers.

You could ask for a success based incentive.

This is over simplified. It's better to lose a finger to an infection or cancer, versus have it spread to all parts of the body. Its the same thing with fiscal policy.

Everyone wants to blame someone - e.g. its the governments fault! In reality, its just an external force that everyone is dealing with, a plague, if you will - its not anyone's fault; it just must be faced, that during a plague, there will be suffering, and there will be casualties. It's that simple.

Rock on - so true - the web used to be a safe place to express oneself; now, saying the wrong thing results in hundreds of negative comments and F/J-finger wagging.

It would be great to get back to more individualism on the web.

Just an idea - put a link to longtermstockexchange.com into your blog post, preferably at the top, with how people can use or buy into it

Overall - I feel the author's pain here - and yet - it does feel a bit like he got burned and this is a bit cathartic.

The first thing is - this is the industry we live in; especially for small companies, it should be expected to have to handle or at least support tangential roles; it should be expected to have more responsibility and lower bus factor; it should be expected that processes, code standards, etc are not matured since this kind of thing often takes time.

The second thing I'd say, is that there are different personality types. Sure, no one wants to be stressed out; but there are a good amount of people that prefer these smaller-company challenges over sitting in large architecture review meetings for months working in a waterfall format (the other extreme).

Some people like to work in a comfortable role, with a predictable schedule, and just color within their lines with the technologies they know, and go home. Others actually appreciate the challenge and difficulty, and see an "on fire" situation and attempting to level up and see if they can get everyone rowing in the same direction, put processes in place that will last, train discipline and standards, and make it a better place to work.

The third piece, is that what I've described thus far I would not use the word "Toxic" for. I would not consider "overworked" to be the same as "Toxic" personally, since it is each person's responsibility to make sure they are lookin out for their own health, and working to an acceptable and sustainable standard. Sure, employers are always going to want you to work more. That said, the line is crossed when the employer demands or forces workers to work beyond healthy or sustainable limits, especially when the worker has clearly communicated these (often, this second part is what is the failure of many devs) - if that limit is crossed, this is what i would describe as "Toxic", including any sort of employer speak which could be described as "abusive."

This looks cool - but it would be 100% cooler if it was just a wearable, that I could customize to use with other games - for instance, World of Warcraft, punching to initiate an attack, and different motions to use items, 'click', etc.

I can't imagine using the wearable very much if the game itself isn't compelling - which, from the movie, looks a little wack

Hey guys - here's just some critical feedback from a fellow dev - here's my n of 1 perspective - of course this could be a very different perspective for e.g. large enterprise companies struggling with this.

Feedback:

It seems overly complicated. You lost me when you said i have to train models? Are you assuming that software developers want to train machine learning models to do something as simple as creating some test data? In reality - I reach for tools that make things easier for me, which includes not having to read a ton of documentation, download new external tools, and things that 'just work'.

It is 100% easier for me to export a little production data to test on (and maybe sanitize), or to write a small script to generate a few users and those things I need to test. Plus - then I know exactly what I'm going to get. A lot of times, after I've done this once, it will work for a good while as well - if I do change the schema, I can add some additional data for that column, and go from there, or otherwise.

For those companies who have 'messy' fixture data - is the tool the issue? My take is that the difficulty with maintaining the data could contribute to this issue, but is also more an issue of simply bad housekeeping - e.g. rushing and not tending the garden. While your system might handle this, your system also seems to require a different skillset (e.g. specific training/knowledge) than the standard QA developer might have.

If I did use it, i'd prefer it to be much easier to use - if I could include a ruby gem, and incorporte it into the testing progress, e.g. an 'after' hook after migrating the db, that would be ideal. Then, I dont really need to know much. However, I would still be concerned about whether this is deterministically creating data or if its random?

Good luck!

There is a spectrum:

Quality+Speed+Efficiency cowboy coding |0-----1------2-------3------4----5| perfect iphone

I would never expect a startup to be operating above 4 or 4.5, it might mean you are spending too much time future proofing.

The best teams operate around 3 or above, but they can do so because they are experienced, disciplined, trust eachother, have a set of tools they know very well, and can move at a quick pace because they automated a lot, have code patterns they follow and are not "re-inventing the wheel" or trying new frameworks for fun.

A LOT of startups are being started by inexperienced developers, where they jump onto some new language or framework, and end up doing a lot of non-core work due to inexperience and due to choosing some nascent framework. This immediately puts them at less than 3, probably between 1-2.

If you are at a 2, i would say you are doing OKAY, any less than that, and I would say you probably are suffering from inexperience, bad choice of frameworks, no tests, etc.

If you make it extreme, then its easier to see the folly / error -

500/1500 students + 1/3 students = ?

Why are there no repurcussions for what essentially amounts to fraud? Why is it acceptable for politicians to commit fraud, but not for anyone else?

Thanks for this - but its the age-old argument of dynamic language vs static/compiled language mixed with hey bloated libraries! and hey bloated features! etc.

0. Performance isn't everything, especially to a lot of companies where having something at all is more important than just being the fastest

1. Dynamic languages are generally require less LOC, which generally equates to faster implementations

2. Rails, Django, <your favorite dynamic language framework> sure are generally bloated, but being able to drop in a library for nearly anything you need cannot be overlooked. Especially for small-midsize companies, spinning up another app server is generally easier than writing a whole bunch of multi-threaded code.

3. The appserver is generally not the bottleneck, rather, of course, its the database.

This is extremely context dependent. For instance, a dev has to consider:

- guess whether or not this is an isolated case, or whether or not this will become core functionality

- a self-assessment of the true difficulty of the problem

- a self-assessment of their own skills and knowledge in the area

- security reasoning

- API access/readabilty for other developers to use this code

- maintainability of new code

I have personally seen personal implementations that lead to bug, after bug, that have already been reasoned about in equivalent libraries.

Often for the simple fact that other devs who have to work on this code, its likely that the abstraction and readability of a third party library is probably greater than the 'quick-and-dirty' implementation.