systematical

The amazing part is they allowed themselves to get hit again. You'd think these organizations would tighten security after the first one...

Fish user here. I've accepted having to drop down to bash here and there. No big deal for me.

HAPPILY just left a company. I'm done working at companies that don't offer unlimited PTO. Second to that, I'm not letting a job chain me to an overpriced city.

The only way for documentation to be part of CI (IMO) is for missing documentation to cause failed builds. There are a few ways I could think of to enforce this but is there anything off the shelf that does this?

Since we're all talking about our drinking rates. I personally just drink with friends and occasionally go to a bar myself, so I am not drinking a lone. I can go a week without drinking, it means I didn't leave my house (and I was likely working on OSS for that week). I could drink three times in a week, it means I hung out with friends three times. Most of that is bike rides where we consume alcohol.

As an introvert, thankfully I have alcohol and bars. I don't give much thoughr to how much alcohol I consume. I don't care if Doctors say I'm an alcoholic because I consumed more 5 drinks in a sitting or whatever. I mostly listen to my body. If I am feeling shitty, I know I've been drinking too much, so I take a break. Today I feel shitty, it was memorial day weekend and I went to a baseball game with friends followed by bike rides and drinking with friends. Time to take a break for a few days.

And today you get all that plus a lot of features you'd expect in other languages. Starting with PHP 7 the language has gotten faster and better and it continues into PHP 8. Just checkout of the RFC's https://wiki.php.net/rfc

Agreed, it's nice and fast. Sublime is my go to for notes, storing quick tidbits, quick macros (this has saved me lots of time), data editing, little bits of quick code, and SQL scratch pad. There is probably a ton more I could be using it for.

I learned earlier today that the little google street view man nopes the fuck out of Kabal.

https://github.com/cnizzardini/cakephp-swagger-bake which builds out openapi from your cakephp applications meta data. One of many projects I took up to occupy myself during covid lockdowns.

I wasn't satisfied with writing the YAML or annotations manually.

Salt Lake County now makes you pay one dollar for a mugshot. That ended websites reposting the pictures.

Linear looks nice. Anyone using it?

For those who have used tools like Hotwire, what has your experience been like? How does it compare to something like Vue or React?

Software engineers don't do it because lead devs don't enforce it and lead by example. It's not hard. Failure comes from the top down.

30 minutes? I don't have exact numbers, but I know ours is under 10 minutes and IMO that is not optimized at all. Maybe 30 minutes is okay for a very large project, but for most applications that seems quite high to me.

Our pipeline runs in Jenkins and builds a docker image that runs composer installs, application copy, and that sort of thing. We also run phpunit, phpstan, phpmd, and phpcs in our pipeline. Finally the image gets pushed up to ECR.

I think that's all pretty standard stuff. TBH I'd like us to move to github actions and optimize for more staged builds in our docker images, but we have higher priorities at the moment.

Federal contractors as well.

Luckily not all federal contractors think like this. Some would report this behavior and some of us would be quite happy to report it. There are those that still believe in doing the right thing, value tax payer dollars, and want to deliver for the American people. If only more of us wanted to completely rip out the rot.

I really hate titles like this.

Think of all the UBI that money could've provided.

I had one good outcome from the pandemic (besides no dying). I had an abundance of time and years of programming experience plus some good ideas. I went all in all writing some OSS and to my surprise people actually began using these libraries. Some even contributed PRs! I in turn began feeling more confident to contribute PRs to other projects. Some were even accepted!

So the take away I got from this article is. Why spend time writing something that "decorates" or improves some OSS in userland and will be lost for eternity in a private code base when I could open source it. This depends on the type of company you work for of course, but to the authors point, why work at a company that doesn't embrace contributing back to the OSS these free loading capitalists have built their business on.

As my reply far up this chain says, the services have a ton in common. So much so that the idea was "just copy and paste" code between. Still sound great? I forced his hand on a shared library that houses lots of the code all services need, but not everything can (or should) go in there.

