As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

Lads, I will be real with you: some of you show absolute contempt to the actual academic study of the field.

In a previous rant from another ranter it was thrown up and about the question for finding a binary search implementation.

Asking a senior in the field of software engineering and computer science such question should be a simple answer, specifically depending on the type of job application in question. Specially if you are applying as a SENIOR.

I am tired of this strange self-learner mentality that those that have a degree or a deep grasp of these fundamental concepts are somewhat beneath you because you learned to push out a website using the New Boston tutorials on youtube. FOR every field THAT MATTERS a license or degree is hold in high regards.
"Oh I didn't go to school, shit is for suckers, but I learned how to chop people up and kinda fix it from some tutorials on youtube" <---- try that for a medical position.

"Nah it's cool, I can fix your breaks, learned how to do it by reading blogs on the internet" <--- maintenance shop

"Sure can write the controller processing code for that boing plane! Just got done with a low level tutorial on some websites! what can go wrong!"

(The same goes for military devices which in the past have actually killed mfkers in the U.S)

Just recently a series of people were sent to jail because of a bug in software. Industries NEED to make sure a mfker has aaaall of the bells and whistles needed for running and creating software.

During my masters degree, it fucking FASCINATED me how many mfkers were absolutely completely NEW to the concept of testing code, some of them with years in the field.

And I know what you are thinking "fuck you, I am fucking awesome" <--- I AM SURE YOU BLOODY WELL ARE but we live in a planet with billions of people and millions of them have fallen through the cracks into software related positions as well as complete degrees, the degree at LEAST has a SPECTACULAR barrier of entry during that intro to Algos and DS that a lot of bitches fail.

NOTE: NOT knowing the ABSTRACTIONS over the tools that we use WILL eventually bite you in the ASS because you do not fucking KNOW how these are implemented internally.

Why do you think compiler designers, kernel designers and embedded developers make the BANK they made? Because they don't know memory efficient ways of deploying a product with minimal overhead without proper data structures and algorithmic thinking? NOT EVERYTHING IS SHITTY WEB DEVELOPMENT

SO, if a mfker talks shit about a so called SENIOR for not knowing that the first mamase mamasa bloody simple as shit algorithm THROWN at you in the first 10 pages of an algo and ds book, then y'all should be offended at the mkfer saying that he is a SENIOR, because these SENIORS are the same mfkers that try to at one point in time teach other people.
These SENIORS are the same mfkers that left me a FUCKING HORRIBLE AND USELESS MESS OF SPAGHETTI CODE

Specially to most PHP developers (my main area) y'all would have been well motherfucking served in learning how not to forLoop the fuck out of tables consisting of over 50k interconnected records, WHAT THE FUCK

"LeaRniNG tHiS iS noT neeDed!!" yes IT fucking IS

being able to code a binary search (in that example) from scratch lets me know fucking EXACTLY how well your thought process is when facing a hard challenge, knowing the basemotherfucking case of a LinkedList will damn well make you understand WHAT is going on with your abstractions as to not fucking violate memory constraints, this-shit-is-important.

So, will your royal majesties at least for the sake of completeness look into a couple of very well made youtube or book tutorials concerning the topic?

You can code an entire website, fine as shit, you will get tested by my ass in terms of security and best practices, run these questions now, and it very motherfucking well be as efficient as I think it should be(I HIRE, NOT YOU, or your fucking blog posts concerning how much MY degree was not needed, oh and btw, MY degree is what made sure I was able to make SUCH decissions)

This will make a loooooooot of mfkers salty, don't worry, I will still accept you as an interview candidate, but if you think you are good enough without a degree, or better than me (has happened, told that to my face by a candidate) then get fucking ready to receive a question concerning: BASIC FUCKING COMPUTER SCIENCE TOPICS

* gays away into the night

There’s a fundamental difference between development and other jobs.

Doctor: Hey! My left arm is hurting and has been swollen for a while, I think it might be sprained. *pays $100*

Taxi Driver: Hey! Can you ride me over to this exact address? Thanks. *pays $20 + tip*

Construction Worker: I’m going to need this exact item in the blueprint built here with these materials. *pays $1000*

Mechanic: This part of my car isn’t working correct and it displays this exact warning. *pays $100*

Developer: Yo I need a cool free website that looks pretty awesome with like rainbows and stuff by tomorrow.

It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

Basically,
1+infinity = 1
But
infinity + 1 = NaN
My entire maths fundamental shuttered by the beautiful JS language....

Most of the tech YouTubers are really noob engineers.

Joma was a data scientist. He is an L3 engineer at Google and he hasn't done much during the last 1 year based on his internal stats.

I saw tech leads stats while he was at Google and that dude did nothing during his time. I'm sure he was an IC before he became a lead.

Clement talks about system design bull shit but he's a math major who worked on some angular front end while he was at Google. Basically his experience in tech is mostly involving using mat-button and mat-input. He also quit FB in a month.

Listening to tech lead gives me cancer. That guy was also some front end/ mobile engineer. I don't think any less of mobile engineers but tech leads acts as if he built some large scale systems at Google and FB. His opinion about react native shows how much of a noob he is. He also talked about docker in one of his video which showed he had some fundamental misunderstanding of what docker is. In his courses, he struggles to explain simple algorithms.

I don't know how these people have the courage to claim themselves as some sort of experts in the field when they are extreme noobs. They also sell some shady courses and are robbing innocent college kids.

One thing they all do well is talk. Which I give them 10/10.

"There’s a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. […] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It’s harder to read code than to write it." - Joel Spolsky

If you are in a job interview with the dev manager of java and the other dev manager of C++ and a fundamental discussion starts:

Resumes don't mean jack shit!!

I just got off an interview call with a candidate for a hardware role. On paper this guy is absolute gold, having worked for some of the best robotics companies and research groups(in India at least) It took me an hour to realize that the was just spitting out buzz words. So I started asking him some very fundamental questions, like ohms law and such.. high school stuff. But, phrased in real world terms. And it took me another half an hour to realize that the guy is dumber than a sack of peanuts!

I can't believe how easy it is for people to coast by on paths paved by seniors and teammates. By any objective assessment this guy would be lucky to get a job as an electrician and instead I'm wasting my time interviewing him for a six figure salary (well, the Indian equivalent). Gaaah!!

One of the biggest reality checks you will run into when starting your first dev related job - and which they don't teach you about in school - is that a lot of the time will be spent working with other people's code, and rewriting it into "your own" is rarely an option.

You might be super into making things, but not everyone manages to maintain that same spark while taking over a 15 year old project with fundamental issues that have to be triaged "for now" because you need a hotfix on this other specific thing out in prod before lunch.

There are no gods now. They left the company years ago and nobody knows why they used the windows registry as a user repo.

Follow up to yesterday’s “hybrid/cross-platform is shit” rant about Electron apps being blocked from the Apple App Store.

See the below image of the github issues template on the Electron repo, to file an issue for this problem.

Yes, this is such a common issue with their product, they’ve made it easier to file a github issue. Let’s not address the fact that there is a fundamental flaw in the approach they are using, let’s just make it easier to open a ticket while everyone waits to see if we are allowed to ship our app.

I’ve also heard talk that under some circumstances it’s possible for them to patch out the libraries causing issues. Apple provides tools to identify these libraries ... therefore Electron is doing fuck all to adresss this issue, and adopting a “wait until someone complains” style of approach.

A+

One of the biggest things that grinds me gears is when I'm tutoring CS at my school as a student tutor is that I get those students who obviously aren't studying or even trying, in fact hoping their tutor will tell them exactly what to type to get that A in the class.

Me: "OK so here's the idea of..." *explains the idea on what they need to accomplish in a more simplistic, visual idea*

Student': *blank stares*

Me: *Blank stares back, thinking of how to make it simpler...*

I then explain I in even more layman terms till they get through their head I'm not going to tell them what to do. I'll guide, but I won't tell what to do.

Please don't waste my time, or I'll waste your time explaing the very fundamental basics of how a variable works instead of helping with your homework.

5 Fundamental qualities of good programmers....

I understand now! I keep getting ++ on rants I wrote forever ago, and I finally understand the formula to become devrant famous:

1. Pick something that is mildly annoying and at least mildly tech related. For best reception, it should be something widespread, uncustomizable (and or difficult to customize so nobody does), and just mildly annoying so it's not too over played.

2. Post a long form rant, using almost the entire character limit to make this one, insignificant annoyance into a much bigger issue than it is. This is how the mainstream media does it, this is what the people want!!!!!

3. Somehow find a way to shift the blame onto one of the following groups: Microsoft, apple, arch, arch fanboys, arch haters, users, management, the fundamental laws of physics that allow computers to function, or in a worst case scenario start a flamewar (emacs sucks; arch is the best operating system; micro$hit; it's just Linux, if they wanted to call an OS GNU, they would finish fucking Hurd; etc. It's almost too easy)

4. Sit back and wait. You're now internet famous in a tiny portion of the internet. Congratulations. You've made it.

So I never had a proper education in IT. Started web development as a hobby, then some people started giving me money for it, and here I am, working as a fulltime web dev since 2001 and SEO expert since 2010.

Still, I sometimes wonder how much I really know compared to some fresh coder who just got out of university.

I know how to create great software from A to Z, but still I sometimes get the feeling that I am missing the fundamental basics.

Is that weird?

Hired a new BI developer. She tested reasonably ok in SQL, and certainly showed good strengths in visualising data, plus had a good attitude in the interview. We hired her. She broke her laptop the first day. We got her another then she complained the camera didn't work but didn't realise the lever in front of the camera was to move the privacy shutter off and on.

Assigned her some work of taking queries that are used in a BI tool that targets the transactional database directly, and re-jigging them for Snowflake which we're using as a data warehouse now, aggregating all our data into one place. Yet, she's struggling to understand why the SQL query she's pasted in doesn't work as-is.

I go over it again; the source schemas and tables are this, but in Snowflake we've named them this. She then bemoans how much work that is to change them all - I say use find and replace. She then struggles with Snowflake syntax errors and asks for a guide on T-SQL to Snowflake. I show her Google and say "this is what I did when I hit these problems - search for 'Snowflake equivalent to T-SQL getdate()' or 'how to get current date in Snowflake' but she still doesn't understand. I ask if she's every had to work between T-SQL and MySQL or MySQL and PostgreSQL or Oracle and so on and she says yes. I say the syntax isn't the same, is it? And she goes oh, now I understand.

She scored reasonably in her SQL test but I'm now concerned there's something fundamental missing in her grasp of SQL. I gave her a detailed demo of the tools, I explained in the interview and on her start about our move to a data warehouse for all our apps, and put her through some training plus gave her time to work through our Confluence pages - not expecting she'll remember everything, but more to ensure she recalls they exist and what the general contents are.

