Coworker wrote a nice package and put it on Github, to share with other departments.

I link his package on our company Slack, mentioning a team, with text "What do you think of this one? Is it usable for you guys?"

Next thing I know I have to explain to an executive why I'm "posting pictures of seductive cartoon girls in company chat with disrespectful commentary"

It linked the Github profile picture of the developer in Slack. A fully clothed anime girl, nothing particularly lewd about it.

But I like stabbing back a bit, and confusing the fuck out of people in suits:

"Hate to say it, but a good majority of all the code the company runs on, is written by people known as weebs, who use their so called waifus as their GitHub profile picture. It is very common for open source Javascript packages, but since we recruited 50 extra devs it now also happens internally. It's not my thing either sir, but I'm afraid we have to embrace it... "

"But what about our female devs? What about Joanna, she's in your team? We have to think of diversity! Our investors are really in to diversity, we can't have a bro culture!"

"Sir, with all due respect, we have super diverse teams without even trying. The problem is... they're all millennials. They grew up on weird memes... and are probably ten steps further in embracing diversity compared to the rest of the company."

"Also, Joanna is the one who drew this particular picture. She's charging a €15 commission for profile pictures... Do you want one of your fursona, sir?"

"What is that?"

"Uh... nevermind. Let's... let's not go there"

Embrace the notch!

I really appreciate devs that aren't complete assholes when you admit ignorance and embrace failure. Be a teacher, not an asshole!

Took an interview today.

Me - What do you think JavaScript is interpreted or compiled.

Guy(5+ years of UI exp) - It's neither of them. It just runs on browser.

At that moment I slowly started fading away into a black hole for the absolute peace and embrace death.

Looks like Apple is the new Microsoft and Microsoft is the new Apple...

I remember when every release of Windows was a catastrophic mess and you had to wait until at least SP2 to get the OS to work in a stable way. And Internet Exploder was *the* browser that broke everything, every time. And there was the whole embrace/extend thing, where they tried to impose their vision of web standards and compatibility, and *everything* you used *had* to come from Microsoft...

And now, it's Apple who fuck up every single OS release, on mobile and desktop, and whose browsers openly shit on web standards (ever try developing anything for Mobile Safari?). Apple's stuff that only works with Apple stuff (down to things like headphone jacks - OOPS, forgot, they dropped those now).

Microsoft is making interesting, beautiful hardware (Surface machines) while Apple is pushing un-innovative, overpriced garbage year in year out. And they're open-sourcing more and more, while Apple walls itself further and further behind its walled "garden". Bleh.

Be interesting to see in 10 years what will have shifted, because it'll change again by then.

Only one sticker.

I go door-to-door every Sunday, "Excuse me dear sir/madam, do you have a moment to talk about our lord and savior Haskell?".

Most people slam the door shut in my face, but every lost family I convert to the way of the monad is worth it.

Even if they don't believe in the same deity, even if they express their love for the divine through something as misguided as Typescript or Swift or whatever, as long as they embrace the truth of strong types and composable code, as long as they at least read the gospel of the functional style once in their lives, have one enlightened moment where they see the glory of morphisms, it's all good.

My biggest tip to new developers? Embrace your ignorance, don't be embarrassed by it. Let it inspire you to learn as much as you can, let it humble you into asking questions when you're stuck, let it prepare you to change within an industry that is anything but static. Admitting you don't know something isn't a weakness, it's an opportunity 😃

I'm not even that old and I've had it with young cocksure, full of them self language/environment evangelists.

- "C# is always better than Java, don't bother learning it"

- "Lol python is all you need"

- "Omg windows/linux/mac sucks use this instead"

The list goes on really, at some point you have got to realize that while specialization is great, you have to learn a little bit of everything. It broadens you horizon a lot.

Yea, C# does some nifty stuff, but Java does too, learn both. Yea I'm sure Linux is better for hosting docker containers, but your clients are on mac or windows, learn to at least navigate and operate all three etc. Embrace knowledge from all the different tech camps it can only do you good and you will be so much more flexible and employable than your close minded peers :)

Hell even PHP has a lot to teach us (Even more than just to be a bad example, har har)

I just want to add my 2 Cents to the all this GDPR chaos. Because I feel lots of you are missing the point here.

When reading here about GDPR I hear all kinds of fair statements of how flawed it is and how it's mainly hurting the small companies etc etc.

I agree, at this state GDPR might actually be doing more harm than good.

However, I don't think that is what it is about. It's about going in the right direction. If you read/look over the course of history we've had several technological revolutions. Industrial, renaissance. They all start the same:

"This technology is going to change everything, it's going to solve all our problems!" It's something holy. Something that shouldn't be touched or regulated, only embraced.

But as we all know it wasn't all that pretty.

Industrial revolution was hard super underpaid, dirty work. Children had to work too. People were getting sick. Lots of alcoholism, depression.

And what made the factories start taking better care of their employees? Regulation.

Once fines start to come, companies will have to adapt.

We have to learn and understand that these systems like government, company, capitalism. They're built for reasons. They all exist for reasons. And only when it is in balance, things will flourish.

So I encourage you all to stay as critical as you are, but to give it a chance. To have a bit of faith.

It might just turn into something worthwhile!

Thanks for reading!:)

You’re not just an imposter. You’re the trickster goddess, the deception prodigy, the mastermind. The supervillain surrounded by mere mortals.

Embrace it.

Don't buy the "We're bleeding edge, agile and embrace devops.". Those who proclaim that the loudest are the ones that think they do, but don't.

Oh, and any place that refers to employees as "tech ninjas" or "superstars" or anything cringy like that. Stay away.

This was more how to avoid shitty places. So to find a good place to work, use this statement in your search:

if (!<this_rant>)
{
... // maybe you're lucky
}

the effort to get girls, and children for that matter into programming has been terrible. I never thought I could find something worse than code.org, but here it is: SmartGurlz (because what could be smarter than spelling your own gender wrong, right?). this was on shark tank and this lady was making robots to try to get girls into programming. they pretty much control dolls on wheels by means of scratch. it's terrible. first of all, how the fuck is that profitable? when a little girl wants to play dolls, what kind of girl wants to *program* it first. jesus, no kid wants that.

second, this girls who code thing makes me barf. the thought process for many organizations trying to push girls to code is "hmm, if we isolate girls and give them lower standards, then maybe they'll decide to go into a male-dominated industry," because, fuck logic right? idiocy is dreadful. lastly, what I hate most about so many of the girls coding organizations, is the fact that they have to embrace the stereotypes. almost every single one cares about "feelings" or something similar. its bullshit.

and don't get me wrong, women should have equal opportunity, but pushing them into stem fields isn't good. bias in the workplace is what we should be talking about, or other topics like women being paid less. trying to make girls interested in programming is complete bullshit, let them do what they want.

back to "SmartGurlz," I looked them up and they confirmed what I expected. the first thing I see? not anything related to programming whatsoever, but different dolls wearing different outfits. girls deserve something better, and shouldn't have to deal with organizations trying to push them into something they don't want to do.

