This is a fun conversation I had:

Test Engineer: 😑 The test bench burst into flames.
Me: 😪😲 Do what now?
TE: 😐 The test bench burst into flames. It made a pretty impressive fire ball.
Me: 😮 . . . How are you so calm about this?
TE: 😐 Well it's not on fire now.
Me: 😶 Good point.
TE:😧 made me mad as hell though.
Me: 😕 why's that?
TE: 😬 Cuz I only had one damn step left in that test procedure and it was to turn the damn test bench off.
Me: 🤔 Correct me if I'm wrong but the test bench is off is it not?
TE: 😐 Well yeah.
Me: 🤔 and you caused it to be turned off by your actions no?
TE: 😕 . . . yeah . . .
Me:🤔 sounds like you turned it off to me.
TE: 😒
Me: 🙂
TE: 😐
Me: ☺
TE: 😑
Me: 😎
TE: 😐 but it won't turn on again.
Me: 🤔 do you have a requirement to be able to turn it on again after you turn it off?
TE: 😑 It's implied.
Me: 😐 not what I asked
TE: 😧 No not explicitly.
Me: 😎 sounds like you completed the test procedure.
TE: 😑
Me: 😎
TE: 😑
Me: 😎
TE: 😧 that's not how it works.
Me: 😎 doesn't it?
TE: 😑 No.
Me:😎
TE: *walks away* 😧😧😧
Me: *turns back to computer* well I was just trying to help YOU out 😒

I am the best at interpersonal communication.

I see, my IDE has mastered semantics. Next step is to master context as well.

Why are interviewers so resistant to letting people use Google while doing coding questions? It’s not like I can remember all the semantics of every language anyway, and so much of coding is learning to use Google correctly.

A new low level language. Modern and clean, like swift or python. Simple syntax and semantics. Low level (non garbage collected, non vm, pointers). I want a new take on C.

Naming my psd file for the n-th time: superimportantrevisedfinal-final-draft.psd. I think it's time to move design stuff to a repo ffs.

Porting over code to python3 from python2 be like:
(Cakechat, in this case)

Day 0 of n of python 3 compatibility work:
This should be _easy_, just use six and do magic!

Day 1 of n:
Oh, true division is default instead of integer division, so I need to replace `/` with `//` in a few places.

Day 2 of n:
Oh, map in python2 behaves differently than map in python3, one returns a list, other an iterator. Time to replace it with `list(map())` then.

Day 3 of n:
Argh, lambdas don't evaluate automatically, time to fix that too.

Day 4 of n:
Why did I bother trying to port this code in the first place? It's been so long and I DON'T EVEN KNOW WHAT IS BROKEN BECAUSE THE STUFF RUNS WHEN I BREAKPOINT AND STEP THROUGH BUT NOT WHEN I RUN IT DIRECTLY?!

Day ??? of n:
[predicted]
*gives up*
I've had enough.

Vendor we('re forced to) work with, as we share a client. This is in their stylesheet. Fuck SEO best practices, amirite?! 😒

Well, not necessary my favourite but the first one I learned.

I think the weird syntax and semantics combined with the ridiculous average length of variable names is a major flaw in this one.

I think I’ve applied to 5 jobs that show up as “remote” now only to get halfway through a screening call and find out “oh, we’re looking for people in Albuquerque”.

Are my expectations out of whack? If you’re looking for someone in your city, you’re not looking for someone remote. You’re looking for a local worker who just has an office that’s not on your balance sheet.

Is it semantics?

Am *I* the bastard?

Tried to reply to @Fast-Nop who had replied to someone wondering if C would be a good first language.

IMHO C should have been put to sleep ages ago. A few years ago I downloaded the latest, greatest C Standard. For a language billed as small and simple (by many) it was over 800 pages long. Still there's a lot that's unspecified like order of evaluation of function arguments. Int etc is implementation dependent. And error handling, let's not go there. The macro assembler throws away all the semantics leaving behind a cryptic value. It's a complex language due to the innumerable interactions possible.

It's been called assembly language for the PDP-11 minicomputer. Recently learned that even the VAX-1 was built from SSI chips like the 4-bit 74181 ALU. The VAX.

Anyway I had several excellent books on programming style written by Henry Ledgard. He despaired of making C look readable. I commend his books which are so old that the code is UPPERCASE A lot of he wrote had to do with program design, naming things, writing good comments and that the visual shape of a program assists mental clarity.

Hey this is the first time i post here.

I just started working part-time for this company last week. What i have to do is to change some windows from Win32 to WPF. As i was reading the legacy code i just had to sigh man. They have like 100 projects in a single solution, from C++ to C#, everything acctached to each other, with almost NO comments or docs. Wtf man? I don't know how it actually works in the industry (this is my first dev job) but when you write fucking 20 classes with each one contains bunch of attributes, methods, properties, you can't just leave all the code's semantics in their names. And by the way the app is so fucking ugly i bet they have appointed part-time developers as UX engineers... Even i have little knowledge about UX/UI, i just can't bear with this kind of ugly and confusing and unintuitive production with a cost of a good photo editting software.

Ok there may be much more to rant in the future but let me try through this and tell you more. Have a good day. :)