Multiple PRs just to complete one task sometimes and we're talking a small 4-6 hour task. If the services were truly independent this wouldn't be needed and the approach wouldn't be a poor developer experience and infrastructure headache. But a change in one often requires a change in another. We don't have a monorepo, because he was too much of a doofus to figure it out and gave up instead of asking for help.

80% of the problems are because the guy doesn't know what he's doing, doesn't know architecture and just said we're doing this. Which means I have to go in and fix his poorly built Dockerfiles that are an expose on what not to do. We're now adding API Gateway. Was this explained as to why we need it? No. Did I ask yes? But I simply get "I've already explained it" Cool. I explained to you why running an update on packages in your build instead of installing from a lock file is some of the dumbest shit I've ever seen yet I just had to go in and clean up your dockerfile again. You want untested packages going into stage / prod? My lead is your guy. I'm sure in a few weeks he'll come to me with "But API Gateway doesn't work and I don't have time can you fix it".

Fuck this dude. I just want to write clean code and not fuck with his mistakes. Did I mention we run completely different Dockerfiles between environments (local vs stage/prod). Like, not even the same O.S (ubuntu vs alpine), web server (apache vs nginx) etc... Getting the picture of whats its like to deal with his mistakes day in and day out and slowly fix them.

A good reason no doubt and if that comes to bear sure. But at least code in a monorepo and split to microservices in your pipeline. Cake and eat.

Read my reply further up, they have a lot in common. We had to build a shared library that goes in as a dependency and even with that we have to still copy/paste code between services. Because a data structure change in one must often be reflected in another HELLO multiple PRs for one task.

Because there is a bunch of shared code behavior and data between the services and his idea was "just copy and paste". We devised a library that gets shared as a dependency, but managing that dependency is PITA and not everything can go into the shared library still. Which means we still copy/paste some code, which is okay with this bozo somehow. I can stomach splitting things into microservices that don't actually talk to each other, though I don't see the need day one, but why not run it as a monorepo and split it out in the CD pipeline so I don't have to open four PRs for one fucking task?

Because the goof couldn't figure it out and just gave up and said here you go. This is before I knew the guy was completely useless. I had to do a whole presentation and get the favor of every single developer just for him to succumb to FACTS about moving to a monorepo that then splits the code out to his beloved CV fuel on build. Trust me, there is a lot more wrong here if you are getting any of this. As for team size we are small. Six warm bodies, three actually moving.

Personally I say go monolith (for most small/medium projects) but design it with an eye towards splitting it into services down the line, that is unless something is smacking you in the face to go all in on micro. For monolithic that means a logical separation today, that can easily be split out in a single sprint tomorrow. That means less pain and more features today and a path towards some dudes wet dream in the future.

Yeah I'm salty.

The author is not lying. I've been learning docker and it is certainly nice to pull and docker-compose up for local dev, but there is a lot to learn when you factor in orchestrators. And when I mean learn, I mean actually learning the nuts and bolts of a Dockerfile and not copy/pasting shit from the internet. While it's all helpful, its certainly not needed for the project we have at work, nor the "microservices" that our lead thinks we need even though they aren't even microservices. All we've done is split our application into seperate mini applications that don't talk to eachother at all, essentially 4 web services. Great! Sigh.

So why am I learning all this instead of just programming? Programming is what I really want to do all day, just writing code and thinking through software architecture. Because the industry tells me if I don't learn this stuff I will be decommissioned. Fun stuff.

Cause you could never have exploits in functional...ever.

I've been saying this for years. The government should actively be hacking corporations, state, and local governments. Then disclosing the vulnerability privately to these organizations. This levels up our offensive capabilities while securing us at the same time.

I'm down for a Dyson Swarm.

I'm interested in adding this on mixerapi.com.

I was waiting for this comment.

Go heavy nuclear and invest in fusion. The later will lead to clean abundant energy and eventually a reduction in resource scarcity. What is the economics of air? That's the economics we want.