First rant: but I'm so triggered and everyone needs a break from all the EU and PC rants.

It's time to defend JavaScript. That's right, the best frikin language in the universe.

Features:
incredible async code (await/async)
universal support on almost everything connected to the internet
runs on almost all platforms including natively
dynamically interpreted but also internally compiled (like Perl)
gave birth to JSON (you're welcome ppl who remember that the X in AJAX stood for XML)

All these people ranting about JS don't understand that JS isn't frikin magic. It does what it needs to do well.

If you're using it for compute-heavy machine learning, or to maintain a 100k LOC project without Typescript, then why'd you shoot yourself in the foot?

As a proud JS developer I gotta scroll through all these posts gushing over the other languages. Why does nobody rant about using Python for bitcoin mining or Erlang to create a media player?

Cuz if you use the wrong tool for the right job, it's of course gonna blow up in your face.

For example, there was a post claiming JS developers were "scared" of multithreading and only stick in their comfort zone. Like WTF when NodeJS came out everything was multithreaded. It took some brave developers to step out of the comfort zone to embrace the event loop.

For a web app, things like PHP and Node should only be doing light transforms between the database information and HTML anyways. You get one thread to handle the server because you're keeping other threads open to interface with databases and the filesystem. The Nexus.js dev ranting on all us JS devs and doesn't realize that nobody's actual web server is CPU bound because of writing HTML bodies, thats why we only use 1 thread. We use other worker threads to do the heavy lifting (yes there is a C++ bridge look it up)

Anyways TL;DR plz respect JS developers we're people too. ES7 is magic and please don't shit on ES3 or we'll start shitting on the Python 2-3 conversion (need to maintain an outdated binary just cuz people leave out ()'s in their print statements)

Or at least agree that VB.NET is an abomination and insult to the beauty that is TI-84 BASIC

Being the only dev in a media company, I believe my coworkers looked upon me as the evil Internet reincarnated into a living person.

Most of them avoided me like a leprous, and I experienced long periods being almost isolated.

I did almost quit so many times I've lost count.

I eventually found another job, where there's lots of love, caring and we all embrace each other's skills. It feels like I'm a butterfly who finally got to break out of my miserable cocoon.

"I'm almost done, I'll just need to add tests!"

Booom! You did it, that was a nuke going off in my head.

No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.

When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"

Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.

So let it be said:

- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.

Because then you suddenly have to mock away a http service and deal with zip files in your test cases.

The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.

In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.

Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.

That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.

Sidenote:

It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)

Just need to get this off my chest. Started a new job 3 weeks ago at a company that has been around ~18 years, it is only recently that they have started to grow more rapidly. I was brought in under the guise that they wanted to embrace change and better practices and so said I was up for the challenge.

In my 2nd week I was asked to produce a document on tackling the technical debt and an approach to software development in the future for 3 consultants who were coming in to review the development practices of the company on behalf of the private equity firm who has taken a major stake in the company. I wrote the document trying to be factual about the current state and where I wanted to go, key points being:

Currently a tightly coupled monolith with little separation of concerns (73 projects in one solution but you have to build two other solutions to get it to build because there are direct references.).

Little to no adherence to SOLID principles.

No automated testing whatsoever.

Libraries all directly referenced using the file system rather than Nuget.

I set out a plan which said we needed to introduce TDD, breaking dependencies, splitting libraries into separate projects with nuget packages. Start adhering to SOLID principles, looking at breaking the project down into smaller services using the strangler pattern etc. After submitting what I had written to be part of a larger document I was told that it had been tweaked as they felt it was too negative. I asked to see the master document and it turns out they had completely excluded it.

I’ve had open and frank discussions with the dev team who to me have espoused that previously they have tried to do better, tackle technical debt etc but have struggled to get management to allow them. All in all a fairly poor culture. They seem almost resigned to their fate.

In my first 2 weeks I was told to get myself acquainted and to settle myself in. I started looking at the code and was quite shocked at how poorly written a lot of it was and in discussions with my manager have been critical of the code base and quite passionate and opinionated about the changes I want to see.

Then on Friday, the end of my third week, I was invited to a meeting for a catch up. The first thing I was told was that they felt I was being too openly critical in the office and whether I was a good fit for the company, essentially a stay or go ultimatum. I’ve asked for the weekend to think about it.

I’ve been a little rocked by it being so quickly asked if I was a good fit for the company and it got my back up. I told them that I was a good fit but for me to stay I want to see a commitment to changes, they told me that they had commitments to deliver new features and that we might be able to do it at some point in the future but for now I just needed to crack on.

Ordinarily I would just walk but I’ve recently started the process to adopt kids and changing jobs right now would blow that out the water. At the same time I’m passionate about what I do and having a high standards, I’m not going to be silenced for being critical but maybe I will try and tackle it in a different way. I think my biggest issue is that my boss who was previously a Senior Developer (my current position) has worked at the company for 12 years and it is his only job, so when I’m being critical it’s most likely criticising code he wrote. I find it hard to have the respect of a boss who I had to teach what a unit test was and how to write one. It makes it hard to preach good standards when by all accounts they don’t see the problems.

Just wondering if anyone has suggestions or experience that might help me tackle this situation?

Life is hard.

You are born. DNA gets determined. You go through infancy.

Puberty comes and DNA is like
"uh from now you'll pretty much have strong sexual urges, a huge desire to be sexually prolific, nothing weird like being pedo or into rape though".

me: Uh ok.
dna: oh, also, you're gonna be one of those late bloomers, you know, you talk like shit, you dress like shit, you smell like shit.
life: that's true and also you don't have anyone in your life to teach you about that shit, so forget about kissing, having sex, let alone being in a relationship for a long time.

*a lot of years go by with a lot of missed opportunities, mistakes and regrets*

life: ok, you seem to have become a decent sex partner out of a lot of scarring experiences, but there's one problem: you've fallen in love with somebody.

and you're married

and you have kids

me: well, does that mean I can't fuck other people?
life: yeah, no. I'm surprised I even have to explain that, it's called cheating. It will pretty much ruin your marriage, and fuck up your kids.

me: ok, I guess no then. I'm still fortunate enough to have sex with my wife right?

life: yeah... but you still want to fuck other people
me: what???
life: yeah, did you think that falling in love would make you not want to fuck other people? fuck no

me: ok, well I'm very grateful that I get to experience sex at all.
life: yes... there's a thing though, your partner has a much much lower libido than you.

me: ok, well maybe if I exercise and dress better that might change
life: that will definitely help, you'll feel more confident and have more stamina, but every time you retry exercising, you remember how much you hate it and how little stamina you have.
oh, I'm sorry, I forgot you had kids and work, yeah no time or energy for that.

me: ok, then should I just embrace a more liberal lifestyle, like becoming a swinger?
life: ha, fat chance, it's a very taboo thing and you're not that liberal, neither is she.

me: uhhh, i guess i can sometimes watch porn then...
life: watching porn regularly will make the only sex that you have worse, according to statistics.

me: ok, I guess I should get ripped