For those who whine about authors putting "TL;DR" after the text that was supposed not to be necessarily read...

"TL;DR" means "Too long; didn't read". Hence, we have all the audacity to insert it *after* the long text. When you don't have time to read, you usually scroll to bottom and find a summary if any.

At least, scrolling can be done even by monke and author can concentrate on writing the streams of text to their heart's content instead of fishy semantics.

The difference between procedures and functions never troubled me. Until it did and now I'm just thinking it for the past hour! Here it is: Procedures perform some logic while functions (like in math) return a value. Daaaamn!

So I am interning at this company, and I am Coding in Go.
Now I don't have much exp with go so I'm learning it, and all of my team is cool cause they also had to learn Go. Anyways I am just petty intern-dev so everyone and everything is cool.

Migrating from python to go is quite hard.

Unlearn, You must.

What I have imagined Go, to be is:
While python has this top down approach to inheritance and polymorphism, Go has bottom up approach.
In Python child classes are derived from parent class but In Go child classes create a parent class. (this might be totally wrong, but that's how I've imagined golang)

Go is static wrt dynamic python.

I have coded in C for 1.5 years then I switched to python, so I feel that am familiar with static typing. The path that lies ahead of me shouldn't be too hard.

I would like to take a step further and say that Golang is C, but with modern syntax/semantics. It derives many of its features from newer langs like js, Python, etc while being a compiled language which translated directly to machine code.

That's all 😊

My team members are really great and supportive, I am about 10 years younger than them but we still connect and sync.

Everything is Great, Life is Good ❤️

This is gonna get someone illogically upset, but idc about that.

I know it's ignorance of semantics but I'm tired of propagated ignorance changing the meaning of things.

Non-binary is NOT a legitimate term for whatever 'gender' you are!

I get what *whoever-started-it* was going for, but it's NOT valid. If you want to say that youre not male or female, fine... just don't abuse binary systems to do it. Just say youre non-bool/anti-boolean or identify with one of the, apparently 50, shades of gray.

I keep getting into logical loops to nowhere about this nonsense. No one is even defining what's supposed to be the 1 vs the 0. Which then makes me think '1 must be male... genitalia=1 in many ways...' which then sources back to the historic validity of males vs undervalued/less than human interpretations of females...

Then <brake>.
Ofc these people aren't going into the historical significance... they don't even realise how binary works! Ofc they'd have no clue that all 0s= no data... and 0s only have significance when viewed in placement to the 1s.

Let's all start using proper terminologies, like non-boolean. Maybe i can start a trend by paying people pennies to learn/teach wtf a boolean value is, and that binary can represent anything. With proper encoding the array is limitless... so being binary is actually a giant spectrum... therefore makes no sense to be "non-binary".

Ok... im done. It had to be said.

Who wants to start identifying as non, or educating wtf is, boolean with me???

When you inspect a relatively new eCommerce site and find that it's using <i> for icon buttons. 😡

Perhaps one of the most important things I will ever learn in life is how powerful regularity is. Read up on a topic once? Understand nothing? Read more random shit on it. Keep reading. And then stare in awe as things fall into place.

I'm writing this out not because people don't know this. Almost everyone knows this. But it's nice to be reminded of it. It's nice to be reminded that learning new things and honing bew skills is never easy. It's nice to be reminded that there's great knowledge and skills waiting to be learned.

This is not meant as motivation so much as it is meant as a reminder. Our colleagues may be garbage. Our clients may be garbage. Our bosses, the interns, the new dev, and almost certainly ourselves, are almost always garbage.

But if you've learned 1-2 new things today, the day wasn't garbage.

