Been looking into 2D maps for a game. I am learning how to use tools that do autotiling. I want to have generated worlds for terrain. It is interesting how the scope of what you are learning starts expanding rapidly and can overwhelm you. I started wanting to learn autotiling. This went from that to autogen, to modifying terrain, to how to store generated terrain, to how to store difference between autogen and player modified, to how to separate things into chunks, to how to store a whole world worth of data! Like dude, chill. Just learn how to use autotiling first. Then learn how autogen, then learn how to efficiently chunk things,. Also the 2d data won't be big so just store the data you genned so if modified. The worlds don't have to be ultra huge. Really stop freaking out what it could be and see what it is. JUST FUCKING ITERATE!

It is wild to watch yourself get featuritus without learning how to crawl fist. Just divide and conquer.

So I have been wondering about "ish" on the end of ethnicitys. Does it mean sorta?

Irish : ire-ish sorta angry
Danish : dane-ish?
Finnish : fin-ish good swimmers?
Spanish : span-ish good with measuring things? Good with wrenches?
Jewish : non practicing Jew?
English : what the hell is an engl?

Genie: You have three wishes
Me: Make it 0
Genie: Ok, you now have 255

HR: On your resume it says you went to Yale.
Me: Yes, for my sister’s graduation.

The problem with getting more experienced is it is really hard to decide what to learn next.

It is like looking at netflix screen for an hour to pick up a movie and going to bed without watching it because you got tired.

We have this guy who is responsible for software testing, user support and stuff. Not a programmer but with good technical base knowledge. He was interested in writing automated tests, and I told him he might take some time to learn and help us there. In the last months I had to answer and explain a gazillion questions about our codebase and coding in general and it took me lot of time. But last week he showed me his first test suite which was actually good code and showed a lot of understanding of all aspects of this. This was more satisfying than anything on work ever.

…okay :D the irony

Ask questions during interview.
Ask about trainings - it's usually a good sign when company offers training budget. Ask about specifics - sometimes it's a shared pluralsight account, and nothing else, which means that that had an idea and half assed it into existence.
Ask tech recruiter about overtime, a good sign is when they have no idea or say that it must be budgeted and scheduled - it means that it does not happen often.
Ask if it is possible to select and change projects, and how often it happens - if often, it may be bad low level management, or people learning new things and jumping between projects.
Also make sure to ask about rules for promotions and pay rises. Good company wił have a clear set of rules in place.
All of the above apply to mid to large companies.
For small company, i'm sure it will be different.

This office has gone [object Object] days without type coercion errors

There is a special place in hell for people that do custom smooth scrolling on their websites.

Worked for a friend of mine in the early 2000s. Had to implement a booking system into PHP for some private customer. This was PHP 4.something, the CMS was some alpha release of an open source project that my friend was sure was the future (it wasn't), and the specs were one A4 page of pencil scribbles that he took while talking to the customer.
Deadline was insane, nothing worked. I worked from getting up to laying down to get shit done, not being able to sleep, feeling stressed all the time. One week before roll-out I actually managed to get it running and we showed it to the customer. He was like "nope, that's not what I meant" and demanded lots of changes but accepted only one or two weeks of roll-out delay.
I did finish the job, made some good money, but then quit as soon as it was done.
This experience broke me so much that I worked in a workshop for 2 years to get away from programming as far as I possibly could.

Relationship Status: just tried to reach for my dog's paw and he pulled it away so I pretended I was reaching for the remote.

TIL about optional chaining in JS.

I can sleep better tonight.

When your partner rolls over in their sleep and manages to smack you in the face… not the best way to wake up.

I just found out one horse has about 15 horsepower and I’m so mad I can’t think straight.

A take on Neumorphism Design, the code is on codepen to try out and the credit to the author of the design. https://codepen.io/flavio_amaral/...

karens on stack overflow...

surprise API

Clicking on wk288 tag in a rant brings you to wk287

All those developers complaining about how at their new job there is no source control process, no ci, no CD, no code reviews, no coding standards, no effective project management, next time maybe try asking some questions during the interview stage 🤔

Remember you are interviewing the company as much as they are interviewing you.

* online meeting *

Why are ya'll muted? We can't have a conversation if you're all muted. Just unmute yourselves.

* someone had a lot of background noise *

Huh? What's happening? What's that noise? I think someone is in a very noisy place. You know what? Just mute yourselves until you want to talk.

THATS WHAT WE WERE DOING YOU PRICK

Psssttt....

https://youtube.com/watch/...

This is a gripe about modern UX interfaces. UX interfaces need to have better ways to get information displayed in text as text. It is exceedingly annoying to be presented with an error message in a dialog with a cryptic error code. The user is forced to transcribe the error message to try and figure out what is causing the error. Just make the text copy-able with normal cut and paste interfaces. I think this should be a standard in interfaces that present text to make it easy to copy the message or text from interfaces. This makes information sharing easier and less cumbersome to the user. This is definitely a mindset change for UX. This is mostly a gripe about desktop. Phone systems are just shit to begin with.

I shall forever stay at 13000:

*be me
* Design a website
* Boss comes in*
* Mmm smth off *
* Me discretely changes nothing, ctrl+S it
* Page reloads
* Boss : looks perfect

Everyone be like "I started programming at the age of 2 and my first ever spoken words were “for...each”".

We get it, child prodigy.

Don't mind me I'm just salty that I only discovered programming after taking the wrong course at uni which coincidentally had an extraneous Fortran module.

You know the world of software is expansive when you're learning new things from candidates in interviews...

Last year I changed jobs from a large multi-national to a small local agency (which happens to be run by friends of mine).

One of the reasons for doing this was that my work involved more office politics than *actual* software development, and had just plain stopped being fun.

Now, I am having fun again! An example?

For one of our clients we have to connect to (a lot) of third-party APIs. Often even SOAP APIs!

Now I hear you protest "But that is no fun at all! SOAP APIS SUCK!" Which is true, more often than not. 😔

BUT! My friend started an internal API-SNAFU Trello board. Every time you get bitten in the ass by some ill conceived fuck-up of an API, you get to add your complaint to the board.

Beside giving as something to reciprocally rant about, the board also serves a serious function: depending on the amount of fuck-ups an API has been known to make, the price for working with that API will go up.

Who said it doesn't pay to complain? 😀

Funny memo

Sam:- What are you doing??
Richard:- recording a baby's voice!
Sam:- why??
Richard:- when he grows up, I shall ask him what he meant by this
Sam:-😶😶😶