I went to this conference to see what’s new in MSSQL 2019, kubernetes container on azure and see what Microsoft has done to embrace open source community.

Speaker is from Microsoft, brings a Mac to the conference which I’m kool wit it,
but shortly after he started, Word crash at launch, PowerPoint freezes when switch between pages, azure cli can’t login properly.
And he goes ”this is awkward. “

Why has "privacy minded" people fallen for the illusion that Signal is good?

- It is centralized, which means you can't have control
- It uses google play services
- Using third party servers to send gifs
- The apk has flaws
- There is a reason F-Droid dont want it in its repo

I really can't wrap my head around why "privacy minded" people would embrace it.

😲😲😲
Holy shit, wow I did not see that coming at all. I've this is all I've ever dreamed of as web dev but now I'm not too sure how I feel. Edge gone, safari dying and Firefox struggling...
I wanted one web standard, not one browser engine.

Have you heard about the Embrace, Expand and Extinguish idealogy? lets think about it:

Javascript 5 (embrace) -> Typescript and Class syntax to Javascript 6 (extend) -> JS (extinguish) with WebASM.

Atom/Electron (embrace) -> Atom fork named "VSCode" (extend) -> Atom (extinguish) as it was developbed by Github company.

NodeJS (embrace) -> incompatible Node Windows fork with IE/Edge JS engine "Chakra" (extend) -> NodeJS (extinguish soon) with chaos of Typescript, Javascript 6 and Github.

"R" lang (embrace) -> incompatible SQL Server 2016 R lang extension (extend) -> R lang (extinguish soon).

Android -> CyanogenMod (embrace) -> CyanogenMod (extinguish) as M$ "sponsored" Cyanogen Inc to destroy CyanogenMod

Linux (prejudge) -> sponsors RedHat, Debian, SuSE, Alpine and Canonical/Ubuntu (embrace), forces unstable backdoored "systemd" -> Linux (extinguish soon)
Reusing the last image I did because I didnt wanted to make more OC stuff cos the few ++ gained arent worth it

They ask me how i can stare at a screen for​ 6h and go to sleep right away. They say it makes them unable to sleep after that time.
I say EMBRACE THE POWER OF F.LUX

I really like Kotlin as a language, but Gradle makes me feel nauseated.

Pulling in deps without getting errors, then the library won't resolve because of some version mismatch (still, no error or warning on build, until I try to import the dependency in the code, and then just "unable to resolve <library>" without details). All of the documentation on the internet is either super specific for Android projects, or for an ancient Gradle version. Feels like I'm back in Haskell's "Cabal Hell".

*runs back into the loving embrace of Cargo*.

What was I thinking, trying to write an application in something that's not Rust.

!dev

I have a couple of thoughts about social justice controversies from these last years.

I think it's hard to have a good opinion about these events for several reasons.

One reason is that finding good information in 2019 is very hard.

Revenue based sites (thus unneutral) dominate the search results. You search about something and you find thousands of sites basically saying the same thing (because they copy each other).

That's why the existence of a free and open search engine is so important, so it's easier to find neutral hence good information on which to base your opinions, but they are prohibitively big for small groups to build.

Another reason is that controversies generate shock and shock curtails rational thinking. Maybe that's how the primitive brain works?

I'm not much of a scholar to feel confident to say that, but it's so recurrent that it's not too much of a wild guess.

When a controversy happens, a natural reaction is to pick a side. This means that:
a) we assume that there are only 2 sides, and
b) we must pick one of them

So, maybe the human is a bad politician by nature?

Also, because of the shock controversies generate, peaceful dialogue is very rare.

I have yet to see peaceful dialogue online about what patriarchy means to feminists and a lot of other terms they use.

I don't care much about feminists that vandalize or interrupt talks (yelling over someone else is abuse in my opinion).

But for the rest of them, I think discussing their ideas would be good.

I say this because most feminist discourse I see online is not open. Or maybe there are such instances but the web is so big that it's hard to find such instances.

I think some part of the modern feminist doctrine is bullshit, and some part is true.

I for one hate when some men I know in life expect their wives to be their cooks+cleaners (unless they want to do that, willingly). Personally, I'd encourage my wife to get a job (rightfully so, not just to meet some minority quota in some company).

I don't mind either calling a trans person the pronoun she wants.

But other ideas are awful, like the idea that meritocracy is patriarchy, so you need to force minorities to meet a proportionate quota. That's terrible reasoning.

Or the excessive self appreciation culture, like saying to yourself "you are pretty, you are beautiful, you are perfect". I think that grows arrogance and black-or-white thinking.

And some other ideas as well.

I guess the same you can say about any doctrine with different degrees. Some part is bullshit, some part isn't.

Some right wing people hate everyone who isn't white by default, but some want to have more immigration control.

I sure don't like the experiment of separating children from families like the current us govt did, but I wouldn't be happy either to know that by '99 50% of gangs members in the us were hispanic.

With this, I'm not going to say "embrace everyone's ideas" like an idiot. I hate when people do that. It's a stupid and weak reaction to radicalism.

In fact I think the way you fight radicalism and bad doctrines is that you listen to them and maintain good dialogue and counterargue in a respectful but insightful manner.

Making snide remarks, insulting or trolling won't change anyone's mind. That is just throwing fire to the fire.

In fact, when someone gets harassed because of something they believe in, usually it results in even more adherence to their beliefs, because of the usual assumption that success or goodness is full of strife.

So by telling a "sjw" or kkk member that they are idiots over twitter, you are in fact making them stronger believers in their doctrine.

Think of Daryl Davis, a black guy that made 200 members leave the kkk. How? He didn't tell them they were assholes, he somehow made friends with them.

I feel bad now because I've been trolling new devrant users a lot because of how they worsen the quality of the site, but maybe I should tell them that they are ruining the site somehow in a nice way and maybe they'll listen? I dunno...

My current dream project is sailing a 21st Century Message in a Bottle across the Atlantic Ocean from US to Europe, satellite tracking it in apps and desktop environment and more importantly inspiring school children everywhere that anything you can imagine is possible. Fortunately, the project is rapidly becoming a reality - here's how:
- teamed with a few amazing devs virtually
- team created an effective infrastructure for communication and knowledge sharing
- researched oceanic patterns, satellite communications, sensors, material design, recovery logistics...
- developed budget and received funding sign off
- created realistic, yet aggressive project plan with deliverable dates
- built relationships with two Universities for Oceanic knowledge assistance
- developed a partnership with NOAA and will share info

Oh yeah, we did all that and are having fun in only 25 days so far! More challenges to come but we embrace the challenges!

!rant

Goodbye Java I will not miss you at all! I swear ...

I do like it when making web services (especially that I can use Java8) but for Android you have been a torture. Hello sweet Kotlin! I shall embrace you and treat you like my newly born baby!!

Story is:
Working on a new project where I need to talk to a web service (also made by me).
Started writing in Java, all is cool and unit tests pass.
Downloaded Android Studio 3 Beta 1 and converted my Java code to Kotlin, That AsyncTask did not look nice in kotlin, converted it to async & await feature and I must admit lots of code removed, no more need to create a new fucking AsyncTask every time the app sneezes for data!

