llmblockchain

I prefer to roll my own dice. When I see two names I am unfamiliar with, I pick the one that sounds better when I say it out loud.

I'd argue physical channels and access are even less secure. People are broken easily (you can't trust anyone) and surveillance is everywhere and more sophisticated than you imagine. My first job was at a US-based video surveillance company owned by Israelis and used by casinos, stadiums, and entire cities. I have an idea of what it's capable of :)

What we need is a truly secure and private method of communication and payment. We're close on both.

I do-- I own my own company and the office is my house :)

There's a difference between becoming incredibly good at frontend and knowing enough to get things done and be a productive member of a team (ie, not get fired like the OP).

Maybe you should learn some front end and avoid the problem altogether?

"I don't do X type of work" is pretty unrealistic and comes across as more stubborn than anything else. This is especially true in a small/scrappy company up to medium size companies where you're expected to wear multiple hats.

Maybe at Google you can get away with being the "person that does X-only" but that doesn't work in most companies.

Your job is to do _the thing_ if that thing includes front end work, then you do the front end work.

It depends on your threat model. If your threat includes three letter agencies and nation states then you're right-- don't use Proton. However, 99.9% of people don't have that threat model. In that case, Proton is better than most other providers out there (for email, vpn, etc).

It's not dead. It just gosub without return.

It would seem the best way to put an end to the ES fiasco is to simply release what you have (and post the update to Kickstarter)?

If the engine and tools are 90% complete, it's better to release 90% of something than nothing at all. The backers would no longer be able to call it a scam. It's probably the only way to put it all to rest.

As soon as I seen the headline I thought, "Falco?"

Nice to see, but people still want you to complete Elysian Shadows or give them their money back.

For the uninitiated:

https://www.reddit.com/r/HobbyDrama/comments/nvf55t/video_ga...

> It seems like you’re more of a ghost on GitHub than a developer. Keep it up, and you might just vanish into the digital ether altogether!

Mission accomplished!

Code review? There was no code review. We did get our own offices though!

"Senior" holds no weight with me. I've had plenty dumb founding conversations with "seniors".

My favorite was at the company that was self hosting their code. The senior team lead wanted me to help him find a memory leak that plagued the product for months. Customers were told to restart the application every few weeks (this was a C++ application).

I sat down with the senior and looked at the code. I spotted the error.

I was like, "You know when you do new[] you need to use delete[]?" as all of his deletions were without [].

The look on his face was the best.

I've been that person a few times.

1. The only developer on the team with Github and put forward the idea of the company not hosting their own source code with TFS.

2. The only developer using branches with git when the co-founder asked (demanded) everyone to only use master.

The list goes on!

The part where Hitler makes fun of them for using a vm to run a docker container to run a 10mb Go binary is spot on.

I scp my binary and let systemd run it :)

This blog post is akin to Phillip Morris telling us smoking isn't bad. Go on, try it.

I live near Intel HQ and I know many Intel employees. Everyone I know has been interviewing at other companies for the last 8-12 months. I haven't met a single person that had a positive thing to say about Intel and its future.

You need to start by copying. Find a page and try to reproduce it on your own. Keep doing it and you'll get to the point where you're comfortable doing your own designs.

I am currently maintaining three SaaS products I built with Go. It's a great tool for the job.

One was with Go with vanilla HTML/CSS/JS (with Turbolinks classic for snappy page loads/transitions). The other two products were built with Go and HTMX+AlpineJS+Tailwind CSS.

In retrospect, I'd like to remove Tailwind as it bloated the HTML a lot and rebuilds are slow (~300ms to ~500ms per-build). Alpine has its uses, but I don't think I used it enough to really need it.

pngcrush !

My favorite quote on perfectionism and one I often think about,

"You know, the whole thing about perfectionism — The perfectionism is very dangerous, because of course if your fidelity to perfectionism is too high, you never do anything. Because doing anything results in … It’s actually kind of tragic because it means you sacrifice how gorgeous and perfect it is in your head for what it really is." - David Foster Wallace

Anyone that has built and shipped something has likely struggled with it. You have a great idea. You build it and it's never as great as it was in your head. You need to ship it anyway, but doing so means getting over that perfectionism. Some can. Most can't.

Structured learning is great, but I think you're over estimating the power of books. Especially in a domain like reverse engineering. The moment a book is published it's out of date. What worked yesterday doesn't work tomorrow.

I never suggested people learn entirely on their own. I learned in a loosely structured way by reading thousands of forum posts, asking questions on forums, sitting in IRC channels talking to people, etc.

My first job was working at a video surveillance company... My specific job was reversing multiple proprietary video streams, transcoding them and stitching them into a single output stream and sending it to a browser. For example, taking nine 1080p video streams and stitching them into a single 3x3 video stream that totaled 1080p.

It was a chaotic mess of C++.

I did it for a year before joining a startup, and on and on.

I never thought of reversing as something you pick up a book for. Everything I learned was through application from a young age.

1. Learning how to use Cheat Engine to scan video game process memory and modify games.

2. Learned how to read/replay packets in an MMO to try an cheat.

3. Learned how to craft DLLs, hooks and inject them in processes.

4. Learned how create patches for executables to solve some crackme challenges.

5. Mess with real world software that requires a license key, to suddenly not require a license key (or accept any key).

6. Mess with binary formats to try an reverse how game saves worked to.. you guessed it, cheat.

7. Get a real job and make money with the skills and knowledge I acquired.

> You get weird bugs where A needs to be 1.71.0 but B needs A at 1.69.0 or 2+. Upgrading A to 2.0.1 will fix A and B but break CDEFG.

Sounds like "modern" web development.

How much value do companies get out of these "enterprise security" companies? I've always thought they were the modern equivalent to commercial virus scanners that come with Windows.

So let me get this right...

Google introduces a lot of "privacy protecting" ideas like removing third party cookies, moving extensions to manifest v3, etc. Then they backtrack on removing third party cookies and keep the manifest v3 roadmap.

Essentially, they are getting their cookies and eating it too.

Some of the content is alright, but that landing page is terribly designed.

This is one of my favorite programming books of all time. A lot of small light bulbs went off reading that book. It really opened my mind to C and its oddities.

I get it. Spam sucks, and I get it for marketing purposes. However, when all you want to do is send low volume transactional messages (payment failure, etc) it really sucks.

I don't mind paying a premium. I'd happily pay 3x Twilio's messaging fee if I had no BS to go through.

Several years ago Twilio wasn't so bad. It always had pretty antiquated API practices and felt clunky but it worked.

Nowadays, it's expensive and contains a ton of hoops to jump through for business and a2p verification. They charge you for many things (monthly for a number, for verification, every submission for a2p and re-submission if they reject it for whatever reason). I tried to contact support and they wanted me to upgrade to a support plan to even ask a question.

If I don't find a simpler solution I'll remove transactional SMS messages entirely from my application. I'd rather remove it than deal with Twilio.