Oh, I'm damn sure it's "for me"...

Bad for me!

I need advice.

So let's say, hypothetically, I found a site with a user data leak.

Would it be illegal if I only told them where the leak was for a bounty?

I am NOT going to distribute the user data. I just don't want to work for free, you know?

Again: NOT DISTRIBUTING USERDATA. No blackmail. Just information that their QA should have caught.

Feeling accomplished today because I finally implemented a matrix library.

I'm curious, what was the most ridiculously otherworldly, the least understandable, eye-opening code you have every seen?

BUT, I mean that in a good way. And what did you learn from it?

For me personally, I would probably say some of the c++ stdlib implementations. Just totally not English in some places. I mean seriously, sometimes asm is more readable than c++

Bit of a bitch to get set up, but I made a SASS auto-recompiler with file watching. Windows was being a total ASS and sends the change event up to 4 times in my testing for a single file save action. It also renders the file unwritable for that time, throwing errors.

I literally had to add debouncing to make this work, but it's kinda nice now.

In the news today, a city in Lebanon fell victim to some sort of explosion, which was captured by hundreds of civilians via cell phone recording.

In other news today, millions of people learned Lebanon is a real place.

This week in Programming Language appreciation: the multiplication operator in Python. You can use it on strings and arrays for incredible ease of use. For a horizontal line in a terminal?

print("-" * 30)

Very helpful, and I have used it a lot. And I miss it in other languages.

Something I discovered at work today:

A sub procedure that takes three arguments:

A table name
Column list
Where clause

It concatenates all of those values together and executed the dynamically generated query.

Why??????????

I hate when I click a link and it opens a download.

I got a fuckin degree lmao

800 line file.

Could be 300 lines but despite having version control, the devs didn't have the balls to remove any of the code. Just commented it out or appended _old to the function names.

"It's easier to undo than version control"

Sure, but how much time are you spending wading through the waist-high swamp of shitty, useless code?

Angular and MVC really slows shit down, doesn't it?

I added 1 (one) page which displayed two data grids,straight out of a database procedure. Here's the head count:

- 13(!!!!!) New files
- 5 old ones modified
- Build process on both server and client side (Visual Studio build and ng build)

java --version
FATAL: Unknown parameter

java -v
FATAL: Unknown parameter

*googles get java version*

java -version
openjdk version "1.8.0_252"

FUCK YOU

What I already knew: hard disks made of crystal exist which can store 360TB of data for billions of years, they're just really slow.

What I didn't know: Elon musk owns the first and second disks and one of them was launched into space alongside is Tesla roadster! (He personally has the second)

Please install more tex