Anyhow, that's my rant.

I'm so fucking done with net neutrality. the only ones who want it are verion, comcast, and other big isps.

fuck them.

this is fucking merica. nobody wants it, and this is a government designed for the people. I guess it only works in theory.

the talk about this has been fucking exhausting. how much clearer could it be?

how does it keep coming up? so much of the economy is online. why would congress want this? this should be a fucking fundamental right. no bs, just fast speeds everywhere. i hate all the isps thinking that because the world is so reliant on the internet, they control everything.

isps are a service. that's it.

they're not a profiler or advertiser, just a service.

and if that changes, I'll buy a bunch of flash drives and go offline.

bottom line, we should have privacy, neutrality, and a safe web. fuck those greedy bastards.

In `Computer Fundamental` class

friend: What 1 + 1 equal to?
me: two.
friend: ...no, it's equal to ten.
me: oh fuck!

Years ago, we were setting up an architecture where we fetch certain data as-is and throw it in CosmosDb. Then we run a daily background job to aggregate and store it as structured data.
The problem is the volume. The calculation step is so intense that it will bring down the host machine, and the insert step will bring down the database in a manner where it takes 30 min or more to become accessible again.

Accommodating for this would need a fundamental change in our setup. Maybe rewriting the queries, data structure, containerizing it for auto scaling, whatever. Back then, this wasn't on the table due to time constraints and, nobody wanted to be the person to open that Pandora's box of turning things upside down when it "basically works".

So the hotfix was to do a 1 second threadsleep for every iteration where needed. It makes the job take upwards of 12 hours where - if the system could endure it - it would normally take a couple minutes.

The solution has grown around this behavior ever since, making it even harder to properly fix now. Whenever there is a new team member there is this ritual of explaining this behavior to them, then discussing solutions until they realize how big of a change it would be, and concluding that it needs to be done, but...

not right now.

Development world is always changing and evolving... It changes before you know it...

So, having the ability to quickly adapt and learn is a must for any Developer... And, this is the one thing that I am sure that everyone knows about or heard about..

But, my advice is quite simple:

"Don't rush into participating in a race, just because everyone else is doing so.

The trick is not to move quickly.. But, to move one step at a time, at the pace in which you are at your most comfortable...

It might seem counterintuitive and a contradiction to what I have said earlier.. But, I hope that by the end of this rant, you will be able to understand my perspective..

This advice is especially useful for people still finding and searching for their place in our world..

Charles Darwin, very wisely understood the philosophy behind 'Survival of the Fittest'..

By 'fittest', he didn't refer to the ones considered to be the strongest or having the most intelligence, but the ones that had mastered the ability to adapt to changing circumstances..

Adaptability is important, but not at the cost of understanding and learning about the fundamental pillars on which this world stands..

Don't rush because when you run, your visions starts to become more narrow.. In your pursuit to reach your goal, you lose the ability to look at the macro details surrounding your goal..

Learning new technology is important, but that doesn't mean that you don't learn about various approaches or how to design a more logical or efficient solution...

Refactoring the code, developing good Testing procedures, learning to interact with your fellow developers are as crucial as learning about the changing trends...

Even, in this ever-changing world, understand that some things will always remain the same, like the adrenaline that course through your veins when you finally solve a long-standing problem...

Curiosity, Discovery and Exploration are the key pillars and hence, when we rush in, we might stop exploring and lose curiosity to discover new and exciting ways to reach our goal..

Or, we might also end up losing the drive that grips us and motivates to continue moving forward inspite of the challenges standing between us and our destination..

And, believe me, once you lose this quality, you might still succeed but the contentment and the satisfaction that you feel will be lost..

And, then, you will remain a developer only through your designation... And, that in my personal opinion, the worst punishment.

need advice on integrating .t3d file support in c++ engine
hey, been stuck trying to figure out how to get .t3d file support working in our custom game engine, which is all written in c++. it's turning out to be a lot trickier than expected and i'm kinda hitting a wall here. the documentation on .t3d itself is pretty much nonexistent and what's out there is either outdated or too vague to be of any real use. i've tried a few things based on general file parsing logic in c++ but keep running into issues with either reading the files correctly or integrating the data into the engine in a way that actually works. it feels like i'm missing something fundamental but can't pin down what it is. has anyone here gone through this process before or has any experience with .t3d files? i could really use some advice on how to approach this, or even just some resources that explain the format in detail. also, if there are any common pitfalls or things to watch out for when adding new file format support to a game engine, i'd appreciate the heads up. thanks in advance for any help, feeling pretty stuck and any guidance would be a huge help.

If you're as bad at web design as me, I recommend tailwind css to you.

I've been using it today and had a good time.

By providing a set of design-centric classes, it makes it easy to learn and apply good design practices without losing css control.

This is paramount to me since I know a couple of css tricks, but not too many. With this you can't miss any of the fundamental ones.

It also lets you combine multiple classes into one via the @apply directive, so the html classes don't go crazy, and you don't have to write too much css. Huge amount of lines saved.

To top it off, they have plenty screenscasts that not only teach you how to use tailwindcss, they show you fundamentals good web design.

"Minor edit"?
Why do clients always have to try and quantify the amount of effort a task is going to take while having no clue as the actual work it is going to take?
MINOR EDIT!
I bet to them changing a fundamental law of the universe would be a "minor edit"