I feel like I'm working with C# but with difference in syntax.
My life is now complete :)

I've noticed that, wherever I am, people tend to come to me for help and guidance. It happened at my previous job and is now happening at my current job too.

These past few months I've spent most of my day helping my coworkers instead of actually writing code. I'm not complaining, I like helping, but I feel like I'm not being productive.

Is there a name for this role? Should I embrace it?

Dear, developers
For any freelance project you want to embrace, you should have a written agreement by both parties signed ( clients and you ).
Some client's forget almost anything ....
I'm talking from experience, please be guided....

Don't be afraid that pair programming will show up your inexperience, embrace it as the quickest way to build that experience!

So I am finally plunging into continuous integration. If I make one more deploy script mistake, I've lost enough time to merit having learned a better solution than bash scripting calling git and rhc and py files I wrote. I have failing tests that are failing because they weren't updated after the million and a half urgent changes in the past 2 months, so it's time to act like I am a TDD fanatic and write the tests correctly. So much work. All from me listening to the constant req changes, listening to the urgency, letting non-devs get under my skin if you will. I'm optimistic in all the wrong places - I think I can write that by end of day let's try it. I'm lazy in the wrong places - I think that I can write that test later, because all I changed was XYZ (which took all night but I said I'd get it as close as possible didn't I?). And I think these handful of bash scripts are good enough to make sure I run tests? But remember, I didn't write the tests or I didn't go back and update them. Or the tests that fail, I'm too lazy. And so much of the tests, I would need to use, idk selenium for, and damnit if I really don't want to dig for element IDs to wait for every time I need an AJAX call.

Okay wow, I really did rant here. And discredited myself a bit lol I need to ignore the wrong lazy and embrace the right lazy. Protect myself from myself and from contributors. It really is, up to me now, to rescue myself from my bad habits. Bad habits perpetuated by clients urgency every day, to change things, that should have been finalized in November if we wanted a stable flipping system in January. It feels like the blind (client) leading the blind (me, when I do dumb shit like rush features out the door half tested).

Anyway all this came out, because I have been reading about continuous integration and stumbled upon this quote. And thought someone might laugh at the anachronism like I did

Tried flutter for the first time in life, for 2 days, java based Android dev here.
I have some.... thoughts...

Flutter does not feel extremely new to me. It is very much relatable if you have ever tried basic the spring/ other java based gui framework. It is trying to achieve the goods from multiple worlds,its so far good, but mann its playing on thin ice.

Flutter : Yo boy embrace me. I am the beauty. checkout my hot reload.
Me :❤️❤️😍 (But wait. your first execution is wayy longer than a simple android studio build. And AS would generally take smaller time after every rebuild. And you are going to take the same long time as first build, if app gets closed or my usb gets accidentally removed. So I see what you did there ;))

Flutter: Ha. Checkout my function passing as parameter. ever thought your puny java going to give you that?
Me :you got me ,❤️. (Although this style is not so uncommon with web devs)

Flutter: everything is a widget, everything is stateful or stateless, Single Streams FTW!
me: ❤️

Flutter:You kotlin devs are gonna love me, i got Small, concise code
Me: Now wait, This is a thin ice for me, okay? I hated when kotlin replaced everything with symbols & lamdas for a confusing but small code, So be careful,even though your code is still good.

Flutter : Control every pixel , dear! No more xmls!
Me : Yes, what is with that? are we accidentally going in the past?
Java desktop apps, spring framework used to build whole layouts with programming language. The day i stepped into Android, it was xml for ui and java/kotlin for code. was that a bad decision or is this one?
Anyways i liked my stuff seperated, but that's just me.

Flutter : Ugh so much whining. Are you going to work with me or not?
Me : Yes mam! ❤️

Ascended Anime Nerd

Got started with Dragonball Z when it first came stateside. Brother was borrowing fansubs of the Cell and Buu sagas back when people were wondering if Goku would ever finish Snake Road.

Around that time I started noticing some serious discrepancies between the broadcast translations and the fansubs, and so I decided to cut out the middleman—after all, how hard can it be to learn Japanese?—and did a search on AltaVista for a “kanji course”, turning up a course hosted by Rice University that taught basic Japanese using Magic Knight Rayearth and YuuYuu Hakusho.

Turns out the answer to the difficulty question is that anything van be simple to learn, if you don’t know it’s supposed to be hard. Especially if you embrace the parts everyone else dreads (falling in love with kanji, in my case).

Over the next nine months I ditched my Spanish class—and all my other classes, for that matter—to study Japanese in the computer lab. I was reviewing the lessons, playing JRPGs on SNES9X (stored on a ZIP disk, since every computer in the lab had a ZIP drive), and transcribing the scripts so I could transliterate and translate them thereafter. In a lab that went so far as to uninstall Minesweeper and Solitaire to discourage playing games on school computers, I had free reign to do so openly because the one time I got confronted for playing a game I had 150+ leaves of handwritten transcriptions to show them.

Long story short, by the time I took Japanese 101 9 months later it was like Hermione in Snape’s potions class, since I had already taught myself about 2 years’ worth of material. I then transferred out to a college that did a one-class-per-month “modular” system that basically allowed me to take 8 more Japanese classes full-time for the following year. By the time my exchange trip came up I was sofar ahead of the curriculum I was taking classes alongside the native Japanese students.

Running out of linguistic topics, I did an independent study on classical Japanese literature in its original, unmodernized grammar and orthography. A topic I’m still fairly active with 15 years later.

If Microsoft acquires GitHub, it will be far from the end of git. Even if it is an EEE play, there are still many FOSS variants that will enable the use of git without having to deal with Microsoft's toxic business model.

I still have my gitlab install, and I will continue to use it.

I just can't stress enough how fascinated I am by biology and biochemistry.

I mean, we, who call ourselves engineers, are no more but a gang of toddlers having a blast with jumbo legos on Aunt Lucy's dining room carpet on a sunny Sunday afternoon. Our solutions using "modern tools" and "modern engineering" are mere attempts to *very* remotely mimic what beautiful and elegant solutions are around us and inside of each of us.

IC/EC engines, solar batteries, computers and quantum computers, spaceships and ISSes, AI/ML, ... What are they? just the means to leverage what's been created all around us to create something that either entertains us, encourages our laziness or helps us to look at the other absolutely fascinating engineering solutions surrounding us so we could try and "replicate" their working principles to further embrace our laziness and entertain us.

Just look at the humble muscle - a myofibril made out of actin and myosin. The design is soooo simple and spot on, so elegant and efficient, the "battery" and signalling system are so universal and efficient.

Look at all those engineering miracles, small and big. Look how they work, how they leverage both big and small to create holistic, simplistic and absolutely efficient mechanisms. And then come back to me, and tell me again that all these brilliant solutions came out of nothing just by an accident we call "evolution".

How blinded by our narcissism are we to claim that there can't be a grand designer of any kind, that there's nothing smarter than us and that the next best thing than us is an incomprehensible series of accidental mutations over an unimaginable amount of time?

