rantallion

> I can't put the url as it's the same blog as the one from march

So you mean nothing has changed and this is a duplicate of old news?

If you're planning on using a static site generator that can also generate an RSS feed, it's trivial. Hugo can update your RSS feed and dev.to can consume that feed. No APIs to set up.

I'd agree with this but also add that it's important to know the benefits of each algorithm compared to others in the same class (i.e. when you'd use each sorting algorithm).

It also helps to be able to adapt an algorithm when the vanilla version doesn't quite cover what you need. I don't think I've ever had to implement a well-known algorithm from scratch at work - I'd just use a library for that and spend my time focusing on business logic.

There's no simple answer to this. It depends on where you live, what languages and technologies are in demand in your area, and how strong you are with them. Years of experience don't mean anything - we've all worked with bad devs with long careers and good devs with short careers.

Check out job listings near you. Interview for a few of the better paying and more interesting sounding roles. See which ones you're well-suited to and take it from there - you're under no obligation to actually accept any of them if you don't want to go through with it.

Developers aren't just the folk writing the code. They're the folk taking the vague, wishy-washy requirements from a product owner, asking all the right questions to figure out the real requirements, and then writing the code.

I'll worry about job security the day that an AI can figure out what a product owner actually wants. Until then, I'm still the interface between then and whatever fancy AI or low-code/no-code solutions might be around for the last step.

I don't remember the last time I saw a group of antisocial youths drinking espressos. Cans of energy drinks, on the other hand...

You're just describing a modular monolith (with or without a decomposed database). It's not a new concept, and plenty of us use this approach already when it makes sense to.

Except for the fact it's backed up by independent studies. Of course people will blow their own trumpets - in this case, it's justified.

Top 3 results for me on 'remote working productivity studies', and there are countless more that come to the same conclusion:

https://blogs.lse.ac.uk/businessreview/2021/09/29/remote-wor... https://www.forbes.com/sites/bryanrobinson/2022/02/04/3-new-... https://www.apollotechnical.com/working-from-home-productivi...

I find this comment interesting as a single example, especially with the data that's available on the topic. So many studies showing that remote and flexible working arrangements result in objectively higher productivity. At the same time, recent surveys show that people don't trust their colleagues to work hard while remote.

I'm sure we've all encountered someone we perceive as a lazy colleague. I'm also sure most of us will agree that data trumps anecdotes. If we accept that the the studies and surveys are all correct, this means that we're all being pretty tough on our colleagues despite their (overall) high performance.

https://www.zdnet.com/article/working-hard-or-hardly-working...

Popular? Most of us hate it with a passion. Smartphones are the only reason anyone's making vertical video and only then because they're too lazy/dumb to rotate their device 90 degrees.

No, they're right. It sounds like you're inexperienced with the tooling and should spend some more time with it. That's not even a criticism, just a truth.

Take this:

> These things typically produce tens of thousands of lines just to add simple libraries.

If you're ending up with a bundle that's thousands of lines long, you've done something wrong. My team use esbuild to bundle code for AWS Lambdas and usually end up with minified code under a couple of kilobytes (though admittedly the bulkier stuff sits in a Lambda layer - since, you know, bundling everything under the sun would be stupid).

You have no commitment to any of them, even after you accept. From the other side of the table, they expect many candidates to spend time preparing and interviewing and will only offer one the position - that's no different from you assessing multiple positions and choosing the one that fits you best.

Having been there myself relatively recently, I can see why you'd initially feel guilty. If you get more than one offer, pick the one that's best for you and politely decline the others. They may come back with a higher offer if they really want you but I wouldn't suggest getting into a bidding war or you just risk annoying all parties and ending up with nothing.

Finally, don't burn any bridges. If you worked with a recruiter, stay amicable - you never know when you'll be using their services again. Even if you applied directly, you may want to revisit their opportunities next time round.

You can divide those 1000 women into two groups: those who had abortions and those who were denied them. Please explain how you divide the 1000 children into two equal groups of aborted and survived and compare each group.

So if I have this right, NFTs are a way to hand over a wad of money to get a receipt back that demonstrates proof of ownership of something that isn't in your possession and which can be deleted/modified/copied at any time, and your tool is a way for buyers to have increased confidence that the thing which can be deleted/modified/copied at any time is in fact the original? I think I'm too old for this nonsense.

Your tool detects 'fraud and forgery' of something that no-one actually owns? How exactly does that work?

The author clearly hasn't heard of the Utin Jääkärirykmentti and doesn't realise that Finland have some of the best special forces in the world.

You want the job to still exist in 6 months, right?

Of course it won't. Who's making the tools that let people make things without programming?

Checking out their projects (if they have any and volunteer them) is fine. Just as long as we don't expect them to have said projects.

I can see the argument for a candidate seeking their first job in IT needing to distinguish themselves from the rest of the crowd and how a couple of well-executed projects can help with that. However, it's unfair to expect that any candidate must have projects, especially if they're already in employment elsewhere - few of us have the time or the energy to put into projects of passion after we've done our 40 hours and taken care of other priorities.

Neat idea but I'm not sure it scales to handle the sometimes hundreds of tabs some of us hoarders have open at once.

So we're starting to see the intended consequences of a decentralised and unregulated currency.

"By default, Next.js pre-renders every page. This means that Next.js generates HTML for each page in advance, instead of having it all done by client-side JavaScript. Pre-rendering can result in better performance and SEO."

The site is down.

If CCTV inside a business's premises are okay, you're going to have a hard time arguing that any other surveillance is unlawful.

They're not storing or sharing anything personal about you that you haven't already granted them permission to store (if you have a work badge with your photo on, you already consented to them storing a likeness of your image for identification purposes).

As much as I empathise with you on your stance against RTO, there's nothing here to fight.

You're talking about Apple, right?

First smartphone, produced by IBM. First portable media player, produced by Archos. First tablet computer, produced by Cambridge Media.

Apple are infamous for taking someone else's idea, giving it a bit more polish, than marketing it as though they came up with it in the first place.

Something something ponzi scheme.

What else do people expect? Stablecoins are proving to be anything but stable. They're just the latest in the line of lies that is cryptocurrency.

> now they can first focus on the logic without having to struggle with the English naming conventions of a regular programming language as well

Instead making it the problem of non-Spanish speakers to have to struggle with the Spanish naming conventions. There are something like three times as many English (~1.5bil) speakers as Spanish speakers (~559mil) in the world. There's no good reason to make it easier for the smaller group and harder for the bigger one.

> Blockchains as a form of "decentralized trust" for example, may have limited utility in most situations, but there probably are cases where that approach makes sense.

We're just waiting for someone to actually find the problem that blockchain solves.

These are the professional versions? Most of them sound pretty passive aggressive. The ones that don't instead use unnecessarily complex phrasing. Professional language is as much about conciseness and clarity as it is about striking the right tone.

> I would hate to give my potential tippers a way out by letting them leave after scanning a QR code and then not using it because they are lazy, which they almost certainly are.

It's got nothing to do with laziness. Tips shouldn't be expected, and the difference between a QR code and a tip jar isn't going to change whether people think the service was deserving of a tip.

A better answer to cashless tips is just to allow customers to add it on to their total and collect it with the card payment. It's done that way in increasingly many restaurants in the UK and EU, especially with the decline of cash and a growing preference for contactless payments during the pandemic. No need for yet another service when the existing stuff handles it.