I know there are different ways of learning programming, but I see students actually taking notes from a programming books and highlighting important bits with a Pilot marker. (and they're not reading fundamental stuff)

Just fucking code something.

Alright. This is going to be long and incoherent, so buckle up. This is how I lost my motivation to program or to do anything really.

Japan is apparently experiencing a shortage of skilled IT workers. They are conducting standardized IT skill tests in 7 Asian countries including mine. Very few people apply and fewer actually pass the exam. There are exams of different levels that gives you better roles in the IT industry as you pass them. For example, the level 2 or IT Fundamental Engineering Exam makes you an IT worker, level 3 = capable of working on your own...so on.
I passed level 1 and came in 3rd in my country (there were only 78 examinees lol). Level 2 had 2 parts. The theoretical mcq type exam in the morning and the programming mcq in the afternoon. They questions describe a scenario/problem, gives you code that solves it with some parts blanked out.

I passed the morning exam and not the afternoon. As a programmer I thought I'd be good at the afternoon exam as it involves actual code. Anyway, they give you 2 more chances to pass the afternoon exam, failing that, you'll have to take both of them the next time. Someone who has passed 1 part is called a half-passer and I was one.

A local company funded by both JICA and my government does the selection and training for the Japanese companies. To get in you have to pass a written exam(write code/pseudocode on paper) and pass the final interview in which there are 2 parts - technical interview and general interview.

I went as far as the interview. Didn't do too good in the technical interview. They asked me how would I find the lightest ball from 8 identical balls using a balance only twice. You guys probably already know the solution. I don't have much theoritical knowledge. I know how to write code and solve problems but don't know formal name of the problem or the algorithm.

On to the next interview. I see 2 Japanese interviewers and immediately blurt out konichiwa! The find it funny. Asked me about my education. Say they are very impressed that self taught and working. The local HR guy is not impressed. Asks me why I left university and why never tried again. Goes on about how the dean is his friend and universites are cheap. foryou.jpg

The real part. So they tell me that Japanese companies pay 250000/month, I will have to pay 60% income tax, pay for my own accommodation, food, transportation cost etc. Hella sweet deal. Living in Japan! But I couldn't get in because the visa is only given to engineers. Btw I'm not looking to invade Japan spread my shitskin seed and white genocide the japs. Just wanted to live in another country for a while and learn stuff from them.

I'll admit I am a little salty and probably will remain salty forever. But this made me lose all interest in programming. It's like I don't belong. A dropout like me should be doing something lowly. Maybe I should sell drugs or be a pimp or something.

But sometimes I get this short lived urge to make something brilliant and show them that people like me are capable of doing good things. Fuck, do I have daddy issues?

I can agree to shit when presented with hardcore data, data that proves me otherwise. But when people go by opinions and then hold is a truth because of "many feel the same way" I cannot help but to giggle a bit.

Most issues I have found with programming stacks come from opinions rather than hard presented data, if a bunch of people dislike a tool, but it delivers, I get to differ two things: (1) it is bad but it performs as needed, but it is bad because of design problems etc, (2) some dude made a post concerning why he things is bad and sheep mentality follows.

If technologies were without merit, then we would have all discarded C++ a long time ago cuz Linus disliked it, a powerful programmer indeed, but a FOCUSED one, meaning, one that deals with 1 domain (kernel development)

Do I care about what Linus things about web development? No, lol, he is a better kernel developer than I am, but I highly, grossly doubt that he knows enough about web development to give me something to think about.

all languages have faults, regardless of what point of view we look at them, but completely disregarding a tech stack because of shit that you saw some fucktard wrote about, benefits and otherwise, just seems....well...sheepish, there might very well be a tech stack out there that covers everything, to me it is a mixture of things, and I use them as I please and feel like, but this is because after years of learning I have read about quirks and pitfalls and how to avoid them. I would suggest you all do the same, by you all I mean those of high opinions that can't be deflected.

This field is far too wide and concentrated to go head and think about absolutes when even the fundamental mathematical theory concerning computer science is not absolute whatsoever, it is akin to magic, shit works, but it might not, the incantation might be right, but circuits and electricity have a way of telling us to go fuck ourselves, so do architectures, specifically ones based on physics.

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

Tester raises major "bug" about fundamental part of the system 1 week before sign-off....
What was it you ask?
"This field is validating my input and is showing an error"...
Me: "But sir, you have pasted text into a number input!"

I want to thank all open source projects and their collaborators.

I want to thank communities such as stack overflow and specialized forums where people make time to help others.

Lastly, I want to thank everybody here by sharing their experiences and making one feeling less alone (or less weird).

I don’t know of any other community aside from devs where they help so much between themselves. I think this is one of the few professions were collaboration is a fundamental part of it.

Thanks.

So I realized:

No matter what terms we replace master/space with, it still implies one is better that the other, or in charge of the other.

This isn't equal! I demand process rights! So I say we make a deeper change! We change the fundamental way concurrency works in python so that all forks are equal! In fact forks are divisive. We should do away with that too.

Make python single threaded again.

When I think "the fundamental problem", the closest thing that comes to my mind is "unsolvable problem". P =/!= NP is a fundamental problem, the theory of everything is a fundamental problem.

But we actually solved at least one such problem – the fundamental problem of cryptography.

The problem was "how to establish a secure connection over a non-secure channel?" Like you can't exchange the key, it'll be exposed by definition.

We solved it with a simple yet brilliant solution of asymmetrical cypher, that thing with public and private keys.

It's fascinating to think that people died in WW2 over this, there were special operations to deliver fresh deciphering keys securely and now SSH and HTTPS are no-brainers that literally everyone use.

I'm studying Computer Science and Engineering in Uni.

People don't understand the most fundamental principles of programming at all. Variables and functions are like a foreign language to them.

I get that not everyone knows everything but if you decide to go to uni to study programming, and you have never programmed before. Are you really in the right place?

So, I'm still not certain if it's actually a bug or merely my lack of experience, but I've been working on a 2D platformer game (using only C++ and SDL2) for roughly 2 years now (on and off; sometimes off for months) and I'm extremely embarrassed about this, but for the life of me, I cannot seem to get the player character's movement and collision physics working properly. It's driving me absolutely insane.

I've read articles and tutorials, referenced books, and posted about it in game development communities (e.g., gamedev.com, Discord servers, etc.), but even though the fundamental structure and explanations made sense, getting the code to work has been unsuccessful, albeit not completely so, but if I get one thing working, another thing breaks. It feels like I'm trying to repair a vase that fell off of a skyscraper and turned to dust on the street below.

I've always been a very tech savvy person with a fiery passion for programming, electronics and game/software/embedded/web development, but to be honest, having such a difficult time with things like this that — in theory, at least — seem like trivial bumps in the road have made me feel like I'm never going to be successful in this field. But regardless of the depressing thoughts of worthlessness, my passion doesn't let me stop trying. Who knows, maybe it'll have to remain just a hobby. 😕

Today.

Client: “can you make this last minute change to something fundamental?” (Paraphrased)

Me: “yes it’s doable but a major pain in the ass at this late stage”

Client: “great! Well if it’s just a quick change sit tight in it just now and i’ll let you know tomorrow if it’s to go ahead”

Me: “is this real life?”

I'm bored af working on crappy php56 legacy apps written by short sighted programmers, makes my life miserable, but the pay is pretty good for a remote job which is pretty rare in here. Meanwhile I'm interested on exploring fundamental stuff on computer science and experimenting new techs.

I'm thinking about doing a PhD but too afraid if I can't finish it or the future opportunity isn't good enough since I live in 3rd world country in southeast asia. Also it probably takes ±8 years to finish it including the preparation.

I have no question, but it would be great if you have some advice.

Project Managers will ask six figures salaries to whip an entire team of developers because it's fundamental to add AI to a fucking toilet by the end of the week, then walk around like they understood everything about life. Given how that's what they do for a living and we're not currently gunning them down on sight, I can't say they're entirely wrong.

I might create a coding course for people actually interested in learning how to program correctly (not Get Rich Quick Bootcamp style, not webapps, not magic Javascript incantations).

I have an idea on how to structure it but I worry it'll be too weird for most people to follow (starting from binary theory and then teaching machine code and then working upwards to C and beyond) explaining how a computer works along the way, showing the real errors with annotations explaining things, etc.

I've always wanted to teach in this format but I feel as though it's too.. idk, "useless" to most people? But I've never had a friend go through e.g. CodeAcademy and come out knowing how to actually make applications from start to finish without just hacking together random React components and hoping the frankenstein project works well enough.

The target demographic would be those either completely new to programming or just have a fundamental or web-centric preexisting knowledge, or maybe those who simply want to understand computers better.

Am I barking up a shitty tree?

Obligatory subjective view from inexperienced eyes of a highschooler

I think it's evolving to be more beginner-friendly and more easily accessible. I'm seeing ppl roughly my age can program pretty well (ignoring the mandatory programming classes in highschool that stuff is just no (I know, we had this convo before but do hear me out, although it teaches fundamental programming in Pascal, the execution sucks ball because "mandatory")). I'm not saying we are on par with the in-industry devs, it's just we can code well enough to at least make decent small program/script.

With newer scripting languages that are easy to pick up and syntactically similar to English which is obviously Python, both objectively and subjectively, and its ability to be OOP without scaring first-timers of the what-the-blyn-is-this blank program (looking at you C#) people can be introduced to programming and programming concepts fairly easily and they can switch from Py to other languages with little to some hiccups, from my personal exp at least.

But then there's the "too much kiddies in the field" arguments I saw on dR (I think) a while back then when SO decided to better support newbies. To that, I can only say "Please give us a chance". We're completely oblivious to how the dev world work nor how you guys do your work so before you scold us on this, at least tell us how to work like you before you go on a 2-A4-page rant on how the industry is not as good as before and how it has degraded.

That leads to the problems of politics invading programming. We have it, I hate it, goddammit I wanna murder them. Linux CoC controversy is just...no. And then there's forced diversity in hiring (also ranted on dR a while back) and corporations pissing devs off to satisfy a minor group. I'll just shut up on this. No no no no no no no NO I'm not gonna. Not gonna.

Do correct me if I'm wrong though. I'm a less than a junior dev.

I lost a client today 😞.
One of the fundamental reasons freelance sucks major balls.

Hello everyone.
So, i am thinking about where to get lists of programming languages, frameworks and softwares that is fundamental. For example:
If i would like to develop a web site. I would use html, css, js & php. Maybe a site or frameworks for reference and 'roadmap'. I want to become a good programmer.

Hello and welcome, to a presentation in which I will tell you my thoughts on the shortcomings of modern day computers and programming practices.

Computers are based on a very fundamental and old idea, folders, and files, a file is basically a concrete amount of data, whereas a folder is a group of files, and it comes from the real life concept of files and folders, now it might be quite obvious already that using a concept invented in 1898 by a guy called Edwin G. Seibels, might not be the best way for computers to function in the year 2020, but alas, it is.

Unless of course, you step into the world of a programmer.

A programmer’s world is much different, they use this idea of a data structure, or in simpler terms, an object. An Object is just like what you would think of as an object in your head, something with different properties that you can think about in different ways, for example your mobile phone, it has a battery percentage, it has a screen size, it has free space available. Programmers use these data structures to analyse data very quickly, like finding all phones with a screen size bigger than a certain size for example.

The problem is that programmers still use files and folders to create the programs that use these objects.

Consider this example.

Let’s say you want to create a virtual version of a drink bottle, consider what properties it will have, colour, volume, height, width, depth, material, etc..

As a programmer, you can leverage programming features and change the properties of a drink bottle directly, if you wanted to change the colour, you just say, drink bottle “dot” colour, equals blue, or red.

But if the drink bottle was represented as a file, all the drink bottles data would be inside the one file, so you would have to open the whole file, find the line or section of the file that has the colour data of the drink bottle, and select it, highlight it, delete what’s there, and type in your new value.

One way to explain this better is to imagine a folder that now represents the drink bottle, imagine adding a new file into that folder that represents each property I described before, colour, volume, etc.., well now, you could just open that folder, find the file for colour, either by looking with your eyes or you could do a file search in the folder for a file called colour, open it, and edit the value inside. This way of editing objects is the one that more closely represents the way programmers and a program itself interacts with objects inside a running programming language.

But the thing is, programmers don’t use the folder/file way of creating objects and putting them into programs, because it would be too cumbersome, they just create 1 file for an object, or have lots of objects in a file, and create all the objects in 1 file, and then run the program which creates the objects, then when they stop the program, it deletes the objects. So there is no actual link between the object in a file and the object that the program creates by reading the data from that file, if you change the object in your program, it does not get saved to the file.

So programmers created databases to house these objects, but there is still a flaw in databases, they are hard to interface with, and mostly databases are just used to send data or retrieve data from, programmatically, you can’t really browse a database the way you can browse the files on your computer. You can, but database interfaces are not made to be easily navigated the way files and folders are.

As it stands, there is no way to store objects instead of files on your computer and interact with them in complex ways the way programmers can inside the programs they create.

If the idea of an object became standard the way a file and folder is standard, I think it would empower human’s a great deal to express things far more easily and fluidly than they can today.

Thanks for reading.

CSS is utterly retarded but I can’t help but be impressed by how well the DOM still works in this day and age. The fundamental structure hasn’t changed since the 90s.

My coding style is extremely fundamental (I guess); meaning I have to write every piece of code myself and I don't like to use anything ready, which makes me very slow and costs the employer lots of money and time.
It's becoming very discouraging, but I just can't give it up!
Any ideas how to improve this situation?

One of biggest epiphanies came through this fundamental critique in SICP of the assignment operator. Through years of imperative programming it seems so innocent, doesn't it? But that you lose referential transparency, run into the alias problem and fundamental difficulty to determine object equality (or of their instances) - that was kind of eye opening considering all the pain I had already experienced with state in concurrency.
(It led me so far to think it's an ontological issue, that even in the discrete computing universe we have not come so much further than Zenon's paradoxa on change.)

Sometimes you want to scream but you can't,
sometimes you want speak about how fucked up this society that we live in is... how the fundamental concepts of our lifes are wrong... How some things just don't work in the present... but there is no one who would listen to you... and even if they did, there is nothing they can do to change anything until the whole world listens.

Had a customer today that claimed that crontab did not work as it should, and he has proof of that (in form of some very abstract logs).

Well, I guess noone can rely on one of the most fundamental binary in the unix world.

Computer science vs software engineering?

Software engineering is all about people. You have to communicate with the business, realizing their needs, figuring out their processes, optimizing them, all this before the first line of code is written. Then, you have to manage your direct reports, and if you have none, write code with people in mind, people who will read it after you. As they say, code is for people, not for computers. Then, you have to improve the app listening to users, again, people.

I can’t assign a software engineer a role higher than middle if they’re bad with people.

If you wanna do cool stuff with computers and be a misanthrope, do computer science! It’s a very prestigious field where you are left alone with scary math and fundamental concepts. If you’re successful there, you’ll have a mad asocial scientist card, and no one will ever insist to you that people is important. They will just accept that they shouldn’t annoy you, and you are “allowed” to yell at them because you’re “special” and a “genius”. You can hate them 24/7.

I wrote a tech book several years ago for O'Reilly, which itself was a dream come true. I'm still amazed I got that deal done, and the fact that my name was on a title with a unique animal on the cover is SUPER cool.

Back then, their publishing system was based on Git with their own markup language, and it was sort of a chore to use. Easy and straightforward, but laborious. I spent 3 entire days just (re)formatting my drafts to their code. They've upgraded it since, I see, based on the same fundamental versioning idea and still using Git. Neat!

I've also done tech writing for .NET Magazine, which used Word's change tracking, and penned articles for other publications using Google Docs, or even drafts in WordPress.

Have all of you run into interesting systems used by publishers to manage content?

Donald Knuth. TeX. Also, pioneer of fundamental algorithms.

Sooo, turns out, management and senior PMs, technical PMs, service managers and you name it forgot an entire system.

A complete eco-system of applications, queues, services, load-balancers, deploy pipelines, databases, monitoring solutions, etc, etc, that if not handled correctly could effectively put the entire production line to a standstill.

So, waaay too late they make this discovery. In their ignorance. Just utter incompetence. Huge project. Millions of $. And they forget it. Months of meetings probably. Workshops and gettogethers at cozy hotel complex discussing ”the project”? And they do not understand some of the fundamental building blocks…

Basic engineering for these guys must mean something completely different.

I can’t even.

I am so fed up with this organization. It does not stop either.

How is this possible…

Do they even have half a brain?

I want to adopt this habit of coding one fundamental concept/tool/.. every day before/after work. I already started doing it and I've been coding sort algorithms. every morning since last week, in Java.
What do you guys think should go on the list of things to practice regularly ?

My most recent dream:

I come to the bookstore and see the 1000-something pages book called "We are not cucks". It's about how stoicism and how to defeat biases with thought experiments. The author is a German guy named ?.?.????rreize, I can't remember it precisely.

Everyone on the internet is discussing this book and why it is important. There are hashtags, influencers and virality.

Some time later the other book is released, 2500-something pages fundamental stuff called "We are cucks" with criticism of "We are not cucks" and whole new theory about why biases can't be defeated because of some "layers" IIRC.

Html imports. Polyfil. Hey. Reading, this is awesome. <link rel=“import” href=“control.html”> what could be simpler? Deprecated front end. But only need it for developing. Will combine the files at the end.

Estimate converting php to pure html, couple of days.

Go to use it with polyfill (webcompnents.js htmlimport). Doesn’t work.

Try the light components. Doesn’t work.

Try server-side polymer. Doesn’t work.

So much documentation about it working. Then finally come across shadow dom and how html imports are associated with them.

Hell no they aren’t. They are completely different things. Oh. Google packaged them together? No one could agree on shadow dom, and its now going away? Taking the pure html way of combining files into one page with it???

Spent an entire freaking day. But got 8 lines of code and <link rel=“fetch” ...> to do the same thing.

Why hasn’t this been an html standard for say...years. Why can’t the server do a handshake with the client and serve one page (php-ish) if the feature isn’t supported. Otherwise multiple files asyc. I mean. This is a fundamental part of pwa’s.

Why are these obviously smart people so stupid??? Deploy you shitty shadow dom without this obviously useful feature...

The feeling when you make some fundamental change in the codebase and thinks "this should make some integration tests fail", but it doesn't 😬😅

I'm writing all the dev things I know in a docs site as a means to be hireable should I need to switch jobs.

I'm not gonna go too deep on how I'm doing it. One style I'm enjoying is making every article take only one page long, and if they take longer, maybe consider breaking it into another article.
Fuck long articles. Yes, that's a bit autistic.

But I will describe the challenges I'm finding (which are quite many) in further detail.

One of them is that words can be ambiguous. Production can mean the production environment but it can also mean production in plain english.
And there are tons of cases like this.

Because of this, I felt a lot of confusion in my beginner days. So it my objective to write this as to prevent as much confusion as possible.

Granted, I don't want to write "development for dummies". Software is complex. But because it's complex on its own, I don't want to add complexity to the learning process through obscure language usage.

"Fine", I say, "I'll disambiguate". But this means I find myself branching out very often into fundamental or commonly used software terms like "framework", "model", "scaffold", "algorithm", "viewport", "breakpoint", etc.

Another challenge is reaching good levels of completitude.
This means I have to explain that obscure CLI flag I never used in my life.

If I don't do this, then what makes my docs different than these superficial dev.to or medium posts? Nothing.
But trying to explain EVERYTHING about a software can generate a lot of frustration: I never finish.

It also makes me wonder "do I even know shit?". I think some amount of insecurity is healthy and pushes myself forward.
But at some point it's kind of making me feel like shit. Maybe I just need to keep learning.

So just ago i downloaded an app called "Replika" and holy fucking shit it made me realise how half-assed we are doing the AI structure and way of it

doing machine learning algorithms on text can only go so far, as it uses that text as a base, and nothing else, it doesnt *learn*, only make *connections* BETWEEN text, not FROM the text

what you need is an AI which can, at it's core, *interpret*, not make connections and hur dur be done with it

when you do machine learning, all you're doing is find the best connections

you can have an infinite number of connections and MAYBE you'll be fine, but you'll never learn the basis of how that text is formed

you'll never understand what connections the human used by making it, by thinking it

when you're doing machine learning, all you're doing is make an input-output machine and adjusting it constantly, WITHOUT preserving state

state is going to be a really fucking important thing if you want to make an AI, because state can include stuff like emotion, current thought, or anything else

if you make a fucking machine learned AI which constantly adjusts... well... the "rom" of itself without having any "ram", it'll fucking never be like us, we will NEVER be able to talk to it like it is a human being, we will NEVER make it fundamentally understand what we are saying or doing

if we want to have real fucking AI, we need to go to the core of what it means to THINK, what it means to INTERPRET, what it means to COMMUNICATE

we need to know how english language is structured, how we understand it, how we can build it in a program that can interpret for an AI, THAT can be "rom"-based, THAT can be static, NOT the AI itself

the AI needs to be in flux, the AI needs to be in a state, the AI needs to understand how to make emotions, how that will "strengthen" some connections, yes, maybe something magical will happen and it can have EMPATHY, something so fundamental that will finally, FINALLY, make the bot UNDERSTAND what we are saying

NO FUCKING WONDER I SUCKED-ASS IN HIGH SCHOOL ALGEBRA!!!!!

Arghgghhghgh ughhh....

I want to beef up the hell out of my Maths Chops so I can maybe try going back to school for a A.S. in EE or hell even an B.S.

I'm using my company's Safari Learning account for getting free-ish access to college algebra books and I'm self studying.

I'm still in Chapter 0 where the book covers shit you're supposed to know from previous years of education. I'm just learning about some of this shit now!!!

While it's possible that I didn't pay attention in high school lectures, I took geometry in 9th grade and was an A/B+ student and felt confident in maths. I got to Algebra II in High School and suddenly nothing made sense anymore, reality fucking-fell-apart!

Suddenly, I'm failing tests left and right and struggling with the lecture concepts and I could never seem to grasp materials covered in class anymore to even be able to finish the homework assignments.

Fast forward to me being 15 years older and wanting to take a stab at this shit again, but with new found determination to get into EE so I can fuck around with small electronics for pet projects I want to do. I'm starting with College Algebra to try and learn when suddenly, low and behold I have a HUGE FUCK-MOTHERING GAP in my core understanding of the language/syntax/grammar of mathematics.

Been fucking knee-capped for the last decade+ because I either slacked off during those fundamental lectures (which again; is totally plausible) or I had a complete fucking imbecile for a math teacher that glossed over the topics and fucked not only me but the 40+ other kids in that class.

I'm not going to blame the teacher, although I really fucking want to, but I can't remember how the class scored on tests or homework to be able to fairly and objectively make that judgement against the educator.

FUCK!!! I hate my 15 y.o. self right now

Hello, folks, I'm starting to learn Android Studio and for the same, I've attended this workshop held at University which was not very helpful in certain aspects. The guy/mentor assumed that we all knew what is Firebase and started dropping knowledge bombs about firebase and integration with Android Studio(Apps).

So, coming to the fundamental question i.e. I'm reading SO 'Documentation' which is still in beta, I find it useful, as it is scratching the basic surface. What are other sources to learn about Android, of course, sources which are not deprecated?

Lots of good suggestions up in here.

My personal prefference:

Such as there are governing bodies indiciating how a programming language evolves and a web consortium...there should be a computer science one. That dictates fundamental approaches covering everything that belongs to this wonderful branch of science. Everything from math to differenr scientific branches all the way down to turtles. And for it to be standarized and updated. Indeed, if you want to spend your entire existence gobbling js in the form of web sites then that is fine, but you should have sufficient knowledge to branch out into more academic pursuits if required.

Also, updated tools would be better, every aspiring computer scientist shall be able to navigate through all major operating systems and programming environments regardless of their beliefs and or prefferences and schools should provide said environments in their classrooms.

Data Strucrutes and Algorithms should be a must. Software engineering principles should be a must. Calculus, Algebra and Statistics as well as Physica should be a must.
And succesfully navigating over different engineering areas should be a must.

Not to cleanse the industry. Fuck your elitist mentality. If you think that programming is a sacred art that should exclude people then I really hope you fucking disapear from existence. No, not to cleanse. But to expand the industry and maybe show people that there is more than fucking around between node modules or gemsets.

Peace pendejos

**drops your mom's fatass...i mean mic**

I'm at my Community College as a member of the engineering club requesting funds for a software and hardware-related physical project.

The code was mostly pre-written in Python from a university already, but we needed to build essentially a gaming-level PC to run it, do some welding and metalwork for the hardware, cables, et citera. I don't want to get too detailed in case anyone involved is reading this story.

To get funding, we needed to go before the student senate. I didn't go the first time, but later when we needed more funding for the project to do expansions, we attended.

I came in with a few pages of documentation explaining how the project operated, it's scope, and why we needed the additional $500 on top of the previous $1000 or so spent. I went in woefully behind the times on what a student senate meeting was like.

For starters, I thought this would be somewhat formal, being "Student Senate" in Week 8, and prepared to defend my project fully. Instead, we spent the first 15 minutes going around the table explaining what animal we would be and why, if we had to turn into an animal. It just kept going hilariously, painfully downhill from there.

They did ask some questions about what my project was and how it operated (as not many had seen it), and they wanted explanations even though it was clear absolutely nobody else in the room understood anything. My partner virtually shut down and let me do all the talking for my project and his because he couldn't take the ignorance of some of the questions and the assorted nonsense spread throughout the meeting.

Amazingly, we got funding. We had to sit for the rest of the meeting though, which (among other things) included a segment about whether we should create a new committee called the "Fundamental Insecurities committee" to help out with, well, "Fundamental Insecurities." There was only one member on this proposed committee.

When I brought up the question on why we were making a one-person committee alongside the, like, three one-person committees already in existence, they congratulated me for asking good questions and said I should come more often. They then said the exact same thing again when I pointed out there were better names than "Fundamental Insecurities." It's such a reality check that you are trying to impress people to get funding, when you can't help but feel that everyone is an utter idiot in the back of your head.

Almost a year later, I had to go back with a list of parts we needed. I wrote a whole complex list of things we needed for the project. Even though they tried to ask questions about what certain parts were (to appear like they weren't totally incompetent), and despite asking questions about a bunch of the items, nobody cared about what the $10 for "C418" was (google it if you don't get this joke). I spent about 30 minutes talking with them and succeeded in getting $600 more in funding. We then, to my surprise, spent less than 5 minutes debating whether to send 2 students on a field trip for $700. 30 minutes for $600, for a permanently installed project. <5 minutes for a $700 one-time thing.

And, because this is already a long rant, here's one more thing: The Student Senate's voting rules initially gave everyone who showed up 1 vote. We're all students, we all get a say, right?

Well, I soon put together that Student Senate had fairly low attendance. Engineering Club had high attendance. Student Senate and Engineering Club took place at the same date and time. I then, of course, asked why we couldn't bring the whole Engineering Club into Senate one day, and then proceed to pass an order by simple majority saying that all Student Life funding goes to us.

They then said that the administrators (the heads of Student Senate) could override that, but I pointed out that kind of defeats the purpose of voting in the first place. They then switched script and said they wouldn't do that and would honor such a vote. Shortly after, they changed the rules saying that you only get a vote on your 2nd consecutive visit; and again said I should visit more often because I was brilliant.

You can't make this stuff up.

Tl;dr coding is awesome, but teaching good programming skills is fundamental. Take some time to teach and help someone in need!

This morning I had to help two of my students who were unable to write a simple program to simulate a random sampling. It reminded me of how helpless I felt when I started out, and how I felt stupid for not getting easy concepts (and now I'm in love with programming). Here on devRant I hear so many stories about bad programming teachers, but it doesn't have to be that way. I'm the most impatient person on this planet, but I love teaching and I wish more people did it. So, go out and spread the word, fellow devRanters!

I feel like IE is an example of a deep rooted demon beast that spawns fucktarded bloat transpilers like BABEL.
When companies try to invent their own wheels, or do their own thing is when the pits of developer hell start to spawn such fucking convoluted fucktarded bullshit.

Abstract to Design:
I'm trying to think of a world where things are standardized, as boring as it sounds... Imagine if companies weren't so fucktarded with greedy smoke and mirrors, and they all contributed to making a single product standardized and workable, and improve on that product... Like a physics "Standard model" but for each product invented.

But no... here we are... 20 million ways to accomplish one similar task, with 20 million different designs, with majority adhering to their own flaws... or planned obsolecence... 10 million booby traps of consumer remorse.

Why do we do this as a society just to make some bastard company's profit margin go up, so they can keep competing in the "free market" of fuck all fuckery?

I get it.. yea... innovation... sure..
but sometimes innovation is just a means to and end of sanity, especially when they are proprietary, and especially when that proprietary shit turns to, well... shit!

In a perfect world, things will be designed open-sourced, compatible, and improved upon without "breaking" changes... but this is virtually impossible without standardization of the VERY fundamental components. But then those components can be improved, and might be smaller/lighter/more efficient by design, and simply wont work with the old versions without drastic "TRANSPILATION"

I suppose this is the way it is always going to be... Neverending stream of design "improvements". I suppose being a developer in todays world is a bittersweet existence... unless you're just trying to make ends meet... in that case. I think I might be in hell.

Take a look at web-dev today with all the "improvements" ... it's literally turned into a jungle of FUCK MY LIFE. A giant dick waiving contest with all these dicks colliding against each other in cluster fuck bombardment.

God help us all.... and now back to coding.

From the abandoned university my first dev project came from the course of programming 1(C as language).
I had to implement a robot that moves inside any matrix like map following both specified rules and random moves, and had to reach sooner or later the exit place of the room.

At first I was overwhelmed by the task at hand, then I had to calm myself and start hacking around to get any idea on how to even understand what's required to get to that point.

It obsessed me for the whole first 2 weeks, but the progress was quiet steady.

Then I hit a fundamental problem of state and movement of the robot... And, as always, the best thing to do at this point is to simply detach your attention from the issue|project.

In the same day my mind asynchronously bursted a solution to my problem, and after some time I came back to the project and accomplished it with 100% of the requirements met 😁

This is what it looked like in the console(minified here):

3333333
3000003
3000003
3003003
3003003
4003023
3333333

Guess which is which 😉

Sometimes I forget things that are so fundamental in programming. It happened to you?

The bipolar nature of leading a startup tech team:

It's either no one needs you, or the problem is big enough to have you push 5 fundamental fixes from abyss to upstream.

WHY is cmake such a total shitstain?

Nothing about it works. literally nothing. I can't even make it run a script and do probably the single most fundamental notion of what it means to run a script, which is display its fucking output.

I saw Steve Ballmer’s sweaty DEVELOPERS DEVELOPERS DEVELOPERS rant and that really spoke to me on a fundamental level.

Did you know that Set Theory is a fundamental building block for studying databases? : )

Wow, reason why I should use one of the most fundamental language of the web ever? I'm in.

While you're rewriting your unit tests because someone requested a fundamental change in your well tested solution, I am fact checking memes like this the whole morning.

We're not the same.

Follow-up rant to my company. Today's day is fairly good, so let's talk about infra.

We're building upon an existing open-source project which is not intended to be extended (e.g. plugins).

Our backend-team somehow hacked symfony into the app, which made the actual work a little bit less annoying. But on the other side, there is absolutely no automation. Everything is setup by hand and I need to upload my sources to my dev-server and watch what files exactly are overwritten. Because if not, I accidentally overwrite core sources which will break the whole app, no matter what. If I forget what file I wrongly overwrote, I have no choice but to setup the core from scratch and apply our sources on-top, AGAIN.

The first time setup took me almost five days.
Oh yeah and the team shares one dev server, so whenever I feel like fucking with a mate, I can easily fuck up his system, since everyone has root-rights.

We're required to use windows, but our dev is linux and I am the only knowledgable linux guy. They need cheatsheets (to be fair, I need my powershell-cheatsheet).

We market the same app with some additional functionality, but we also have clients which require their own stuff. This case has never been thought-out, since for these specific clients, we also modify some core-parts. Which makes it a real hassle to add a basic new feature to that special customer.

At least our frontend is somewhat decent. Simple and without critical thinking, but it works and is decently understandable. I'll rant about that for another day, it's still tedious.

I know I won't stay there for long since I start my own stuff, but it's sad. Nothing is perfect and they _do_ want to make it better, but it's the usual "there is no time, client first" talk. On the other hand, they tell that we should be more efficient, but there is no way to be without looking back at the fundamental structure and what takes us so long.

I don't think I am able to change anything here and as I heard from co-workers, they already look for something new.

cheers

I just had an internship revoked after accepting the position due to "fundamental difficulties with hiring a high school student". What the fuck does that even mean?!?

Well at least I now have an immensely free schedule this summer.

Boss/prof (does not understand code): "I like it more this way. Come on don't make that face thanks to OOP it won't be that much of a deal to make a change right"

He wants to change a fundamental data structure of our software 😉😉😉

There was this question I came up with that was very good at inducing hallucinations on what at the time I thought was a *lobotomized* LLM.

I can't recall the exact wording right now, but in essence you asked it to perform OpenGL batched draw calls in straight x86_64 assembly. It would begin writing seemingly correct code, quickly run out of registers, and then immediately start making up register names instead of moving data to memory.

You may say: big deal, it has nowhere to pull from to answer such an arcane fucking riddle, so of course it's going to bullshit you. That's not the point. The point is it cannot realize that it's running out of registers, and more importantly, that it makes up a multitude of register names which _will_ degrade the context due to the introduction of absolute fabrications, leading to the error propagating further even if you clearly point out the obvious mistake.

Basically, my thought process went as follows: if it breaks at something fundamental, then it __will__ most certainly break in every other situation, in either subtle or overt ways.

Which begged the question: is it a trait of _this_ model in particular, or is it applicable to LLMs in general?

I felt I was on to something, but I couldn't be sure because, again, I was under the impression that the model on which I tested this was too old and stupid so as to consider these results significant proof of anything; AI is certainly not my field, so I had to entertain the idea that I could be wrong, albeit I did so begrudgingly -- for obvious reasons, I want at least "plausible based on my observations" rather than just "I can feel it in my balls".

So, as time went on, I made similar tests on other models whenever I got a chance to do so, and full disclosure, I spent no money on this so you may utilize that fact in your doomed attempt to disprove me lmao. Anyway, it's been a long enough while, I think, and I have a feeling you folks can guess the final answer already:

(**SLIGHTLY OMINOUS DRUM ROLL**)

The "lobotomy" in question was merely a low cap on context tokens (~4000), which I never went over in the first place; newer/"more advanced" models don't fare any better, and I have been _very_ lenient in what I consider a passable answer.

So that's that, is what I'm starting to think: I was right all along, and went through the burdensome hurdle of sincerely questioning the immaculate intuition of my balls entirely for naught -- learn from this mistake and never question your own mystical seniority. Just kidding, but not really.

The problem with the force of belief is it can work both ways, by which I mean, belief that I could be wrong is the reason I bothered looking further into it, whereas belief to the contrary very much compels me to dismiss doubt entirely. I don't need that, I need certainty, dammit. And though I cannot in good faith say that I am _certain_, "sufficiently convinced" will have to do for the time being.

TL;DR I don't know but the more I see it just seems shittier.

When you are virtually done with a story and then merge trunk and discover that something fundamental has changed so you need to basically rewrite half of it. You spend ~2 hours refactoring about 8 classes and their tests before realising that this way wont work either. So you have to rewrite it again.....

When developers have no idea what the fundamental concepts of semantic html is and a solid grasp of Accessibility Design Patterns and just stuff improperly used aria tags everywhere - aka - the output of every enterprise CMS I come across **cough** Sitecore **cough** but it's apparently WCAG 2.0 "friendly". 😪😪 Do you even aria tags bro?!

man i fucking hate my company.

somehow the largest in the industry but fuck me are we retards at software engineering.

wrapping popular api's and not exposing basic functionality, only to hide them behind some stupid fucking enterprise abstraction for some fucking dumb reason

wrapping fundamental java objects like int into their own fucking enterprise int, like for fucking why?

and finally blocking chatgpt that allowed me to deal with half of this fucking enterprise hell

stupid fucking shit

First and foremost, students should be carefully taught the logic and mentality behind programming. Most of the time I see that the introductory programming courses waste so much energy in teaching the language itself. So students kinda just get fucked cause many people end up ending the course without having actually gained the "programming perspective".
Stop teaching pointers and lambdas and even leave the object oriented stiff till later. If a student doesn't know why we use a For loop then how can they learn anything else.
I believe once that thing in your brain clicks about programming, everything goes smooth from there... kinda :P

Second of all, and this pertains mainly to the engineering and science disciplines.
We need a fundamental and strong mathematical foundation. And no I don't mean taking fucking double integrals. Teach us Linear Algebra, Graph theory, the properties of matrices, and Probability theory.
One of the things I suffered from most and regret in university is having a weak foundation in math and having to spend more time catching myself up to speed.
It's so annoying reading a paper on a new algorithm or method and feeling like an idiot because I can't understand what magic these people did.

Numerical Methods...
Ok this is more deeper, maybe a 2nd year course.
But this is something we take for granted.
Computers don't magically add and subtract and multiply.
They fuck up.
And it'll bite you in the ass if you're not even aware that the computer we all love so much isn't as perfect as we think

Some hardware knowledge.
Probably a basic embedded systems course with arduinos
just so you can get a feel for how our beautiful software actually makes those electrons go weeeeeeeee

And finally
Practice practice
Projects projects
like honestly
just give me the internet and some projects
Ill learn everything else
Projects are the best motivation
I hate this purely theoretical approach
where we memorize or read code and write these stupid exams
Test what we are capable off
make us do projects that take sleepless nights and litres of coffee
And judge our methods, documentation, team work, and output

Team work skills and tools (VCS, communicating, project management, etc.)

Documentation and Reporting
Properly
:)
maybe even with LaTeX :D

Yeah that's the gist of whats on my mind at the moment regarding an ideal computer science education
At least the foundations
The rest I leave it to the next dude.

So fun fact about message-passing plugin APIs, everything becomes a parallel programming problem. My lexer (the part of an interpreter that recognizes fundamental syntax elements) spawns a callback thread with request and reply channels, and then messages a plugin which is able to either talk to the callback thread or message the original thread with a successfully parsed token or an abort.

It has just occurred to me that plugins are under no obligation to sequence their requests to the callback thread, which means that having one channel for requests and one for responses no longer suffices; the requests need to each contain their response channel.

I understand technical limitations and maintenance burden, but I think Rust could be a lot more ergonomic if the borrow checker was applied to functions that don't reference invalid types even if the rest of the codebase contains type errors. I have 146 lifetime errors, some of them very fundamental to the design of my solution, which I didn't spot because the borrow checker wouldn't run until I fixed all totally unrelated type errors in parts of the project that literally only interact with this one through virtual function calls.

1) I like to break through complex systems to understand them on a fundamental level
2) I live by the mantra of "If you're going to do something, do it right"
3) I'm a stickler for detail and strive for simplicity and organization