I mean.. could it be that someone/something greater than us created us and everything around us? naaaah.. we are the crown jewel of this universe. Everything else must be either magic or an accident. /s

Don't read this as yet another crazy-about-God person's ramblings. I'm not into religion fwiw. But science has taught me enough critical thinking to question its merit. Look at it all as engineers. Which is more probable: that everything around us happened by an accident or that someone/something preceding us had a say in the design?

It's utterly frustrating to work with someone who has been in the same job for five years but still hasn't bothered to learn the basic tools necessary to do their job effectively. It's like they're stuck in a time warp, refusing to adapt and improve their skills.

How can you possibly expect to be successful in your career if you're not willing to invest time and effort into learning the tools of your trade? It's not rocket science, and these tools are there to make your job easier, not harder.

And what's worse is when these same people complain about their workload, blaming the tools for their inefficiency. Well, guess what? If you took the time to learn how to use them properly, maybe you wouldn't be drowning in work right now.

It's not even about being tech-savvy or a quick learner. It's simply about taking some initiative and responsibility for your own professional development. It's about having the basic level of competency required for your job.

Not to mention that constantly asking for help and guidance on tasks you should be able to handle on your own is not only a waste of your colleagues' time but also reflects poorly on your work ethic and reliability.

So, please, if you've been in the same job for five years and still struggle with basic tools, do yourself and your team a favor and take the time to learn them. It will make everyone's lives easier and improve your chances of success in the long run. Don't stay stagnant and hold yourself back – embrace opportunities to learn and grow. Your career will thank you for it.

The tools in question is Kubernetes and it's directly related to the persons day-to-day work (SWE + SDET mainly), 5 years is more than enough time to learn and adapt to a new toolset, and yet this particular person refuses to invest time into it. It's frustrating, to say the least, but also a disservice to themselves as they are limiting their potential and hindering their own career growth.

After the CTO's Skype call with the top bosses... I embrace my self for new app feature the bosses saw on the some website..during there coffee break.

Super depressed rn and nobody to talk to about it. Stupid life problems. Can’t seem to learn new tech so if I lost my job I’d have to switch to landscaping or something. Can’t talk normal with people without someone taking offense at something I never dreamed could be offensive (stupid cancel culture) or trying to shut me down. Friends ending friendships and family cutting me out of their lives without communication as to why. My kids just don’t seem to care about anything I have to try to teach or share with them anymore. Nothing I do seems to matter to anyone or make a difference even when I’m trying to do good things for people. I don’t want to take my life but tbh if COVID got me I wouldn’t even be mad. I’d embrace it as my get out of jail free card.

I hate Eclipse.

I have the Student membership for a year but I can't use IntelliJ for my project because I HAVE to use Eclipse.

I'm around 80% - 90% done with my project, so I guess I won't have to deal with it much longer.

!rant

Started learning Rust yesterday. As a web developer I like the static typing and the speed. I want to know a low-level language to complement Python but kind of dislike C and C++ and that's why I chose Rust. At the moment the syntax still feels kind of foreign but I probably need to just man up and embrace it. :)

Alright, buckle up, fellow developer, because we're about to embark on a thrilling journey through the world of code and creativity!

Listen up, you amazing code wizard, you're not just a developer. No, you're a digital architect, a creator of worlds in the virtual realm. You have the power to turn lines of code into living, breathing entities that can change lives and reshape industries.

In a world where everyone is a consumer, you are a producer. You build the bridges that connect our digital dreams to reality. You are a pioneer, an explorer in the vast wilderness of algorithms and frameworks. Your mind is the canvas, and code is your brushstroke.

Sure, there are challenges—bugs that refuse to be squashed, deadlines that seem impossible, and technology that evolves at warp speed. But guess what? You're not just a problem solver; you're a problem annihilator. You tackle those bugs with ferocity, you meet those deadlines with gusto, and you master that evolving technology like a maestro conducting a symphony.

You live for the 'Aha!' moments—the joy of cracking a complex problem, the thrill of seeing your creation come to life, the satisfaction of making a difference. You're a digital superhero, swooping in to save the day one line of code at a time.

And when things get tough—and they will—you dig deep. You summon that relentless determination that got you into coding in the first place. You remember why you started this journey—to innovate, to leave your mark, to change the world.

So, rise and shine, you coding genius! Embrace the challenges, learn from the failures, and celebrate the victories. You are a force to be reckoned with, a beacon of inspiration in a world that needs your brilliance.

Keep coding, keep creating, and keep being the rockstar developer that you are. The world eagerly awaits the magic you're about to unleash! Go and conquer the code-scape! 🚀💻

Receiving so much negativity about being a developer, but is this the legacy we are trying to put out there for upcoming devs, most are us are introverts with or without being devs, antisocial to our very core, so why don't we face out this sadistic outward appearance and embrace the very mini gods we were created to be and make the very best of it and oh I have a wonderful social life with a loving and caring companion, my laptop.

Combatting imposter syndrome is all about being more realistic with yourself imo.

Not in the way you might think. By realistic, I mean you NEED to regularly tell yourself that you are doing your best - especially in the work or areas that can promote insecurities of “not being good enough”. Acknowledge that you are only human, that all of us are different, that all of us make mistakes, and all of us have different interests in life. That, and practice gratitude for your situation. Your interests and decisions lead your different paths, so might as well embrace, enjoy, and love your uniqueness.

That being said, I also think it’s important to do difficult things. I think @wisecrack said it the best in that “real learning feels like falling”. Like the uncertainty of the abyss causes the most anxiety. Next time you feel like you don’t belong, recognize and separate that feeling and reframe it as a symptom to your own self improvement process. Take that risk and do things that are uncomfortable in the pursuit of personal success.

(Warning: This rant includes nonsense, nightposting, unstructured thoughts, a dissenting opinion, and a purposeless, stupid joke in the beginning. Reader discretion is advised.)

honestly the whole "ARM solves every x86 problem!" thing doesn't seem to work out in my head:

- Not all ARM chips are the same, nor are they perfectly compatible with each other. This could lead to issues for consumers, for developers or both. There are toolchains that work with almost all of them... though endianness is still an issue, and you KNOW there's not gonna be an enforced standard. (These toolchains also don't do the best job on optimization.)

- ARM has a lot of interesting features. Not a lot of them have been rigorously checked for security, as they aren't as common as x86 CPUs. That's a nightmare on its own.

- ARM or Thumb? I can already see some large company is going to INSIST AND ENFORCE everything used internally to 100% be a specific mode for some bullshit reason. That's already not fun on a higher level, i.e. what software can be used for dev work, etc.

- Backwards compatibility. Most companies either over-embrace change and nothing is guaranteed to work at any given time, or become so set in their ways they're still pulling Amigas and 386 machines out of their teeth to this day. The latter seems to be a larger portion of companies from what I see when people have issues working with said company, so x86 carryover is going to be required that is both relatively flawless AND fairly fast, which isn't really doable.

