… that just means your computer is useless when you start it up. And anyway I’m talking about things like your browser with previous tabs or your IDE.

Ok ok

boot hardly takes any time at all. it’s all the programs on the computer that take forever to start.

two apps? where do you work that you only have two apps open? just on my home pc right now I have 21 programs open, of course that includes things that autostartup, but those things take time to startup. stuff like dropbox can take several minutes until it stops thrashing your cpu. On my work computer I have even more. Just in basic programs to do my job that’s at minimum 8 programs. That doesn’t include auto startup apps, or other apps I use. That’s just basics required by my job. Several of them are IDEs which take several minutes to start, and then when they do start you have to open up the project, indexing happens. All told, the computer can start in 20 seconds, but getting to a working desktop state is about 10 minutes.

this meme is really true for windows, sometimes my pc wakes up the second I put it to sleep. seems to be some random app I have open allowing it to wake up again. infuriating. With intel macs, they wasted a lot of battery asleep, but my silicon mac can sleep for weeks without losing hardly any battery. linux I still can’t get sound to work properly.

I literally didn’t mention micro services at all. So once again it’s very clear you didn’t read what I wrote. And no, that’s not what micro services are. Smdh.

You’re right I haven’t heard of that model, but NASA has documented pretty well that it follows waterfall. https://appel.nasa.gov/2018/11/27/spotlight-on-lessons-learned-aligning-system-development-models-with-insight-approaches/

pretty sure they’re saying waterfall for building a rocket because that’s literally how NASA builds a rocket, including the software. It’s terrible for building anything other than a rocket though, because the stakes aren’t high for most other projects, at least not in the way that a critical mistake will be incredibly bad.

python is a bad first language because the tooling is terrible. “ah yes let’s teach beginners by making them deal with tooling problems for the first 90 hours of their lessons, then we can finally get to actually teaching the language”

Because I clearly said that you don’t cut up things into tiny pieces. It was both in the first paragraph in my post and the last one. I said you use tiny functions to glue together larger systems. So yeah you clearly didn’t read what I wrote.

nobody was using jif as a file type in the 90s, and no it wasn’t “only logical to use the hard G”. There are plenty of sources stating that no one pronounced it with a soft g up until it got popular as an image format on social media. It was universally understood to be a play on the peanut butter name. There are plenty of sources on this, I’m sorry but you’re either just making shit up or you were the only person to call it with a hard g in the 90s.

jif was copyrighted. gif was literally named after the peanut butter. it came with a jingle “choosy developers choose gif”. How many different forms of proof do you need.

it’s spelled img - ur, as in img or the shortening of image in every context. You can’t shorten image any other way.

You didn’t read what I wrote at all.

You can write your glue nano-service in c/c++ if you want, it’s just that: glue. It doesn’t matter as long as you don’t need to change the original services which also can be written in whatever you want. Ruby, Python, JS just work out of the box with aws lambda and you don’t really have to maintain them or any sort of build infra so it allows for very little maintenance or upkeep cost. You don’t really test these glue lambdas either.

This is hilarious

How do you pronounce it?

Yeah lots of people don’t realize that 1. English rules don’t matter a majority of the time, 2. English has a lot of loan words that people mispronounce, not just mispronounce from the perspective of the owning language but from an English rules perspective as well, and 3. Proper nouns don’t give a shit about anything. GIF is a proper noun, created and owned by a company. They get to call it whatever they want and the rules of the language don’t matter. I

SCUBA and NASA are always the ones I use against that argument. It would be Skuh-baa instead of scooba, and neh-sa instead of nah-suh.

And no matter what way it was spelled, it’s the only word we’re still arguing about that literally has a song to go with it to make sure everyone pronounced it correctly. It’s pretty clearly a soft g, because it was a marketing trick, not a dictionary word. It doesn’t have to follow any rules of English, just like all those companies just removing random letters and changing ck for x, etc. Flickr, tumblr, Grindr, scribd, Lyft, Kwik, Cheez, etc etc etc. Twitter was originally even twttr.

we’ve been using nano-services for the past 6 months or so. Two different reasons. A codebase we absorbed when a different team was dissolved had a bunch of them, all part of AWS AppSync functions. I hate it. It’s incredibly hard to parse and understand what is going on because every single thing is a single function and they all call each other in different ways. Very confusing.

But the second way we implemented ourselves and it’s going very well. We started using AWS Step Functions and it allows building very decoupled systems by piecing together much larger pieces. It’s honestly a joy to use and incredibly easy to debug. Hardest part is testing, but once it’s working it seems very stable. But sometimes you need to do something to transform data to piece together these larger systems. That’s where ‘nano-services’ come in. Essentially they’re just small ruby, python, js lambdas that are stuck into the middle of a step function flow in order to do more complex data transformation to pass it to the next node in the flow. When I say small I mean one of the functions we have is just this

def handler(event:, context:)
  if event['errorType']
    clazz = Object.const_set event['errorType'], Class.new(StandardError)
    raise clazz.new.exception, event['errorMessage']
  end
  event
end

to map a service that doesn’t fail with a 4xx http code to one that does fail with a 4xx http code.

You could argue this is a complete waste of resources, but it allows us to keep using that other service without any modifications. All the other services that depend on that service that maps its own error types can keep working the way they want. And if we ever do update that service and all its dependencies, now ‘fixing’ the workflow is literally as simple as just deleting the node and the ‘nano-service’ to go along with it.

I should note that the article is about the first thing I discussed, the terrible codebase. Please don’t use nano-services like that, it’s literally one of the worst codebases I’ve ever touched and no joke, it’s less than 2 years old.