This morning: Two projects, neither working, both hopelessly broken (think: won't even build)

By lunch: both fixed.

A happy meal

Something I probably shouldn't talk about:

One of the projects at work has a specific path you can visit. The """security""" is that nobody should know the path. But I can guaran-fucking-tee you it's not difficult to guess.

On this page, ***without a login***, you can view some user information. Well, you can view all of it, but only certain fields.

And if you perform a specific action on this page, you can get their password, plaintext.

This project is not mine. But learning all of this made me super uneasy. I had to share it.

I've always liked Windows more than MacOS, but known deep in my heart that MacOS is more polished. More shiny, attractive, makes more sense, is easier to use, etc. Windows was never that far behind (however, they were probably furthest behind in Vista and 8), but they were always behind.

Looking at the new MacOS, I genuinely think that Microsoft offers a better experience now. While Android and iOS are still firmly battling, Windows just beats the living shit out of MacOS.

Windows is an OS built for either touch or mouse. If you use touch controls, the OS automatically adapts to it (larger context menus if you press and hold, smaller ones if you right click). You can enter tablet mode. The start menu has a good interface for both touch and mouse.

MacOS is an operating system designed for touch input on a device which famously has none.

It has fallen victim to a very common design error: too much fucking spacing. Every little thing, even items in a list, has a ton of pixels between them, and they all have rounded corners. Again, this is common for touch displays where you don't wanna fat finger stuff. But they don't offer a touch screen Mac and have expressed no interest in ever doing so.

Now they're going ARM on custom silicon. This is a good move in the long run, but it's going to be a rough couple of years. Apple admits two. You can probably reliably double that.

Is Apple killing the Mac on purpose or by accident?

I hated the detailed, shadow-y icons that Windows 10 implemented a while back.

Now CopyApple is using them too...

Am I just crazy? Am I wrong about this new design trend being total ass?

Also: Apple literally copying everything now huh.

It's official. I'm making multiplayer Minesweeper.

There's a Trello board, Discord server, and GitHub repo.

Initial gamemodes will be singleplayer, public (like agar.io) and vs (2+ players, support for teams is planned).

My big idea besides that is to have interesting powerups you can buy or find, adding a component of luck and some exciting new rules to the game.

And I may even put ads on it and try to feed myself.

The minimap for my documentation looks like a sick knife

The amount of times I have read "I can't summit the application" in user issue tickets has prompted me to make this

On the screen: four text boxes cycling through rainbow color backgrounds and spinning wildly in circles.

Manager walks in.

Here's the context.

We were pair programming and working on a simple form. We were just finishing up the style, and I suggested we use a CSS3 animation to make the invalid fields pulsate a light red once.

I'm the young guy in the office, so I am most familiar with the "new" front end stuff like flex and CSS3.

My colleague was unfamiliar with CSS3 animations, so I implemented the red flash quickly and showed him.

He was curious what else you could do with CSS3 animations, so I changed my "to/ from" to a "0%/ 25%/ 75%/ 100%" style animation to show how keyframes worked. Then I made the animation iterations infinite so it went on forever. Of course, I didn't have any normal colors on hand so I just went with my debug colors: red, green, blue, yellow, etc.

We submitted the form with invalid inputs and sure enough, they flashed rainbow colors. It looked pretty funny so I thought "haha, lets quickly add rotation while we're at it"

That's the point where the education turned to a little fun but it wasn't going to take more than a second.

So we did it and it looked pretty funny and it actually made me laugh. Then we started discussing next steps on the form (back-end). Discussion lasted maybe five minutes before our manager visited to update us.

As we were discussing, the invalid controls were still spinning and rainbow colored in the background. Whoops.

The words we managed to say were just "It's invalid" and then we broke out laughing.

One week, and it turned out to be worse than that.

I was put on a project for a COVID-19 program in America (The CARES Act). The financial team came to us on Monday morning and said they need to give away a couple thousand dollars.

No big deal. All they wanted was a single form that people could submit with some critical info. Didn't need a login/ registration flow or anything. You could have basically used Google Forms for this project.

The project landed in my lap just before lunch on Monday morning. I was a junior in a team with a senior and another junior on standby. It was going to go live the next Monday.

The scope of the project made it seem like the one week deadline wasn't too awful. We just had to send some high priority emails to get some prod servers and app keys and we were fine.

Now is the time where I pause the rant to express to you just how fine we were decidedly **not**: we were not fine.

Tuesday rolls around and what a bad Tuesday it was. It was the first of many requirement changes. There was going to need to be a review process. Instead of the team just reading submissions from the site, they needed accept and reject buttons. They needed a way to deny people for specific reasons. Meaning the employee dashboard just got a little more complicated.

Wednesday came around and yeah, we need a registration and login flow. Yikes.

Thursday came and the couple-thousand dollars turned into a tens of millions. The amount of users we expected just blew up.

Friday, and they needed a way for users to edit their submissions and re-submit if they were rejected. And we needed to send out emails for the status of their applications.

Every day, a new meeting. Every meeting, new requirements that were devastating given our timeframe.

We put in overtime. Came in on the weekend. And by Monday, we had a form that users could submit and a registration/ login flow. No reviewer dashboard. We figured we could take in user input on time and then finish the dashboard later.

Well, financial team has some qualms. They wanted a more complicated review process. They wanted roles; managers assign to assistants. Assistants review assigned items.

The deadline that we worked so hard on whizzed by without so much as a thought, much less the funeral it deserved.

Then, they wanted multiple people to review an application before it was final. Then, they needed different landing pages for a few more departments to be able to review different steps of the applications.

Ended up going live on Friday, close to a month after that faithful Monday which disrupted everything else I was working on, effective immediately.

I don't know why, but we always go live on a Friday for some reason. It must be some sort of conspiracy to force overtime out of our managers. I'm baffled.

But I worked support after the launch.

And there's a funny story about support too: we were asked to create a "submit an issue" form. Me and the other junior worked on it on a wednesday three weeks into the project. Finished it. And the next day it was scrapped and moved to another service we already had running. Poor management like that plagued the project and worked in tandem with the dynamic and ridiculous requirements to make this project hell.

Back to support.

Phone calls give me bad anxiety. But Friday, just before lunch, I was put on the support team. Sure, we have a department that makes calls and deal with users. But they can't be trained on this program: it didn't exist just a month ago, and three days ago it worked differently (the slippery requirements never stopped).

So all of Friday and then all of Saturday and all of Monday (...) I had extended panic attacks calling hundreds of people. And the team that was calling people was only two people. We had over 400 tickets in the first two days.

And fuck me, stupid me, for doing a good job. Because I was put on the call team for **another** COVID project afterwards. I knew nothing about this project. I have hated my job recently. But I'm a junior. What am I gonna say, no?

THIS JUST IN: American colleges are dedicated to renaming "master's" degrees to "main's" degrees, following GitHub's example

There's a classic joke about how programmers check both ways on a one way street because users are so stupid.

Well I took a walk on my break and literally 30 seconds from the door to my building someone was going the wrong way on a one way street.

Does art imitate life, or does life imitate art?

typedef struct _Name {

} Name;

Or

typedef struct {

} Name;

...and why?

What's the WORST commonly used language to use for server side web development? By this, I mean which is LEAST fit for the job, not which one do you hate the most.

I vote Java. It's lack of creature comforts like operator overloading and it's verbose and strict nature are in direct contrast with the free-form nature of the web. At least C# lets you do some crazy stuff.

Set up a chron job to backup my movies server.

copying 100-200 GB from a slow HDD to a slower HDD on a CPU that isn't exactly NASA material if you catch my drift.

I expected it to take a while but holy fuck, 45 minutes.

At least the archive finished at just 80GB.

Maybe a stupid question but I can't seem to google the right words.

In Linux, how do I reference the same device (disk) through reboots? Like, there's no guarantee that /dev/sda1 will be the same device twice, right?

Like, if I have three or four disks and I want one for "backups", how do I choose that disk *every time*?