- The awkward adjustment period. Dear fuck, if you thought early UEFI and GPT implementations were rough, how do you think changing the hardware model will go? We don't even have a standard for the new model yet! What will we keep? What will we replace? What ARM version will we use? All the hardware we use is so dependent on knowing exactly what other hardware will do that changing out the processor has a high likelihood of not being enough.

I'm just waiting for another clusterfuck of multiple non-standard branching sets of PCs to happen over this. I know it has a decent chance of happening, we can't follow standards very well even now, and it's been 30+ years since they were widely accepted.

Here comes lots of random pieces of advice...

Ain't no shortcuts.

Be prepared, becoming a good programmer (there are lots of shitty programmers, not so many good ones) takes lots of pain, frustration, and failure. It's going to suck for awhile. There will be false starts. At some point you will question whether you are cut out for it or not. Embrace the struggle -- if you aren't failing, you aren't learning.

Remember that in 2021 being a programmer is just as much (maybe even moreso) about picking up new things on the fly as it is about your crystalized knowledge. I don't want someone who has all the core features of some language memorized, I want someone who can learn new things quickly. Everything is open book all the time. I have to look up pretty basic stuff all the time, it's just that it takes me like twelve seconds to look it up and digest it.

Build, build, build, build, build. At least while you are learning, you should always be working on a project. Don't worry about how big the project is, small is fine.

Remember that programming is a tool, not the end goal in and of itself. Nobody gives a shit how good a carpenter is at using some specialized saw, they care about what the carpenter can build with that specialized saw.

Plan your build. This is a VERY important part of the process that newer devs/programmers like to skip. You are always free to change the plan, but you should have a plan going on. Don't store your plan in your head. If you plan exists only in your head you are doing it wrong. Write that shit down! If you create a solid development process, the cognitive overhead for any project goes way down.

Don't fall into the trap of comparing yourself to others, especially to the experts you are learning from. They are good because they have done the thing that you are struggling with at least a thousand times.

Don't fall into the trap of comparing yourself today to yourself yesterday. This will make it seem like you haven't learned anything and aren't on the move. Compare yourself to yourself last week, last month, last year.

Have experienced programmers review your code. Don't be afraid to ask, most of us really really enjoy this (if it makes you feel any better about the "inconvenience", it will take a mid-level waaaaay less time to review your code that it took for you to write it, and a senior dev even less time than that). You will hate it, it will suck having someone seem like they are just ripping your code apart, but it will make you so much better so much faster than just relying on your own internal knowledge.

When you start to be able to put the pieces together, stay humble. I've seen countless devs with a year of experience start to get a big head and talk like they know shit. Don't keep your mouth closed, but as a newer dev if you are talking noise instead of asking questions there is no way I will think you are ready to have the Jr./Associate/Whatever removed from your title.

Don't ever. Ever. Ever. Criticize someone else's preferred tools. Tooling is so far down the list of what makes a good programmer. This is another thing newer devs have a tendency to do, thinking that their tool chain is the only way to do it. Definitely recommend to people alternatives to check out. A senior dev using Notepad++, a terminal window, and a compiler from 1977 is probably better than you are with the newest shiniest IDE.

Don't be a dick about terminology/vocabulary. Different words mean different things to different people in different organizations. If what you call GNU/Linux somebody else just calls Linux, let it go man! You understand what they mean, and if you don't it's your job to figure out what they mean, not tell them the right way to say it.

One analogy I like to make is that becoming a programmer is a lot like becoming a chef. You don't become a chef by following recipes (i.e. just following tutorials and walk-throughs). You become a chef by learning about different ingredients, learning about different cooking techniques, learning about different styles of cuisine, and (this is the important part), learning how to put together ingredients, techniques, and cuisines in ways that no one has ever showed you about before.

Recently, I failed a lot. Most of them were interviews. Some failed at code challenge. Some of them were leet code type challenge. Some failed at less quality vs other people. Used to be ashamed or angry. Now able to embrace it. Thanks to jack ma's documentary. Start to integrated his philosophy into life.

When will Dev and Ops lay down their arms and embrace as brothers? This war has destroyed too many lives already.

I embrace the removal of the audio jack on smartphones, and I like listening to music via my Bluetooth headset.

Yet why, for fuck's sake, is a double tap on the headset's play button mapped to Call Redial?

I have lost count how often I called someone by mistake. How is such on action a meaningful default? What were they thinking, were they thinking at all?

Everytime I turn on the goddamn headset, I take extra care to ensure that I don't doubletap yet it still often happens by mistake.

I rarely call people anyways on my smartphone anyways.

Just came across this sentence in an oped... some strange times we live in. I still remember when I was getting into tech how everyone was afraid of Microsoft... but to be honest google & apple are doing more EEE than Microsoft so...

!RANT

Oh, the SORROW that is JEST! 😡

Endless days have been swallowed by the abyss in my quest to configure Jest with TypeScript and ECMAScript modules instead of CommonJS. Triumph seemed within my grasp until - BAM! - suddenly the tool forgets what "import" or "export" means. And the kicker? On the CI, it still runs like nothing’s amiss!

Allow me to elucidate for the uninitiated: Jest is supposed to be a testing safeguard, a protective barrier insulating devs from the errors of their peers, ensuring a smooth, uninterrupted coding experience.

But OH, how the tables have turned when the very shield becomes the sword, stabbing me with countless, infuriating errors birthed from Jest’s own design decisions!

The audacity to reinvent the whole module loading process just to facilitate module mocking is mind-boggling! Imagine constructing an entirely new ecosystem just to allow people to pretend modules are something they're not. This is not just overkill; it's a preposterous reinvention of a wheel that insists on being a pentagon!

Sure, if devs want to globally expose their variables, entwining everything in a static context, so be it. BUT, why should we, who walk the righteous path of dependency injection, be subjugated to this configured chaos?!

My blood boils as the jestering Jest thrusts upon me a fragile, perpetually breaking system, punishing ME for its determination to support whole module mocking! A technique, mind you, that I wouldn’t touch with a ten-foot pole, because, you know, DEPENDENCY INJECTION!

Where are the alternatives, you ask? Drowned in the abyss, it seems! Why can’t we embrace snapshots and all the delectable integrations WITHOUT being dragged through this module-mocking mire? Can’t module mocking just be a friendly sidekick, an OPTIONAL add-on, rather than the cruel dictator forcing its agenda upon our code?

Punish those clinging to their static contexts, their global variables – NOT those of us advocating for cleaner, more stable practices!

It’s high time we decouple the goodness of Jest from its built-in bad practices. Must we continue to dance with the devil to delight in the depth of Jest’s capabilities?

WHY, Jest, WHY?! 😭

Honestly, nothing.
I’ve had some bad experiences in my career so far, but I wouldn’t go back and change any of it.
I believe I am the engineer I am now because of all the experiences I have had.
Embrace your bad experiences and awful projects, because you gain a greater appreciation for the right way to build things when you’ve witnessed the wrong way first hand.

any mathematician turned devs here?

I think developers with a formal mathematical education should be the ones actually developing softwares. Ordinary developers are just good cooks who know to prepare these recipes by knowing to mix and manage the Ingredients through their experience, developing software using various libraries and frameworks, I don't understand what innovation we devs do in it, makes me feel less passionate about my work sometimes.