I'm just learning move semantics...

Intel 8085 micro-processor, anyone?

In my graduation, one of the semesters had Intel 8085 programming in the curriculum. It's because of that dev-kit I understood what assembly-level language means.

A simple scenario of adding two numbers would result in half a page long sequence of commands that literally didn't excuse any mistakes.

It made me understand the semantics or basically what we get taught as "middle level" languages.
We had to memorize the exact pins of the thing and had to draw it from memory. And we had to learn the instruction set it had.

Later we had to learn Intel 8086 but its instruction set was way too complicated and I gave up on it.

I know it sounds geeky but I randomly remembered it today.

I have this irrational cringe every time that people say infinite when they actually mean unlimited. I hear and read it everywhere, multiple times per day. In English and in German.

"You can do this infinitely often"

"AI bots have infinite APM"

"The number of items you can store is infinite"

Aaaaargh! Stop it! It hurts! 😫

I hate when they give new people that don't know the software the job to update requirements. We used to have 2 use cases that touched a functionality. Now we have three. The requirement was added for the third case. He held us up bitching that that the newly added requirement for Case 3 didn't include Case 1 and 2. Dude. That shit has been in the software for 4 years. Those requirements were written by requirements guys that are better than you. Don't waste my time with semantics. Only I'm allowed to waste my time on semantics.

It wasn't really the project itself, but more the execution of it

Last semester we were tasked with writing a new programming language from scratch. We were a team of six people, everything went great to begin with. We discussed language features, the framework runtime it should run on and even what language to write it in.

Fast forward two weeks, nobody is doing anything but me, the two dudes tasked with helping me were both no-shows and the others were busy documenting the syntax and semantics of the language.

I basically ended up having to write the whole language myself with no breaks no help and no guidance.

A few weeks before deadline I completely burned out and couldn't do anything other than just sit and stare at the code; mentally exhausted and not in a mood to do anything other than doing mindless unrelated tasks. But alas work had to get done.

And it did get done... Sorta.
Our beautiful statically typed, statically scoped concurrent programming language that was supposed to compile to BEAM code was neither statically typed, statically scoped, and the output ended up being half-working elixir code that only worked on the most specific of cases.

I don't want to work with those guys again.

Holy fuck, I though working with Wordpress was a fucking nightmare, but it’s a dream compared to the shit I am estimating maintenance on...
It’s running on Asp.net and the Sitecore cms... I have no fucking clue what the fuck is going on anywhere

I’ve estimated 3-4 days for doing basic maintenance like improving SEO and fix some minor semantics. Everything is wrapped in a fucking <form> element, I mean every fucking thing. It goes;
<body><form method=POST>shit content</form><body>

I think I finally, really, comprehend why secret societies have historically been created... I mean the potentially logical ones. This train of thought is logically terrifying.

I want a logic check.

I've been jokingly mentioning some of my totally true, practically useless in most scenarios, skills/specific fields of knowledge/ability under a moniker of 'extremely useful, assuming apocalyptic event' for years. Things like advanced knowledge of Coefficients of glass expansion, Fortran, various things that have caused friends to refer to me as MacGyver after the reboot came out.

In recent years, I've personally encountered several varieties of the ones defined by helplessness, self-victimisation, some version of a real disability... that theyve expounded into a personified personal nemesis-- to flashily battle yet never overcome, etc... the vast majority perplexing me as to why that's a valid form of life to them... it's not that they never consider some other way; the ball is just quickly dropped and never picked back up.

