Bruno Marques

[MrBeast @MrBeast]

I’m gonna give 10 random people that repost this and follow me $25,000 for fun (the $250,000 my X video made)

I’ll pick the winners in 72 hours

[Bruno Marques @bmponline]

@starbuxman Spring tips

[naviz @iam_viz]

Our professor is creating a blockchain with Golang in Microsoft word😭😭😭

[World of Statistics @stats_feed]

Antidepressant users per 1,000 people:

🇮🇳 India: 9
🇱🇻 Latvia: 21
🇷🇺 Russia: 23
🇰🇷 South Korea: 27
🇭🇺 Hungary: 29
🇱🇹 Lithuania: 36
🇨🇷 Costa Rica: 39
🇪🇪 Estonia: 40
🇮🇹 Italy: 44
🇳🇱 Netherlands: 47
🇸🇰 Slovakia: 48
🇹🇷 Turkey: 48
🇫🇷 France: 54
🇱🇺 Luxembourg: 57
🇮🇱 Israel: 57
🇧🇷 Brazil: 58
🇳🇴 Norway: 61
🇩🇪 Germany: 62
🇦🇹 Austria: 63
🇸🇮 Slovenia: 63
🇨🇿 Czechia: 65
🇬🇷 Greece: 70
🇫🇮 Finland: 81
🇧🇪 Belgium: 83
🇩🇰 Denmark: 84
🇨🇱 Chile: 90
🇪🇸 Spain: 92
🇸🇪 Sweden: 105
🇬🇧 UK: 108
🇺🇸 USA: 110
🇦🇺 Australia: 122
🇨🇦 Canada: 130
🇵🇹 Portugal: 139
🇮🇸 Iceland: 161

[Santiago @svpino]

Software estimates are one of the oldest lies we tell ourselves.

We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan.

I focused a big part of my undergrad on software estimation.

After graduating, I wrote plenty about the topic.

Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built.

I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom.

Here is the most important lesson I learned:

People can't estimate software. It doesn't matter who they are or how much experience they have.

Estimating software reliably is science fiction.

And the best part:

They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable.

And then they will. They always do.

There are two solutions for this. Let's start with my recommendations for those who don't have a choice:

1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work.

2. Never volunteer an estimate. Everything you say will be used against you.

3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours."

4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours.

But we all know your manager will force you to give an estimate. Here is what you should do:

1. Estimate how long you think it will take you to complete the task.

2. Multiply the number by 3. This will be the lower range of your estimate.

3. Double the lower range of the estimate. This will be the upper range.

Example: If you think something will take you 1 day of work, say "between 3 and 6 days."

Here is the funny part:

It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of.

The true solution for this problem:

Work for a company that doesn't care about estimates.

[Maciej Walkowiak 🍃 @maciejwalkowiak]

In Spring Framework 6.1, HttpExchange annotations, previously used only for declarative HTTP client interfaces now can be used also on controllers - meaning, you can use the same interface on the HTTP server and HTTP client side.

https://t.co/wlQ4CENzWp

[Maciej Walkowiak 🍃 @maciejwalkowiak]

🚀 New in Spring Framework 6.1: RestClient

Learn about the new HTTP client coming in Spring Framework 6.1 & @springboot 3.2. I love it and once released, it's going to be my go-to HTTP client in Spring.

https://t.co/J5OeO5ICbd

[Joshua Bloch @joshbloch]

Effective Java is banned in Ohio prisons! I am not making this up. Thanks to @Cidmonster and the @MarshallProj for their fine investigative reporting. https://t.co/mAqsd9ia7V

[Wisen Tanasa @ceilfors]

Once you've fixed a bug, stop and question yourself: How did this bug come about?

You may notice structural issues in the code, tidy it up to prevent future bugs.

You may notice missing tests, add the tests.

[Dave Anderson @scarletinked]

If you're a software engineer, your main job is maintaining legacy code.

Why? Because building a system doesn't take long, in comparison to how long code will last, assuming the code/business are successful.

Here are the 10 commandments of maintaining legacy code.

🧵

[Josh Long @starbuxman]

Did you know @jetbrains has a @spotify playlist of classic 80’s music for coding? https://t.co/L7dx1dnYfH

[Bruno Marques @bmponline]

@maciejwalkowiak No underscores please, prefer the subpackage approach.

[Bruno Marques @bmponline]

@maciejwalkowiak 2 days max. Always try to divide into small PRs.

[Bruno Marques @bmponline]

@nixcraft 🙋‍♂️

[Historic Vids @historyinmemes]

In 1951, Adelbert Ames created the mind-boggling ‘Ames Window’

[Bruno Marques @bmponline]

Impressive

[Bruno Marques @bmponline]

Manic miner ftw

[GitHub @github]

What was your favorite video game when you were younger?

[Bruno Marques @bmponline]

Vergonha alheia ...