(I embrace the fact that being a developer requires an arstisic craftsmanship to do it properly)

"The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn’t have the same constraints, and design for this flexibility. But first, we must 'accept the ebb and flow of things.'" - John Allsopp

I love and embrace hurdles but I suppose getting people to understand and adhere to locked down requirements. I have seen lots of moving targets and scope creep impact projects and ultimately business success.

Does your bosses/managers also posting shit ton of pathetic buzzwords posts on LinkedIn (like: embrace, family, awesome organisation, very proud, guru, celebrating) and yet you know the organisation from inside and it's same corporate sh*t as everywhere else?

npm audit has gone wild since GitHub (aka Microsoft) acquisition, they surely found a way to influence the community.

Now, guys, embrace the creeping evil until deno is really out.

That feeling when you find the god damn bug after 2 hours.. however, it made me better understand my code, so thank you tiny bug❤

JFC people, if you can't understand why some people are losing their shit about MS acquiring GitHub, google "Embrace, Extend, Exterminate" and spend some time reading up about ALL the shady shit MS has done past.

I can't get over how absurd this is:

a = "123456"
a = int(a)

Is it just me or do you have to let go of everything you hold dear, embrace Satan, and sell your soul to be able to code in Python.

Currently moving all my projects and files up onto GitHub as I prepare to fully embrace Linux and not dual boot anymore as I have been doing for the past couple months. I'm so excited!

Not using all my time. I really don’t apply myself sometimes. Sometimes that means not using work time efficiently, sometimes that means I get stuck on a simple problem for too long because I don’t think through it. Also, I’m trying to love coding more. It takes a lot of code to get a small result sometimes, and that’s ok. I got hooked on being able to do big things with little code from the start. As we get better we know there’s more that can be done, but we are more familiar with just how much work it really is. At the same time we are more capable than ever of doing it. Just gotta embrace the suck, then love your finished product.

> As a developer in the Go world, I would recommend you to embrace idiomatic Go patterns and avoid dependency injection.

google literally created a DI lib for go.

The gap of data science in industry and academia is so large. As a data scientist in a large financial company, I see that people are still using traditional models such as linear regression and SVM, while people in academia keep inventing new concepts and techniques such as deep learning.

I am not saying that we should completely embrace deep learning, or stick to classic methods. But I just feel so surprised that the gap is so large...Sometimes I am even thinking whether I am doing the right "data science"...

* Ditch Java, Embrace Python
* Do my own thing
* Everest Base Camp
* Reduce monthly expenses, have some savings

Coding font of choice?

I want to use Inconsolata but the warm embrace of Menlo is too much to resist.

Oh, and maybe I should clear out some fonts...

Say what you will but React JS development is utterly exhausting. Every React project is a totally new stack and there is no consensus in the ecosystem.That is how I feel after having worked on 5 big SPA React JS projects over the course of 5 years.

The structure of these projects was all but similar: most used HOC's, some render props, functions-as-a-child, hooks or rather component lifecycles, some used container-components, some Redux, others sprinkled business logic & state all over, and yet others use a mix of server-side rendering and "hydration"...

I dangerouslySetInnerHTML on LazyExoticComponents, and dared not useEffect on the DO_NOT_TOUCH_OR_YOU_WILL_BE_FIRED root property. Hooks embrace functions, but without sacrificing the practical spirit of React, you see.

I didn't make this up. It's verbatim from the code and the docs.
This is not web development, this is at best a tedious fantasy multiplayer game or at worst, a costly joke.

I really hate double quotes because in my eyes they look awfully inelegant if compared to single quotes. Now that the Black formatter (Python) decided to use double quotes everywhere I feel very conflicted. I have always supported standards but I'm not sure I can embrace one that forces double quotes...

I'm working again with blue prism on a very very old SAP website. A hundred thousand nested iframes with a hundred thousand nested tables.

Please kill me, I long for the sweet embrace of death

When you embrace the TDD coding style, good things happen.

Trying to start a dev meetup with a friend, super excited but also nervous! I'm just a junior dev, absolutely overwhelmed by every aspect of the pool of knowledge available to me but absolutely excited to embrace it! I'm just a lowly angular developer but my aspirations are great :) I hope to bring people of unconventional ideologies together to discuss concepts in ways thay are... Well, unconventional!

Here's to learning, and growing!

"The Perils and Triumphs of Debugging: A Developer's Odyssey"

You know you're in for an adventurous coding session when you decide to dive headfirst into debugging. It's like setting sail on the tumultuous seas of code, not quite sure if you'll end up on the shores of success or stranded on the island of endless errors.

As a developer, I often find myself in this perilous predicament, armed with my trusty text editor and a cup of coffee, ready to conquer the bugs lurking in the shadows. The first line of code looks innocent enough, but little did I know that it was the calm before the storm.

The journey begins with that one cryptic error message that might as well be written in an ancient, forgotten language. It's a puzzle, a riddle, and a test of patience all rolled into one. You read it, re-read it, and then call over your colleague, hoping they possess the magical incantation to decipher it. Alas, they're just as clueless.

With each debugging attempt, you explore uncharted territories of your codebase, and every line feels like a step into the abyss. You question your life choices and wonder why you didn't become a chef instead. But then, as you unravel one issue, two more pop up like hydra heads. The sense of despair is palpable.

But, my fellow developers, there's a silver lining in this chaotic journey. The moment when you finally squash that bug is an unparalleled triumph. It's the victory music after a challenging boss fight, the "Eureka!" moment that echoes through the office, and the affirmation that, yes, you can tame this unruly beast we call code.

So, the next time you find yourself knee-deep in debugging hell, remember that you're not alone. We've all been there, and we've all emerged stronger, wiser, and maybe just a little crazier. Debugging is our odyssey, and every error is a dragon to be slain. Embrace the chaos, and may your code be ever bug-free!

Hello!. I have a little tech app idea I'll love to startup. I made an educated guess that my target users are mostly on the android platform. At least 70-80%.Now I don't have funds to get a development team and I want to keep the expenses to the barest minimum. I have a little tech background. I have, used html, css, c# in the past. I always hated Java in school. But it seems I have to embrace it or Kotlin for the development of the app. I want to be able to build at least the MVP and try to gain traction. I am also thinking about cross platform options to cater for both Android and the few iOS users we may have. React Native and Flutter comes to mind. I also think I can get someone highly technical than myself as a co-founder to help. I will appreciate it if you can drop your 2 cents.

I get really bad headaches whenever I stare at a screen too long, especially if it's too bright. I definitely chose the right career path.

Maybe I should just embrace my inner douchebag and start wearing sunglasses indoors.

So if universal apps are coming to macOS, does that mean we'll be able to use React Native and friends to create native desktop apps and ditch Electron and it's insatiable hunger for memory.
I mean that's cool, but why not just embrace PWA's?