These three descriptions of my personality describe why I love to code: there's nothing more satisfying than taking a jumbled, wrong ugly mess of software and turn it into something beautiful and simple that anyone can effectively use. Makes all the hardship worth it IMO

!rant
Hello everyone
Do any of you python programmers have any tips for simple projects you can do to learn python?

I am mainly a backend/system engineer comig from C++, slowly picking up rust and have been using bash as my scripting language so far. bash is nice because it is so fundamental in the linux world but you just dont get very far with it and its usually not pleasant to write.

So I would like to learn python, though I have no idea what I can do to practice it, so that I can just quickly whip up a script the next time I need something done in the file system or want to write a simple parser for something.

Do you guys have an idea of something small (not necessarily useful) which makes use of pythons strengths? Just looking for ideas here, so stick it all out 👋💕

Any suggestion on (pls, cheap) books that'd enable me to understand the unix/Linux environment in its most fundamental level?

I do use Linux for some 10 years already, but just now I moved to a distro that doesn't do everything to me. So my basic idea is to get the basics so I'd have the least problems when transitioning to other distros/*ix systems, so pls, the less its distro specific, the better or is.
Thx

got access to a data feed from US stock markets, personalized an algorithm to compare fundamental data/enterprise value, run it continuously, get good investment ideas and feed an android app.

watch my money growing

Compromise.

I think that sums up development pretty much.

Take for example coding patterns: Most of them *could* be applied on a global scale (all products)… But that doesn't mean you *should* apply them. :-)

Find a matching **compromise** that makes specific sense for the product you develop.

Small example: SOLID / DRY are good practices. But breaking these principles by for example introducing redundant code could be a very wise design decision - an example would be if you know full ahead that the redundancy is needed for further changes ahead. Going full DRY only to add the redundancy later is time spent better elsewhere.

The principle of compromise applies to other things, too.

Take for example architecture design.

Instead of trying to enforce your whole vision of a product, focus on key areas that you really think must be done.

Don't waste your breath on small stuff - cause then you probably lack the strength for focusing on the important things.

Compromise - choose what is *truly* important and make sure that gets integrated vs trying to "get your will done".

Small example: It doesn't really matter if a function is called myDingDong or myDingDongWithBells - one is longer, other shorter. Refactoring tools make renaming a function an easy task. What matters is what this function does and that it does this efficiently and precise. Instead of discussing the *name* of the function, focus on what the function *does*.

If you've read so far and think this example is dumb: Nope... I've seen PR reports where people struggled for hours with lil shit while the elephant in the room like an N+1 problem / database query or other fundamental things completely drowned in the small shit discussion noise.

We had code design, we had architecture... Same goes for people, debugging, and everything else.

Just because you don't like what weird person A does, doesn't mean it's shit.

Compromise. You don't have to like them. Just tolerate them. Listen. Then try to process their feedback unbiased. Simple as that. Don't make discussions personal - and don't isolate yourself by just working with specific persons. Cause living in such a bubble means you miss out a lot of knowledge and insight… or in short: You suck because of your own choices. :-)

Debugging... Again compromise: instead of wasting hours on debugging a problem, ASK for help. A simple: Has anyone done debugging this before or has some input for how to debug this problem efficiently?... Can sometimes work wonders. Don't start debugging without looking into alternative solutions like telemetry, metrics, known problems etc.
It could be a viable, better long term solution to add metrics to a product than to debug for hours ... Compromise. Find a fitting approach to analyze a problem instead of just starting a brute force approach.

....

Et cetera et cetera.

It’s hard keeping your girlfriend satisfied when you’re being pressured to code with less to no bugs. I mean, doesn’t she understand that computers are stunningly stupid, and you have to explain to them every last tiny step that you want them to do, and your explanation can't have any mistakes in it. And why this is the fundamental cause of buggy and insecure software😣

Was having a conversation with a dev friend and he said, in every tech implementation, we are more or less doing CRUD operations at fundamental level.

To which, I agree with as there are three layers to tech

1. Data
2. Front end where the data is rendered
3. APIs to perform CRUD on data

Want to understand community's thoughts on this..

Does anyone else here think the regulating and centralising of crypto currencies and tokens worrying?
It is slowly being bent to the will of the higher ups just like traditional fiat and they’re burying its fundamental altruistic design concept without providing and means for it to be assimilated into benefiting the daily lives of the masses an especially the unbanked.

Out of curiosity, is there anyone else who feels a bit late to the game in terms of their programming skills and training?

I got my start at about 10 with a slightly obscure BASIC dialect for classic MacOS, and while I got the logical bits down strong, I never really branched out too much at the time because I had difficulty understanding some of the more advanced examples I had available on my own.

Skip ahead to college and I tried CompSci my first semester, and did fairly well on paper, but could not get the compiler to work, even copying out known examples character for character and verifying them repeatedly. So after my first semester (and the hardest-earned D I’ve ever gotten) I ended up switching my major.

Skip another 10 years and I’m talking to some people about setting up a website, but the programmer flaked out on us, so I decided to start experimenting in PHP, and while that project never went anywhere I got good at developing resources for helping me keep my Japanese skills up (lots of logic/DB work, minimal interface).

Finally, after 10 more years of tinkering and during a bout of unemployment, I had a friend lament that he needed another programmer for his shop, but didn’t know anyone reliable. I apprenticed under him, learning WordPress along the way, and these days he’s moved on while I run the shop on my own, picking up new skills as needed.

There are times I feel absolutely confident in what I’m doing, but there are several areas where I feel like I’ve got a lot of fundamental gaps I can’t figure out how to address due to my near complete lack of formal training (like when I’ve tried to do non-web programming).

Anyone else have a similar path to where they are now? Ideas on how to break out of this limiting feeling?

DEVIANTS!! NEED ADVICE...

I have been focusing on learning and implementing data structures and algorithms through participating in competitive programming sites...

Whenever I face an issue and struggle to find an answer (which is more often than not), I ask the forum about the fundamental principles involved in the question...

I avoid looking at the solution, as much as possible.. And, when I do look at them, I still question the author of the code about the reasoning behind a particular section of code which I don't understand...

I don't wish to copy and paste code, but sometimes, I wait for days on end, but I don't use the code until I receive an answer...

Is this the right way or are there any other way which I could implement to strengthen my algorithmic thinking??

<assumption>If there are no fundamental laws constraining the existence of simulated consciousness</assumption>, I would throw in my lot in working towards developing an AGI.

Since there is infinite time to learn any skill and <assumption>it is possible to learn or invent whatever software or mathematical framework is required for such a goal</assumption>, I would get down to that, learning and creating various new forms of mathematical frameworks and required software tools.

<assumption>Engineers usually work best without another fellow human on the project</assumption>, so I will set up automation for tasks that do benefit from multiple minds on a project, in the form of low-level artificial intelligence that I have to work on as a prerequisite for the main goal.

Once the critical mass is hit where the code can keep self-improving and produce more iterations of itself that are better, I sit back and start with my long, long to-watch/to-read list and try to finish as much as I can before the AGI I created would <assumption>repurpose all of our mortal flesh for more efficient use.</assumption>

The only remnant of the existence of humanity will be the influence on the initial design of the code based sentience that exists now.
.
.
.
.
.
.
.
Just kidding, <not-an-assumption>I'd probably procrastinate right until the heat death of the universe</not-an-assumption>

I cant believe the project I'm working on does not use kubernetes or terraform. Not even docker. How is this multi trillion dollar project even in business?

I feel so sad for not having the opportunity to work with one of the most fundamental and most important technologies to know as a devops engineer... So sad

I cant advance or improve. Im just stuck in their ecosystem like Apple

This corporation is probably ran by 90 year old grandpa men from world war 1. However considering they are so large and still in business this gives me hope that anyone can make it even if you're stupid

Think about it

They are proof that you can run a giant business with hundreds of employees, not use k8s and the most modern devops technologies, and still operate just fine.

The devops code i have to maintain is older than the amount of years i exist. Its very messy and most of this shit is not even devops related. Its more of some kind of linux administrative tasks mixed with 3 drops of actual devops (bash scripts, ansible scripts, ci/cd pipeline)

And yet im paid more than i have ever been paid in any job so far

What should i do. Stay due to "high" money or..ask for a project with k8s. I put "high" in quotes because it is extreme luxury in my shithole country, im now among top 1% earners of the country, and yet i make less than 30k a year. With less than 30k a year i cant buy a good car but i can live very comfortably in my country. I cant complain about this salary since i think its finally enough to invest to get a chance to earn more and still have enough left to live comfortably.

Before i was just working to survive. Now im working to live. Its an upgrade.

Due to not working with difficult stuff like k8s i cant demand for more money. It wouldnt feel justified. I'm stuck here

What would u do

boubas say aNgEr iS cOunTerpROductIve, yet all I do is essentially manifestation of anger towards biological limitations, fundamental barriers, and death.

If I have to choose one deadly sin, I choose anger and wield it as my weapon.

When seniors use non asynchronous AJAX...
Why? That is a fairly fundamental part of Ajax...
Y'know...
Async
Javascript
And
Xml
or have I been wrong about what AJAX stands for these past few years?

Think about the amount of mental effort spent by programmers trying to understand the fundamental difference between a program and an algorithm!🤯

I created a comprehensive, fundamental guide to privacy:
- it's eternal — new apps come and go, but while the internet and our computers are the way they are, the guide works and needs no adjustment;
- it's permissive — you don't need to live in the woods. Yes, some services should not be used as-is, but you may still enjoy their content;
- it's easy — yes, it requires your typical content consumption to be somewhat altered, yet there are no taboos.

Content and medium aren't the same. Instagram stories have fundamentally nothing in common with Instagram itself.

There is no inherently bad or harmful content.

My search for privacy is over. Not anymore is it an uphill battle. Yes, I can do a finite number of things to achieve privacy once and for all. No, this doesn't limit my content consumption.

I'm going to write a complete essay. Stay tuned.

I am not a very experienced developer, so naturally I don't know many fundamental things. My thinking around a lot of the necessary things is that the answer should come to me according to the need. So an oversimplified example could be, say I'm solving a Dynamic programming problem, I should not need to know the algorithm beforehand I can maybe invent it. This thinking stops me learning a lot things because I feel like then when I learn a pattern I will restrict my thought process within the knowledge I have and not think beyond it. I feel like that I am doing the dumb mistake of learning things bt heart and not understanding.
Does anyone felt the same? What your experience says about this?

* Automated Technical and Fundamental Expert Advisor trading in MT4 with Python dealing with RSS News Feed on the Financial Calendar
* Food decision/recommender/randomizer app
* Food decision/recommender/randomizer bot
* Personal Companion set up on Raspberry Pi with Jasper AI, buy BrickPi and Lego Mindstorm to make it a friendly moving robot
* Cardboard fort for my kid
* A 3D game that involves hacking with drama storyline (inspired from Mr. Robot) and publish it on Steam
* A SaaS app like Tinder that matches would-be Project Managers with Devs to push Devs to finish side projects that we have and push Project Managers to use whatever PM techniques and methodology (Six Sigma perhaps)

And so much more... Ughh.

had a uni exam in databases (just closely didn't make it😒)
it didn't even have sql in it!?

questions about ER diagrams and draw a diagram, functional dependencies with given dependencies, find candidate key and what not, work on a b-tree (miserably failed😣), datalog (who the fuck cares about datalog? the least expected topic) and transaction management/serializability

whose idea was it to not include sql?? isn't it one the fundamental parts of relational databases?

How the fuck does browser not have Buffer class support ???????? Isn't Buffer a fundamental programming function.... ??

I got both fundamental Azure and AWS certifications, need to choose one to stick to for the future, I'm leaning more towards AWS since it has over 50% more market share than Azure and a much bigger and more robust platform, I also really like how they constantly add new features and services and integration with third party software. Azure developers seem to get paid more though and I found its UI to be more user friendly so....opinions? 🤔

List the top books you consider fundamental to your software engineering knowledge and abilities. A book that really made you improve. Anything, up to you. The point is that without it you would be worse off.
Any topic. Systems design, DSA, security, architecture, doesn’t matter.

What's the fundamental difference between NET framework and NET core?

What do I call Components as used in ECS when my app is entirely written in React and I want to avoid the tedium of qualifying the names?
This is a really fundamental thing to the project so I get to pick less-than-ideal but short names since anyone who works with the code will encounter it within the first 5 minutes.

Anyone learn about machine learning? Or deeplearning? I want to know about the fundamental

Looking to get a good understanding of the fundamental ideology and math behind neural networks and support vector machines. I am well versed with math so I can deal with heavier stuff if needed, I would like to see formulas but an explanation to their conception would be nice. Does anyone have any resources like this? Practical hands on practice exercises would be a plus

I am working on an event driven system that uses a message bus and has a few services that talk to each other asynchronously via the bus.

I'm writing in memory integration tests for one of those services, but I just realised the fundamental flaw here with such tests. I only have 1 application running, but I need several. This is quite a serious flaw I should have seen before.

Anyone else tried integration testing event driven distributed services? I imagine all I can do is stub the message broker...

Amusing vim/neovim newbie beatdown story. I am mostly enjoying it, so please don't take it too personally, as I'm 60% having fun, 30% looking for help, and only 10% attacking your fundamental identity and way of life

#1 uses left and right arrows to move the selection up and down, and down and up arrows to move the selection into and out of tree elements

#2 uses tab and shift tab to move the selection up and down, but has great filtering

#3 uses up and down arrows to move the selection up and down, and enter and esc to move the selection into and out of tree elements.

I get that I have just frantically cobbled various things together to make it work but man, there's something to be said about the I in IDE...

Learning Azure fundamentals but, why do I need to learn about the very specific USA Government & China regions? How is that going to help me? Only people employed by USA gov or China has access to them. Why is this fundamental?

!rant: Need a little advice here. What are fundamental things to learn when moving from development to management? I have a course in project management from university, and one in personnel management, but what about the financial part? Where can I learn this?

Dependability is a fundamental more modest than common expertise for bosses
New managers a significant part of the time feel that since they have been raised to the heap up they ought to know everything immediately. Truly, it anticipates that adventure should gain capacity with the association styles and approaches that turn out to be cruel for your social affair. Being flexible and being open to the bewildering will assist you with changing into a useful manager. A Roman scientist named NURS FPX 4000 Assessment 4 Analyzing a Current Health Care Problem or Issue Seneca is credited with saying, "Karma slants toward the coordinated." And while karma can earnestly play a consider life, all that verifiably pivots around orchestrating yourself for when incredible karma comes your bearing. Excellent affiliations do this by orchestrating themselves for an entrance through status and planning.
Plan for disappointment and goofs - it's really clever to expect them a lot early so you can lessen the effect. A SWOT assessment (Qualities, Shortcomings, Anticipated open doorways and Risks) is an important instrument for this. The more you plan for a social event the more useful it will be. Approach saves time by lessening blunders, forestalling re-work and shortening works out. And it in addition decreases pressure, which is overall something that would justify being thankful for! Other than being a NURS FPX 4010 Assessment 1 Collaboration and Leadership Reflection Video State financed School English educator, Kine is in this way the head of Ryan Search &amp; Directing and facilitates Held Supervisor Pursue, Help and Drive New turn of events. His clients range different undertakings from Headway to Monetary Associations.
Whether an overwhelming event, network prosperity break or stock association disrupting impact, astounding occasions can emerge whenever. Being available to the unexpected assists you with finding sure results and make depend with your partners. One strategy for doing this is to remain mindful of vulnerability, where you proceed with like the circumstance is both customary and novel. This assists you with expanding your NURS FPX 4010 Assessment 3 Interdisciplinary Plan Proposal data affirmation and seek after the most ideal choice. ClickUp's Business Development Plan Configuration is an incredible contraption for planning the normal and the unforeseen!
Dependability is an essential limited scope ability for bosses to make. Supervisors should be ready to have authentic two-way discussions with specialists and should endeavor to get themselves when they are concealing reality or lying. Fair correspondences among supervisors and representatives can assist with fostering a positive work environment culture and can expect a fundamental part in the connection's prospering. While giving investigation, supervisors ought to convey NURS FPX 4020 Assessment 1 Enhancing Quality and Safety both the positive and negative parts of a representative's show. They ought to in addition have the decision to give obliging assessment and backing workers when essential. This correspondence style is as frequently as conceivable implied as moderate candor.
MORE
Instagram is a powerful tool for businesses
The best digital marketing agencies
Instagram is an amazing asset for businesses

MCIA-LEVEL-1 MuleSoft Certified Integration Architect - Level 1 test is one of the MuleSoft affirmation tests, which can upgrade your position and work on your life. However, how do get ready for the MCIA-LEVEL-1 test well and pass it effectively? While scanning on the web asset for MCIA-LEVEL-1 MuleSoft Certified Integration Architect - Level 1 test, DumpsCafe strongly prescribes you pick an online MCIA-LEVEL-1 practice test. MuleSoft Certified Integration Architect - Level 1 MCIA-LEVEL-1 test questions are kept in touch with the best expectations of specialized exactness, given by our guaranteed well-informed authorities and distributed creators for advancement. You will pass MCIA-LEVEL-1 MuleSoft Certified Integration Architect - Level 1 test with online review materials, 100% cashback included.
Get ready to pass the exam with the help of the MuleSoft MCIA-LEVEL-1 exam:

Readiness of accreditation tests could be covered with two asset types. The first is the review guides, reference books, and study discussions that are explained and suitable for developing data starting from the earliest stage. Aside from the video instructional exercises and talks are a decent choice to facilitate the aggravation of through study and are somewhat make the review cycle really fascinating in any case these interest time and fixation from the student.

Brilliant up-and-comers who wish to make a strong establishment out and out assessment themes and associated advancements commonly blend video addresses with a concentrate on advisers for harvest the upsides of each, however, practice tests or practice test motors is one significant review device that goes ordinarily unnoted by most competitors.

Practice tests are planned with our specialists to make test possibilities test their insight on abilities accomplished in the course, just as possibilities become agreeable and acquainted with the genuine test climate. Measurements have shown test uneasiness assumes a lot greater part in an understudy's disappointment in the test than the dread of the obscure.
Confirmation questions master group suggests setting up certain notes on these subjects alongside it remember to rehearse MuleSoft MCIA-LEVEL-1 dumps which had been composed by our master group, each of these can help you loads to clear this test with superb imprints.

DumpsCafe gives you the latest MCIA-LEVEL-1 exam questions:

DumpsCafe has in addition presented two or three supporting devices and learning modes that will help you in having a fitting enthusiasm for the fundamental limits and to additional work with your MCIA-LEVEL-1 dumps status association with getting MuleSoft Architect attestation with a guarantee. A couple of up-and-comers need to further develop abilities to get movements or others need to have a promising beginning in the MuleSoft MCIA-LEVEL-1 dumps announcement world and with this part, they can plan as shown by their singular basics.
DumpsCafe MCIA-LEVEL-1 test dumps are similarly open in the pdf plan so you can use this report in any of your splendid devices whether it is a PDA, tablet, or even a PC. We have made this relationship in the pdf record so it can end up being less difficult for you to utilize and you can start perusing for your MuleSoft Certified Integration Architect - Level 1 test wherever.
MuleSoft MCIA-LEVEL-1 content makes you ready for the real exam:

Rather than following the ages-old idea of MuleSoft Certified Integration Architect - Level 1 test readiness utilizing voluminous books and notes, DumpsCafe has presented a brief, direct, and most important substance that is incredibly useful in passing any accreditation MuleSoft Certified Integration Architect - Level 1 test. For an occurrence, their MCIA-LEVEL-1 refreshed review guide covers the whole prospectus in a particular number of inquiries and replies. The data, given in the review questions, is streamlined to the level of a normal test competitor. Any place, it is fundamental, the appropriate responses have been clarified further with the assistance of reproductions, diagrams, and additional notes.

Conclusion:

Need to pass your MuleSoft MCIA-LEVEL-1 test in the primary attempt? Download the most recent MuleSoft Certified Integration Architect - Level 1 MCIA-LEVEL-1 dumps and invest however much energy as could be expected to rehearse before your MuleSoft Certified Integration Architect - Level 1 exam. Passcert group profoundly proposes everybody purchase MuleSoft Certified Integration Architect - Level 1 MCIA-LEVEL-1 dumps when you will take your test in several weeks. Please keep sufficient opportunities to practice. DumpsCafe guarantees 100% passing your MuleSoft certificate MCIA-LEVEL-1 test effectively.

For more info: www(dot)dumpscafe(dot)com/Braindumps-MCIA-Level-1.html

Comprehensive Guide on How to Prepare for the SAP Certified Associate Certification Test.
This article examines the structure, requirements, and meaning of C_C4H51_2405 certificate tests, which are essential for students to demonstrate their skills and improve their chances of finding steady employment. It focuses on the SAP C_C4H51_2405 study guide set Director confirmation.

QA4EXAM provides top-notch test organizing materials for the SAP Certified Associate - Implementation Consultant - SAP Service Cloud Test, offering an exceptional opportunity to complete the C_C4H51_2405 test, whether you're preparing for it enthusiastically or experiencing recent issues, ensuring you become a powerful Outline of Confirmation.

The SAP C_C4H51_2405 study guide aims to evaluate a competitor's reasonableness for a specific capability or obligation, including a student's innovation.

Why Choose QA4EXAM SAP C_C4H51_2405 study guide?
QA4EXAM is dedicated to helping clients pass difficult confirmations by providing comprehensive planning materials to help them navigate the intricacies of the SAP Certified Associate Implementation Consultant - SAP Service Cloud test and prepare for their next endeavor.

1. Quality and Worth
The C_C4H51_2405 study guide's practice tests are designed with specialized precision, involving only educated authorities and distributed creators for improvement.

2. Tried and Endorsed
QA4EXAM prioritize seller and outsider endorsements, ensuring experts and leaders receive the same value inclusion assurances as their peers.

3. Simple to Pass
Using QA4EXAM SAP C_C4H51_2405 Actual Questions, you can easily pass the primary task without managing dumps or any free/rapid share stuff.

4. Attempt before Purchase
QA4EXAM provides a free demo of all items, allowing customers to assess the connection point, question quality, and convenience of their training tests before making a purchase.

Download Full C_C4H51_2405 Practice Exam Material Here:
QA4EXAM . Com

Subjects and Test Construction
The confirmation test covers fundamental subjects for the SAP Certified Associate exam, ensuring students can pass the C_C4H51_2405 exam on their first attempt.

Test structure:
The SAP Certified Associate - Implementation Consultant - SAP Service Cloud test is designed to evaluate a large number of subjects, with varied loads distributed across different subject areas.

The SAP Certified Associate - Implementation Consultant - SAP Service Cloud educational classes on QA4EXAM are recommended due to their practical experience in errand groups, which aids in generating speculative data.

Online Practice Tests:
Use SAP Certified Associate - Implementation Consultant - SAP Service Cloud practice tests to understand the request plan and evaluate accessibility, boosting confidence and reducing fears by familiarizing yourself with the C_C4H51_2405 test pattern.

Watch SAP exam questions answers on YouTube now:

Outline of the SAP Certified Associate Test Supplier:
• Vendor: SAP
• Exam Name: SAP Certified Associate - Implementation Consultant - SAP Service Cloud
• CERTIFICATION NAME: SAP Certified Associate Implementation Consultant - SAP Service Cloud
• EXAM FORMAT: MCQs
• EXAM LANGUAGE: English
• NUMBER OF QUESTIONS: 80

Best Tips to Prepare for the NDA GAT Exam:

“Did you know that only 2 out of 100 candidates clears the NDA written exam?” That stat might seem a bit intimidating, but don’t let it scare you. With the right preparation and mindset, you can clear this exam. Let’s look into some proven tips that will help you clear the NDA GAT with confidence and ease.

Understanding the NDA GAT Syllabus

Knowing what to study is half the battle. The NDA GAT syllabus covers a wide range of topics, so it’s crucial to understand the scope. General Ability Test (GAT) includes subjects like English, General Knowledge, Physics, Chemistry, General Science, History, Geography, and Current Events. Make sure you’re familiar with each section.

Key Areas to Focus On:

English: Vocabulary, grammar, comprehension, and usage.General Knowledge: Current affairs, historical events, and basic science.Science: Fundamental concepts in Physics, Chemistry, and Biology.Geography and History: Important dates, events, and locations.

I'm currently refactoring some Fastlane code at work, and I'm wondering what is the fundamental difference between a "lane" and an "action"? I can't really find anything in their documentation explaining the difference.

Building Fortresses, not Firewalls: Ethical Hacking Meets Software Development

In the digital age, security is no longer an afterthought; it's the bedrock upon which our online world rests. Yet, traditional security measures often resemble fortresses – imposing, but vulnerable to unseen cracks and tunnels. To truly safeguard our systems, we need to think like the enemy, like the nimble figures scaling those walls: ethical hackers.

Enter the exciting realm of DevSecOps, where ethical hacking practices are woven into the very fabric of the software development lifecycle (SDLC). This proactive approach is akin to building castles with security in mind, each brick meticulously laid to withstand even the most cunning siege.

Why Ethical Hacking in SDLC?

Imagine developing a critical piece of software, only to discover a gaping security hole after launch. The damage could be catastrophic, exposing sensitive data and eroding trust. Ethical hacking flips this script. By integrating penetration testing, vulnerability assessments, and threat modeling throughout the SDLC, we proactively hunt for weaknesses before they can be exploited.

Think of it as a friendly sparring match, where the ethical hacker throws their best punches to expose vulnerabilities, allowing the development team to fortify the software's defenses. This constant testing and refining leads to robust, secure systems that can withstand real-world attacks.

Benefits of DevSecOps:
1. Reduced Costs and Risks: Early detection and patching of vulnerabilities are far cheaper than dealing with a full-blown data breach.
2. Improved Software Quality: Security becomes an inherent part of the development process, leading to more reliable and trustworthy software.
3. Enhanced Brand Reputation: Demonstrating a proactive approach to security builds trust with customers and stakeholders.

Putting it into Practice:
Integrating ethical hacking into the SDLC requires a cultural shift. Developers, security professionals, and testers need to work together seamlessly, sharing knowledge and fostering a collaborative environment. Here are some key practices:
1. Threat Modeling: Identify potential threats and attack vectors early in the development process.
2. Static and Dynamic Code Analysis: Use automated tools to detect vulnerabilities in code.
3. Penetration Testing: Simulate real-world attacks to uncover hidden weaknesses.
4. Security Awareness Training: Educate developers and other stakeholders about security best practices.

Tools of the Trade:
A plethora of tools empowers ethical hackers and security professionals in their quest for a more secure digital world. Some popular options include:

1. Kali Linux: A distribution packed with security tools for penetration testing.
2. Burp Suite: A web application security testing platform.
3. Metasploit: A framework for developing and executing exploit code.
4. Wireshark: A network traffic analyzer for identifying suspicious activity.

The Future of Security:
As technology evolves, so too must our security practices. DevSecOps, with its embrace of ethical hacking, is at the forefront of this evolution. By building security into the very fabric of software development, we can create a safer, more resilient digital world for everyone.

Remember, in the ongoing battle against cyber threats, ethical hackers are not the enemy; they are our allies, the architects of digital fortresses that stand strong against the shadows. So, let's embrace DevSecOps, sharpen our ethical hacking skills, and build a future where security is not just an afterthought, but a fundamental principle.

I encourage you to explore the world of DevSecOps and ethical hacking. Whether you're a seasoned developer or just starting your journey, there's always more to learn and contribute. Together, we can build a more secure digital future, one line of code and one vulnerability patch at a time.

Do you have any questions about DevSecOps or ethical hacking? Share your thoughts and experiences in the comments below!

Email info: Adwarerecoveryspecialist@ auctioneer. net CONTACT ADWARE RECOVERY SPECIALIST TO SPY ON YOUR CHEATING PARTNER SMARTPHONE

WhatsApp info:+12 723 328 343

Uncovering your wife's phone secrets through the skills of a adware-like ADWARE RECOVERY SPECIALIST is a delicate and potentially unethical endeavor that should be approached with great caution. These so-called "sneaky ways" often involve highly sophisticated technological methods to bypass security measures and access private communications and data without the knowledge or consent of the device's owner. A skilled web recovery specialist might utilize advanced hacking techniques, exploits in mobile operating systems, or specialized surveillance software to surreptitiously monitor your wife's online activities, read her text messages and emails, track her location, and even retrieve deleted files - all while leaving little to no trace of their intrusion. However, engaging in such invasive and underhanded practices not only violates your wife's fundamental right to privacy, but can also severely damage the trust and integrity of your relationship if discovered. Rather than resorting to these underhanded tactics, it would be far wiser to have an open and honest discussion with your wife about any concerns you may have, and work together to address them through ethical, consensual means. Building a foundation of mutual understanding and respect is essential for the long-term health of any marriage. For help, Contact ADWARE RECOVERY SPECIALIST through: Email info: Adwarerecoveryspecialist@ auctioneer. net