College?(not that I'm a big fan) they wish they could but so expensive... aide? The form was hard/confusing/past-due...

Lookup/learn something more indepth than a tiktok? *some self-deprecating bs*

Yet it's "I always wanted to do/be/learn X"

Shows like 'How It's Made' fascinate, but don't inspire enough for a 5min google query.

In the dev world its a clear, inverted pyramid-- one of the first posts I saw when I rejoined here was ostream's rant on Apple sucking because after they stop support/updates you "can't" load a different OS... ofc you can. But several comments down... no mention of that... i think it was @LensFlare who was the only one in ~15 respondents to point out the core logical fallacy.

Basic shit is totally forgotten... try asking some random adults what plastic is made from... or pay attention to how many people declare they have a gluten "allergy".

I get people frequently telling me that things im pointing out as differences don't matter because "it's just semantics"... semantics is literally the epitome of "significance", with roots in 'meaning' and 'truth'

Back to the main issue... We are in a world where DIY is typically something you pay more to do as a catered experience than actually learning anything, people destroy their own arguments hopes of validity unwittingly often by stating the arguement, get 'offended' or 'triggered' by factual statements, propagate misinformation and bastardise words until MW needs money enough to print a new version, likely adding the misuse as an actual definition and basic knowledge and the thought to actually learn is vetoed by the existence of google translate, the wisdom of tiktok and the pure brillance of troubleshooting every random linux issue you have from not knowing basic CLI and thinking linux makes you cool, with chmod 777 because so many other dumbasses on forums keep propagating misinformation. Ask them what 777 means, most have no clue... as they didnt consider googling that one before putting it in a terminal several times.
The number of humans that actually know the basic shit that the infrastructure of the world is built on keeps decreasing... and we aren't even keeping a running tally.

The structure of the internet has the right idea... dns- 13 active master root servers, with multiple redundancies if they start dropping... hell ICANN is like a secret society but publicly known/obfuscated... the modern internet hasnt had a global meltdown... aside from the lack of censorship and global availability changing the social definition of a valid use of braincells to essentially propagating spam as if it's factual and educational.

So many 'devs' so few understanding what a driver is, much less how to write one... irl network techs that don't know what dhcp is or that their equiptment has logs... professionals in deducated fields like Autism research/coping... no clue why it was called "autism", obesity and malnutrition simultaneously existing in the same humans... it's like we need to prepare a subterranean life-supporting vault and stock it like Noah's ark... just including the basic knowledge of things that used to be common/obvious. I've literally had 2 different, early 20s, female, certified medical assistants taking my medical history legitimately ask if not having a uterus made it harder to get pregnant...i wish i was joking.

Any ideas better than a subterranean human vault system? It's not like we can simply store detailed explanations, guides, media... unless we find a way to make them into obfuscated tiktok videos apparently on nonsense or makeup tutorials.

My final year taking a B.Sc. I'm writing up my Distributed Systems project, the day before handing it in. It's on top of Transis, and source code is "stored" in RCS (yes, I'm that old). The project is a reliable system administration tool, that performs the same action across a cluster with guaranteed semantics.
I'm very proud of the semantics, but cannot figure out why the subdirectory installation stuff works almost but not quite. Here's my sequence of actions:
1. Install across all machines.
2. Manually see it's broken.
3. "rm -rf *".
4. Repeat.

What in to discover is that the subdirectory installation always finishes off in a current directory 1 level higher than where it started. Oh, and the entire cluster sees my NFS home directory. Oh, and I'm running each cluster member in a deep subdirectory of my dev directory. Oh, and my RCS files live in a subdirectory of my dev directory.

All of a sudden, my 5 concurrent "rm -rf *"s were printing weird error messages about ENOENT and not being able to find some inodes. In a belated flash of brilliance, I figure out all the above, and also that I've just deleted my dev directory. 5 times, concurrently. And the RCS files.

That was the day a kindly sysadmin taught me than NetApps have these .snapshot directories.

Yubikey: Worth it?
I'm a college student with way too many logins and offend reusing passwords. I also do password semantics research at the institution and know how useless they are.

In an object/dictionary/map config object where multiple source paths are mapped to destinations, which structure makes more sense to you (and why)?

1. { "src/path.ext": "dest/path.ext" }
2. { "dest/path.ext": "src/path.ext" }

Could also be a URI redirect map

I’ve been doing web development and mostly focusing on the frontend side of things professionally for almost 10 years. Still, I have to put up with some backend developer who did a couple of years of frontend development who now thinks he knows it all. Everytime someone reports a UX problem or asks for a feature that has some complexity and needs more thought to have a good enough solution, he steps out of his lane with “suggestions” on how to get it done with solutions that are half baked and don’t consider things like accessibility, responsiveness, or even semantics. Still, he is the hero and we’re the bad guys when we call him out for only providing crappy solutions and presenting them as complete solutions.

Currently working on a distributional semantics database or something like that. The goal is to read natural language texts and construct a graph of words, with directed edges containing the relative distances between them. Then I want to enter one or more words and find all of the possible words which could be used before, after or in between those words, simply based on the previously learned texts. Then I want to find words which are used in similar contexts and build a kind of dictionary that way.

The end goal is to use this to define software or other states and procedures, using natural language.

What do you think of this idea? Can you imagine it being feasable for its purpose? What are your thoughts?

Sometimes I ask myself how former IT people can become "Bosses"

Boss: We need to validate all links on our site

Me:Okay, let's vrab the response codes and some variations of under construction and we should be done.

Boss: No that only tests negatives, we need to test if the website content still matches.

Me: How?

Boss: Hmm... Just test if some keywords exist.

Me: So you want me to add a bunch of keywords for +-150 links? What about the maintenance?

Boss: Well, those sites basically never change.

Me: Then why do that?

Boss: Well, for when they change.

Now I can search through 150 mostly legal stuffy pages to find usefull keywords only to get a bunch of wrong negatives because the fucking semantics have changed...
+I have to type all that shit. Primarily, I have to type.

Having a question regarding build number semantics (Im working on android app for that matter)

My current app build which is released is 5.3.6 (build number 94)

I already merged one feature to develop but haven't released it.

I also finished working on another feature but haven't merged it to develop yet.

Now my question is should I make a new build (5.4.0 with build number 95) and just merge to master, then release to google play (it would contain both two features)

Or should I make a new build 5.4.0 bn 95, merge to master, release it. And then make another build for the second feature 5.5.0 bn 96 and release that as well?

My reasoning would be to go with 2 separate builds and versions (in case my second feature messes up, I can revert it and also it will be easier to manage versions).

But then what about users: will they receive two updates from google play or only one (the latest version) ?

Unguided code style decisions and the whole personal style things sometimes display an intention behind a piece of code. They can hint on semantics and relations between the pieces of data or operations, like it's often the case with grouping that doesn't separate bunch of statements with a blank line. Sometimes, they can even carry an emotional message. Love, hate, grudges, deepest affection for some golden hammer feature of the language, everything is on the table actually. For instance, this is what fear looks like:

3==o

!rant
I'm undertaking this huge personal project. For this I would require a serverside language/framework. Till now, I have only used php7 for backend, and although it gets the job done, its not fun to code in and is a pain in the ass. Since I learnt php after Angular, I have written php in a very Angular-MVC style (where I have custom components and templates; I did this because I wanted to see if I can use as little of javascript as possible).

I've heard django is really good, but I've never used it despite knowing python.

Dart is supposed to be really good, but I have no idea how to use it. Plus, can you run this on the server?

I would like to use dart as its syntax and semantics seem to be very nice. Is crystal a viable option?

The UML specification book satisfies OCD quite well I'd say.

Page 59, the actual content hasn't started yet, but I'm happy: "Within each clause, there is first a brief informal description of the concepts described in that clause. The clause is then
split into sub clauses, each describing a coherent set of concepts that constitute a portion of the formalism specified by
the clause. Each sub clause is then split into Abstract Syntax, Semantics, Notation, and Examples.
"

a = a + 1;

Change my mind.

Being a developer allows you to enjoy using most of the creative skills artists also put to use (writing structured prose, design, semantics, ergonomics, ethics), while adding logic, job safety, and a decent paycheck to the mix.

Also: puts you in a good position to readily take advantage of new digital goodies (eg bitcoin), and to understand the gem that is developer humor

Hypothetically, if I knew all the elements of a functioning programming language runtime, language syntax and semantics… do I need anything other than a parser generator to make my own?

You dipshits! Yet again...
- use contract X from team WeJustFuckUp
- WeJustFuckUps tell me I "used the contract with the wrong semantics"
- What the fuck how is that possible!? Explain to the fuck ups that if it's the wrong semantics then it shouldn't be documented. Ask what right semantics is... They do not support their own correct semantics...
Fuck you! Just say you fucked up and come to me with a new contract!

Two weeks pass, new contract breaks half the functionality... And they ask me: "is it a problem? Can't you use it as is?"

Now listen here you pile of elephant dung, you have an unresponsive system with an unscalabe architecture... You have twisted contracts and you come to me to fix them!? I have more to do then to babysit your assess!

I am so tired of your bulshit... You are a bunch of prairie dogs hitting keyboards and call yourself developers!? My dog is a better developer, he at least does not break he's own software and when he takes a massive dump he owns it...

I am this close to making a request of changing your work computers to an abacus! It's all you can handle...

Fuck off! You are waste of resources and your parents should be spanked!!

What are the best online resources to learn the basics for front-end development? (HTML/ Semantics / CSS / VCS / Workflow basics )

We're setting up a baseline for our new interns, in case they don't know the basics, we'd like some good material.