So i got this advice from a acquaintance that's the head of some big company that deals with opensource.
"Stay away from .NET, it's the devil's doings"
Didn't quite know what to make of that, took my college degree in CS using java, got my first job with a java codetest and interview.. however I was so nervous I forgot to ask the tech questions about the job.
Anyway, just learnt that I'm now hired as a .NET developer (it's a trainee program so gets to learn it at work).

So, .net.. am I fucked or should I put my prejudices aside and embrace it as something good?

I am really tired of these tech religious fanatics. Hardly they worked on one real life project but love to preach clean code, oops , follow the coding specification blah blah. Keep your fucking mind open. If a programming language and pradigm is widely used then it doesn't mean you should embrace it blindly. For fuck sack.

I finally understand it. Its all about adaptability. The body and the subconsciouses mind is in a continuous adaptation to the environment it lives in. That explains why we always strive for new, better and cooler things, why we never are satisfied with what we have.

Be happy in the current position you are in, be grateful for simply living. It sounds like I'm on drugs or something, but we take such things for granted, appreciate and embrace what you have.

Open question:

Do you and your dev team openly embrace using a formatter for your projects, or do you not? And why?

My senior dev is trying to argue that it creates too much noise for commits, especially on older files and it's driving me nuts because I religiously use it (default TS formatter in VSCode btw, nothing crazy or super opinionated!)

Fuck thurston waffles, embrace Mr. Bubz

!rant
To embrace the TIFO (today I found out)
$git rebase -i <hash>^

You can reorder commits and squash.
I just used it, to amend a commit that was not HEAD with some changes I’ve done later.

"Embrace change or become a Design-O-Saur." - Von Glitschka

Hey ranters who once shared my inability to just announce when I don't understand something, how did you get over it and just embrace pointing out that you're confused at this point in time?
I tend to just brush stuff off and figure I'll have time to properly investigate and figure it out later, which usually works, but it does mean I will keep quiet if something isn't entirely clear.
I think this is bad and I'd to stop doing it. At the same time, it doesn't seem worth interrupting a discussion / explaining to ask what something is when I can look it up now or later and fill in the mental gap. I guess there's a balance to be found. Any tips? Any slaps to the face?

Irony
Even the black folks when faced with the problem.of wanting a better life for themselves apparently embraced the mindset of the fucking confederacy in a scenario where the untenable system or seemingly so of economics we embrace as a globe turned out not to work
They just tried to make more people like they were to keep themselves better off

Pig In a suit sort of deal

So how does an experienced programmer break his own code in a such a terrible manner.

And why would someone try to make me embrace a bogus thing I KNOW doesn't work to make sure its broken ?
See this is what I hate about this shit.

No programmer would make the mistake that was made. They converted all their classes that interpret STRING VALUES using a parse to BitConverter.

(The input is a byte array) for like, ALL THEIR CLASSES.

Again this seems fucking intentional.
Instead of letting it remain a goddamn class that handed around an open file stream with a binaryreader around it which was simple, they tried some fucking fancy shit and throw readonlyspan<byte> at a read method which is where the code WILL fuck up ! wtf is wrong with you fucking dumb bastards ? IF YOU DONT WANT THE CHOMS GETTING AHEAD SHOOT THEM JESUS CHRIST !

Maybe this is some special interests shit to make sure ArcGis remains the dominant gis package and no ordinary lowly programmer can have a reader to get started with their own manipulations.

YOu fucking bastards screwed up the world and i want to eat your fucking hearts from your chests and wear your fucking scalps and ears on a fucking necklace while burning down your fucking houses !

AND FIX THAT GODDAMN STEAM RELEASE VALVE !!!

Dear Thieves.
So I was looking at some guy who's job I designed today.
He was sitting there with the new laptop I bought during one visit here.
It was an hp with a silver keyboard and handrest because supposedly normal people stopped owning laptops when you all decided to embrace schizophrenia and create inane rather stupid meanings that are associated with literally everything but sense or sophistication.

comparing oneself to an animal for example doesn't focus on positive or spiritual values, its something perverse.

ordering food is not about enjoying new things or savoring flavors, its about something perverse.

going to school is not to learn things, its to crash and burn later because the powers that be refuse to update the system from the 1970s.

living, is not living at all, but working to pay bills and get old bitter and fat.

well.

shit.

retards.

anyway. doesn't explain people like myself who made things when we could and were enthusiastic about our jobs at points.

oh. and supposedly the guy who stole the job was 'I".... and it was a job that would become 'outmoded'......
i believe that was the word often used. let;s check. yup, close enough.

then all these people talking about 'new' jobs because noone could trust the group of monsters they made with too much spare time. since you know. they thought it was funny to steal human beings lives since they were not human. subhuman.

anyway.

where suddenly everything meant something else and a whole new world of retarded people emerged from the shadows because the trash children of a former generation got sick of being lectured about morality when they were in fact just bad people who should have been shot.

i don't care how else the whiney bastards explain themselves. i really don't.

you can say that in desperate fucked situations involving psychological torture, rape, etc that a decent person *raises their hand* might do TERRIBLE things to their captors in order to escape, but THEY caused that while whining that someone from the 1940s or earlier made them evil and they had no choice but to steal jobs, money, retirement funds, public institutions, the morals of a generation, i'll bite: toddlers, spread their legs like psycho whores to get pregnant, so steal people's unborn children, turn every fund available that could have gone towards people that needed things to money laundering and in general gleefully fucked our whole country up with the lack of foresight that psychopaths commonly display.

great job.
was it worth dying ?

how about going crazy and letting another group of evil people make an excuse to drive everyone into an endless idiotic loop ?

but hey no, keep lying. works so well.
well at least fedora 37 is released again.

give the stolen photos back.
just want to know what i looked like, and don't want to talk like a retard to get people who understand english to pretend they finally comprehend.

fucking bastards.

Don't be afraid to tackle error messages actually embrace them because you learn more from your error messages.

Angel number 811 and its spiritual meaning you should know.

Do you find yourself waking up at 8:11 AM or PM every day? Well, you're not alone! This recurring number sequence is actually an angel number that holds a powerful spiritual meaning.

The angel number 811 spiritual meaning is all about new beginnings and positive transformations. It's a sign from the universe that you are on the right path towards your life's purpose and that you should have faith in your journey. This number sequence is a message from your angels that you are being guided towards a new chapter in your life, one that will bring you joy, abundance, and fulfillment.

The number 8 in angel number 811 represents abundance and prosperity, while the number 1 symbolizes new beginnings and leadership. Together, these numbers create a powerful combination that signifies that you have the power to manifest your dreams and achieve success in all areas of your life.

If you keep seeing the angel number 811, pay attention to the signs around you. Your angels are trying to communicate with you and guide you towards your highest good. Take time to reflect on your current path and make any necessary changes to align with your true purpose. Trust that the universe has a plan for you and that everything is working out for your highest good.

In conclusion, the angel number 811 spiritual meaning is all about new beginnings, positive transformations, and abundance. It's a powerful message from your angels that you are on the right path towards your life's purpose and that you should have faith in your journey. So, embrace this powerful number sequence and trust that the universe has a plan for you.