elmerland

I agree with you! It's a shock to the system for a lot of folks to have their code base used that way. FOSS is often a labor of love by very smart folks. If it's legal (and the license allows for it), then it's fair game and hard/impossible to stop.

Commitment to the bit is the only way. None of that “I like it ironically” bs here

I dare you to

Omg legend! I’m jealous because without LLMs I wouldn’t have the talent to create a site as good as https://thebestmotherfucking.website/

Thank you for your service sir!

This site is for the lolz and obviously following the style set by the previous mf websites. I find it cathartic to laugh at the ridiculousness of the situation we are in, but also genuinely engage with the neck breaking pace of change we are all having to adjust to.

And the LLM came up with some really funny lines

Ya, it’s Claude

There are a few bangers in there

It sounds nice in theory, and maybe you could make it work. But in reality, distracting a developer from whatever they were doing has a cost. Add up ten 1 minute fixes and your whole day goes by.

From the customer's perspective though having a fix out in a couple of minutes is the golden standard. I guess that's were team organization and planning comes into play. Having a couple of dedicated resources to address these ad hoc issues, without distracting the people working on larger projects.

I'm confused about this article. On the one side I agree with his point on constant and timely feedback. On the other side I disagree with his dismissal of yearly reviews and weekly meetings.

You need these more formal environments to quantify the performance over a longer period of time. In doing so you can correct for biases, and get feedback not just from the manager but from everyone you work with. Additionally you can aggregate the data company wide to see patterns and hopefully try something new. I'm sure plenty of people do it wrong and that might be a different conversation.

Maybe what the performance improvement was missing was a human touch. Giving feedback without caring for the person can feel cold and calculating.

Why would they make less money by moving to a streaming model? I would imagine more people would go and buy just that instead of getting a cable package. They can also start charging a reasonable amount based on what it costs to produce the content.

If right now they rely on people paying for the channel but not watching it. Wouldn't switching to a streaming model mean that advertisers would be more interested because more people were actually watching the channel and saw ads?

I think they are talking about the more common process of leaving out the pulp and only serving the liquid.

I wonder how do cold pressed vegetable/fruit juices compare to plain fruit juice?

What is the business model for companies like these? They don't collect data like social media sites so advertisers are not as drawn to them. And moderating the groups is near impossible. What was their end goal here?

Do we know which "third party app" had the vulnerability?

lol fair, I was working under the assumption that you believe in the product the company you work for is making/selling.

All things being equal if all you know is their side projects that makes sense. Normally you would have their resume which includes work done at their job. I get how it's so tempting to look at people's side projects as a measure of proficiency. I just don't think it's fair to judge people by their ability to spend hours working outside of work.

I like your point of view. Showing an interest is not the same as rude. I guess I really depends on the person who has to deal with constant questions to handle the encounter with Grace. Which I realize is not fair and people can't be expected to always be their "best" self around strangers.

I admire the author of the article for her confidence and courage. I could stand to be more like her.

If I were interviewing you I would care a lot more about the job you were hired to do than about any side-projects that are not part of your job.

I'm not a fan of recruiters incentivizing "required" side-work. That's the time you dedicate to all other important things in your life (which could be a side project, but it is not in most cases)

Note sure how reliable/accurate the conclusions in the article are. At the very least the introverts among us can use this bit of (confirmation bias) information to convince ourselves that "we were right all along" and extroverts should be more like us.

My 2-cents here I would say that working smarter directly related to developing your leadership skills. You can do a lot more by helping lead a group of technical people than you could ever do/code by yourself.

I would say that non-technical competencies are not optional and they will help your career one way or another. Maybe a better question to ask ourselves is how do I continue to add value in the environment I'm in? I doubt the answer to that remains constant throughout a long career.

You can say that about any language I think. Maybe JavaScript is a little special because of how it has grown over the years and it's general lack of a "rigid" structure or implementation.

That's exactly what I thought! One of best designed blogs I've ever seen. It has exactly what you need and nothing more. Looking at the HTML code its also incredibly simple and elegant! What a pleasure to read

I'm surprised the author didn't mention the main difference between paper maps and google maps. That is, google maps is interactive. With a paper map what you see is what you get. You had to cram as much information as it would allow. But this is not the case with google maps. You can zoom in, out, and anywhere in between. You can't compare the two based on the level of information displayed at one fixed zoom level because google maps is 3D whereas traditional paper maps are 2D.

Completely agree! Nobody should be shamed because he/she prioritizes things differently. As long as people accomplish the job agreed upon, it should not matter that some people are not OK with never seeing their family.

Consider a page like wikipedia. Every time you click on a link to another article a new request is made, the page is loaded along with all its dependencies and resources.

A SPA would instead only get the text of the new article and write it in place. Therefore, removing the need to re-download the entire page again. You can also read about this in the blog post by bloomberg: http://www.bloomberg.com/company/2015-03-24/bloomberg-weve-m...

You make some good points and you are correct that my redesign of the manual is far from ideal in terms of accessibility. I will definitely take these things into consideration and improve upon them. This is not an area I'm familiar with, which is the perfect excuse to go a learn about it!

In regards to the 'experimentation' done by websites. I would say that this 'experimentation' is something that should happen. How else are we supposed to discover new and better ways of doing things than by trying something different. Not all new things are better, and most of them fail. This trial and error, however eventually leads to better design and better 'standard' ways of doing things.

It is unfortunate that today accessibility has fallen down the priority list. Likely, a side effect of all the new ways we can interact with our electronics. So above all let me say thank you! We need people like you who remind developers to keep accessibility a top priority.

That's fair.

Yeah I agree with your comments. Initially I only tested as far down as tablets, because I figured that the target audience are programmers on their laptops or desktops. I will be fixing this issue on the next iteration.

I just checked disabling CSS with firefox. I can still see and interact with all of the content. What type of errors are you referring to?