Parents: When your child spends a lot of time with the PC and doesn't want to interact with you, you have some reflection to do before you turn off the internet and nag them for things all day. Chances are, they don't like being with you but don't want to say it, either, because of the kind of things they know you will say and think if they do it.

And for the love of everything that is holy, do NOT turn the internet off! That pisses them off even more!

Maybe I'd have told you how much I hate being forced to be with you if it didn't mean I'd get guilt tripped about it.

Being around the people who pretend that you are a fucking machine that only needs material things in life and does not at all need emotional support at least in the early parts of your life and deflecting every legit argument for the things you stand for with "Muh Feelingz" makes them seem even more pathetic than they are. They manage to be an inspiration to everyone who doesn't know them, yet fail to be the persons their children have any respect for.

It's as if children never imitate their surroundings at all...

Today I had a reflection with an client and they surprised me with a present. They wanted to thank me for the hard work and effort I made.

Wauw! It just keeps me motivating to work hard and keep my clients happy!

To be a good developer, you must thrive in chaos, and have an insatiable desire to turn it into order.

All user input, both work tasks and actual application input, is pure fucking chaos.

The only way to turn that input into anything usable, is to interpret, structure and categorize it, to describe the rules for transformation as adequately as you can.

Sometimes companies create semi-helpful roles to assist you with this process. Often, these people are so unaware of the delicacy of the existing chaos, that any decision they make just ripples out in waves leaving nearly irreparable confusion and destruction in its path.

So applications themselves also slowly wear down into chaos under pressure of chaotic steak-holders which never seem to be able to choose between peppercorn or bernaise sauce for their steaks.

Features are added, data is migrated between formats, rules become unclear. Is ketchup even fucking valid, as a steak sauce?

The only way to preserve an application long term, is refactoring chaos into order.

But... the ocean of chaos will never end.

You must learn to swim in it.

All you can hope to do is create little pools of clarity where new creative ideas can freely spawn.

Ideas which will no doubt end up polluting their own environment, but that's a problem for tomorrow.

So you must learn to deal with the infinite stream of perplexed reactions from those who can't attach screenshots to issue reports.

You must deflect dragging conversations from those who never quite manage to translate gut feeling into rational sentences.

You must learn to deal with the fact that in reality there are no true microservice backends. There are no clean React frontends. There are no normalized databases. Full test coverage, well-executed retrospectives, finished sprints -- they are all as real as spherical cows in a vacuum.

There is no such thing as clean code.

There is only "relatively cleaner code", and even then there are arguments as to why it would be "subjectively relatively cleaner code".

Every repository, every product, every team and every company is an amalgamation of half-implemented ideals, well-intended tug of war games, and brilliantly shattered dreams.

You will encounter fragmented shards of perfect APIs, miles of tangled barbed documentation, beheaded validator classes, bloody mangled corpses of analytical dashboards, crumbled concrete databases.

You must be able to breathe in those thick toxic clouds of rotting technical and procedural debt, look at your reflection in the locker room mirror while you struggle yourself into a hazmat suit, and think:

"Fuck yes, I was born for this job".

It's such a lovely day, sun is shining, think I'll sit outside with my laptop and a beer and continue working on personal project.

(...goes outside)

It's too bright, can't see shit, plus working on two screens is easier

(goes back inside)

Code is reflection of your soul. Consider whether your soul is shit.

At McDonald's.
Ignore the reflection, I know I'm good looking.

How often do you clean your iMac's screen ?

Me : null

Half life 2 runs smoothly in a 12 year old PC with Nvidia 8500, 1 GB RAM, and a dual core.
A FPS with wavy water reflection, body physics and huge designed maps which is updates every fucking frame.

Today I can't run smoothly an IDE with 8 GB of RAM and 4 cores.
A program which only reacts to events stutters if I write at more than 3 letters per sec.

I wanna go back. Can we go back? Lets keep the new hardware and go back with the software pleeeease.

WTF is up with open-source projects using emojis in their commit messages... FUCKING emojis..

I get it, programming is fun and a hobby to many, but can we also keep at least a minimum level of professionalism here.

WTF is a wheelchair or bento emoji at the beginning of a commit message supposed to mean? Why the hell even bother to use it in the first place? There is no fucking reason for this retarded shit.

Is this what happens when activist developers get out of their way to make programming "inclusive"?

It is your personal project and so if you want to use emojis it is OK, I respect that (not really) but I can't trust your code, your commitment, or the quality of your work if I see those dumb Unicode characters there.

Git commit messages are not a game. Be playful with comments in code or your readme.md file but git messages should be a clear reflection of the changes not what a teenager's phone vomited on the keyboard.

-Look at super hacky code for 30 minutes
-Ask yourself, how did this ever work, guy must have been an idiot
-Check annotations, you committed it
-"Dear God past self, what have you done..."

Had my online persona drawn by a great artist who goes by meowyin.

I think it's pretty damn good reflection of me.

Self(programmer) reflection 🙄

A dev team has been spending the past couple of weeks working on a 'generic rule engine' to validate a marketing process. The “Buy 5, get 10% off” kind of promotions.

The UI has all the great bits, drop-downs, various data lookups, etc etc..

What the dev is storing the database is the actual string representation FieldA=“Buy 5, get 10% off” that is “built” from the UI.

Might be OK, but now they want to apply that string to an actual order. Extract ‘5’, the word ‘Buy’ to apply to the purchase quantity rule, ‘10%’ and the word ‘off’ to subtract from the total.

Dev asked me:

Dev: “How can I use reflection to parse the string and determine what are integers, decimals, and percents?”
Me: “That sounds complicated. Why would you do that?”
Dev: “It’s only a string. Parsing it was easy. First we need to know how to extract numbers and be able to compare them.”
Me: “I’ve seen the data structures, wouldn’t it be easier to serialize the objects to JSON and store the string in the database? When you deserialize, you won’t have to parse or do any kind of reflection. You should try to keep the rule behavior as simple as possible. Developing your own tokenizer that relies on reflection and hoping the UI doesn’t change isn’t going to be reliable.”
Dev: “Tokens!...yea…tokens…that’s what we want. I’ll come up with a tokenizing algorithm that can utilize recursion and reflection to extract all the comparable data structures.”
Me: “Wow…uh…no, don’t do that. The UI already has to map the data, just make it easy on yourself and serialize that object. It’s like one line of code to serialize and deserialize.”
Dev: “I don’t know…sounds like magic. Using tokens seems like the more straightforward O-O approach. Thanks anyway.”

I probably getting too old to keep up with these kids, I have no idea what the frack he was talking about. Not sure if they are too smart or I’m too stupid/lazy. Either way, I keeping my name as far away from that project as possible.

Hardware of laptops today.
Displays: Glossy screens everywhere. "Hurr durr it has better colors". Idgaf what colors it has, when the only thing I can see is the wall behind me and my own reflection. Make it matte or get it out.
Touchpads: Bring back mechanical buttons. Haptic feedback dying with touchscreens/surfaces is a tragedy. "But we can have bigger touchpad area without buttons" ...why? the goal shouldn't be 1:1 touchpad vs. display ratio. It ain't a bloody tablet.
Docking stations: Some bright fucker figured out that they can utilize USB C. That thing keeps falling out with slightest laptop movement disconnecting all peripherals (guess why microUSB had those small hooks?). Also it doesn't have sufficient throughput, so the 5 years old dock can feed 3 full HD monitors just fine and the new one can't.
Keyboards: Personally I hate chiclet. And it's everywhere, because "apple has it so we must too". But the thing I hate even more is retardation of the arrow keys (up and down merged into size of one key), missing dedicated Home/End/PgDwn/PgUp buttons and somebody deciding the F keys are not needed and started replacing them with some multimedia bullshit.

My overall feeling is that this happens when you give the market to designers and customer demand. You end up with eye candy and useless fancy gadgets, with lowered ergonomy and worse features than previous generations of the same hardware. My laptop dying is my daily nightmare as I have no idea with what on the current market I would replace it.

One of my theoretical CS teachers always complains and makes it sound like everything around him is an annoyance to his existence
- being late or in a bad mood? His pregnant wife is very tiring (good ol' haha women are hormonal much?)
- having to create and correct exercises for us (students) is a nuisance because it's so much work and we're not supposed to be spoon-fed (which makes the whole learning experience very demotivating)
- every explanation start is continued by at least 3 changes in the explanation itself, which makes everything super-confusing
- all his helpers are incompetent and not rising up to his expectations

Someone needs some self-reflection

Unity3D Game Dev Interview

Interviewer: What is reflection and why would you use it?

Me: Gives overview of system and how I've used it in games before.

Interviewer: Sorry that was a trick question, Reflection is really dangerous and slow. You need to go back and learn the basics.

Me: ???...

A huge portion of Unity is built upon Reflection based systems, the entire Monobehaviour base relies on it. Their events system uses it, animation and timeline. I guess their team needs to go back to the drawing board.

How is this person a senior dev?

...i just remembered why I have a MasturbatorPattern repository on my bitbucket, why is it named that way, and what it does.

It's one of the core abilities of that magical AI i've mentioned in my previous rant. And it's called that way, because of how it works:

The Agent has some objects (as in, class instances) available to it, and wants to get some other kind of object. So it inspects by reflection ("touches") all objects around itself, inspecting their public functions, building up a plan/path/tree of "this function takes the object I have as input, and returns this other object which this other function of other object takes as input and returns this different object, which...." etc, etc, until the final function returns the object the Agent wanted to get in the first place.

And then it goes and "does" all those functions, in that order piping the parameters through.

So first it touches them (second layer of metaphor - linux finger command), and then it does those which output (ejaculate =D) something useful to it.

Therefore, MasturbatorPattern =D

Not sure if my sense of humor is just weird or outright unfunny.

So this is an update of the afore mentioned IT related RPG I am making. I have settled on the title "Lords of Bullshit: a tale of corporate incompetence".

I need some ideas guys. I have Java, C, Python, PHP, bash and git as skill types, but I need spells for each.

For example in C I have malloc and dealloc as spells (revive and death spells).

I am having trouble with Java spells. I am trying to come up with things that focus on OOP or reflection and meta programming, but I am having trouble.

Any ideas? Also, anyone want to help with some sprites? All of the sprites the character generator can make are medieval looking.

Here's a real tip for people new to the industry.

It's one of those things that's been said over and over again but very few can really seem to employ. I suggest you learn it /well/.

You are not your code. Criticisms of your code, ideas, or your thought processes, is not a criticism of YOU. You absolutely cannot take criticisms of your work personally.

We are engineers. We strive to seek the best solution at all times.

If someone has found a problem with your code or with an idea or whatnot, it is coming from a place of "this is not the best solution", NOT "you're an idiot".

It's coming from a place of "I'm closing this PR because it is not a change I feel suits this project", NOT "I'm closing this PR because it's coming from a woman".

It's coming from a place of "This feature request is ridiculous/this bug is not actually a bug", NOT "you're a fucking idiot, fuck you".

It's coming from a place of "I've already had to address this in a number of issues before and it's eaten up a considerable amount of my time already", NOT "I don't even know you and this I don't have time for a nobody".

You do not get to be bitchy to maintainers because they denied your request. It's not a reflection of you at all. But if you're arguing with someone who has maintained a piece of code for almost a decade, and they're telling you something authoritative, believe them. They're probably smarter than you on this subject. They've probably thought about it more. They've probably seen their code used in many different places. They have more experience than you with that codebase in almost all cases.

Believe me, if we cared about who was behind all of the issues, pull requests, etc. we get, we'd get NOTHING done. Stop taking shit personally. It's a skill, not a defense mechanism. Nobody has the time to sugar coat every little thing.

Let's normalize directness and stop wasting time during technical discussions into opportunities for ego-stroking and circle-jerking and back-patting.

oh, it got better!

One year ago I got fed up with my daily chores at work and decided to build a robot that does them, and does them better and with higher accuracy than I could ever do (or either of my teammates). So I did it. And since it was my personal initiative, I wasn't given any spare time to work on it. So that leaves gaps between my BAU tasks and personal time after working hours.

Regardless, I spent countless hours building the thing. It's not very large, ~50k LoC, but for a single person with very little time, it's quite a project to make.

The result is a pure-Java slack-bot and a REST API that's utilized by the bot. The bot knows how to parse natural language, how to reply responses in human-friendly format and how to shout out errors in human-friendly manner. Also supports conversation contexts (e.g. asks for additional details if needed before starting some task), and some other bells and whistles. It's a pretty cool automaton with a human-friendly human-like UI.

A year goes by. Management decides that another team should take this project over. Well okay, they are the client, the code is technically theirs.

The team asks me to do the knowledge transfer. Sounds reasonable. Okay.. I'll do it. It's my baby, you are taking it over - sure, I'll teach you how to have fun with it.

Then they announce they will want to port this codebase to use an excessive, completely rudimentary framework (in this project) and hog of resources - Spring. I was startled... They have a perfectly running lightweight pure-java solution, suitable for lambdas (starts up in 0.3sec), having complete control over all the parts of the machinery. And they want to turn it into a clunky, slow monster, riddled with Reflection, limited by the framework, allowing (and often encouraging) bad coding practices.

When I asked "what problem does this codebase have that Spring is going to solve" they replied me with "none, it's just that we're more used to maintaining Spring projects"

sure... why not... My baby is too pretty and too powerful for you - make it disgusting first thing in the morning! You own it anyway..

Then I am asked to consult them on how is it best to make the port. How to destroy my perfectly isolated handlers and merge them into monstrous @Controller classes with shared contexts and stuff. So you not only want to kill my baby - you want me to advise you on how to do it best.

sure... why not...

I did what I was asked until they ran into classloader conflicts (Spring context has its own classloaders). A few months later the port is not yet complete - the Spring version does not boot up. And they accidentally mention that a demo is coming. They'll be demoing that degenerate abomination to the VP.
The port was far from ready, so they were going to use my original version. And once again they asked me "what do you think we should show in the demo?"

You took my baby. You want to mutilate it. You want me to advise on how to do that best. And now you want me to advise on "which angle would it be best to look at it".

I wasn't invited to the demo, but my colleagues were. After the demo they told me mgmt asked those devs "why are you porting it to Spring?" and they answered with "because Spring will open us lots of possibilities for maintenance and extension of this project"

That hurts.
I can take a lot. But man, that hurts.

I wonder what else have they planned for me...

I'm currently one of two "pen testers" for the anticheat system of a game.

It all started a few days ago when the developer handed me the obfuscated package and told me to go at it. No big deal, I've bypassed it before the obfuscation, so I just changed some imports and sent in the screenshot.

Fast forward 100+ hours, it's turned into a cat-and-mouse game. He sends us (the testers) an update, we break it within hours. We show him what we exploited and he attempts to fix it. Rinse and repeat.

Finally, today he patched the one hole that I've been using all this time: a field in a predictable location that contains the object used for networking. Did that stop me? No!

After hours of searching, I found the field in an inner class of an inner class. Here we go again.

Worst possible coworker ever, narcisit beyond belief.... When something new arrived, sealed, he would open asap, break it (audibly and visibly) in front of everyone and proclaim it came in broken from the manufacturer.... He was absolutely incapable of reflection, logic or compassion in any way.

Building a wheel is great.
Building a steering wheel is also great
Building a brakes pedal is amazing.

Making them work asynchronously - not that good of an idea is it...

Who the fuck thought separating data stream (copying bytes) from stream control (when does the stream start/end) is a good idea...?

- open a connection
- send data to the stream
- send() returns
- close the connection

Apparently, the send() does not copy the data and returns. Instead, it enqueues the data copying task end returns. When does the actual copying start? IDK. When does it end? IDK. Can I close the conn? NO!

This thing is UNUSABLE. And I'd riddle it with reflection-based workarounds if it weren't for the static methods.

Fuck!

We were running an obfuscator as part of our build pipeline, but also were not. I discovered we had disabled every rule, and after asking around it turns out that the obfuscator broke the app (because of reflection and things I won't go into).

So I turned it off.

An hour later the CTO came to me and said to put it back. "We have to obfuscate, put it back."

"But... it wasn't doing anything, other than slowing the build down."

"I don't care, we HAVE to run obfuscation. It's in our contract with the client."

...

"not sure if we can meet those salary requirements, but I'll get back to you"

JK they just send me the code challenge, no idea of what salary to expect. scratch that one off the list.

meanwhile in another prospect i have had not just multiple interviews, but then add on two additional 'prep' and 'post' interviews for each of the ORIGINAL interviews i have to do with the recruiting company REEEEEEEEEEEEE

honestly it's not a good reflection of what is really valued at these companies - paper pushing over getting to work... ok

WEVE ALREADY TALKED FOR HOURS JUST MAKE A DESICION: GIVE ME AND OFFER, OR DON'T AAAAAAAAAAAAAAAAAAAA

Trying out Reflection in C#, feels so much more intuitive than in Java!

Upon reflection, I think that the amount of math I learned in school pales in comparison to the amount I learned about LaTeX. I could pretty reliably recreate the textbook rendition of the problem. Maybe it's just me but just knowing the solution felt too abstract. I want a solid looking execution of it.

I'm graduating today so I don't know how relatable this is for everyone else. I'm just reflecting.

I was so annoyed by my acne over the past few years that today I went and got the entire area of my facial skin blasted with laser. Now, a several microns thin veneer, containing all that ugly pore openings, is removed.

Isotretinoin, benzoylperoxid, all failed. But I'm not afraid of trying newer methods. Now, serums will be used to grow new skin differently than it might have grown back on its own.

When it grows back, another laser will be used to destroy sebaceous glands. Blackheads and bumps will be physically impossible. A new skin. Even. Glowing. Artificial. Absolutely flawless, absolutely perfect. What a nice reflection of my vision on every thing I make.

When god was sitting in its room, chewing on a donut and designing the world we live in, he never thought much of humans. He got bored and went for a smoke with other gods of other worlds. Little did he know, there was a knock on his door, and a consequential rush of anxiety in realization that it was no fellow god friend, but a human. A human of the generation that figured out Theory of Everything, CRISPR and immortality. Desperate, dirty apes dared to trick silicon sand into thinking, and now they're there, not to talk, but to kill him, a privileged astral plane kid who fell short of those apes who figured everything out on their own.

Disease is natural. Death is natural.

Eternal things are artificial.

I was being interviewed by a tenured Java Dev for a position of android Dev in a big company. it was a glass walled cubicle, and I could see in the reflection that he was browsing stack overflow and asking me the questions. My answers, although correct, didn't match with the accepted answer in stack overflow. sigh. felt good to be rejected.

While working, I suddenly noticed my own reflection on monitor
*starts thinking*
"I should get a haircut"
*starts coding again*
😐

Someone used reflection when he brewed this whisky.

My definition of hell?
Being forced to debug nested callbacks abusing global variables & closures generated from from reflection...

- Launch the new version of the system I have been refactoring for 2 years and counting, then ceremoniously burn (literally) the legacy code as well as the cluster fuck of hardware it runs on.

- Decrease my stress + bus factor by bringing another up to speed on my code & the new version (his cluster fuck now).

- Pay attention to & take better care of health, my wrists in patricular.

- Find a mentor and mentor someone else.

- Get out of crisis management mode and find the time to write tuts, experiment and live a little.

- Find & join a local dev meetup, maybe make a local dev friend.

- Book leave and actually take it, preferabbly without having to take my laptop to the beach - actually, preferabbly at least have the choice to take a offline vacation.

- Sort through the drives containing ALL the code I have ever written, migrate the usefull interesting bits to Github.

Phew, that bit of self reflection was intense! I'm adding a cron to my server to sms & email me this rant in a year to remind me what hope looks like.

Solved a problem while maintaining backward compatibility using reflection... Then i had to spend half an hour to justify using reflection.

Reflection is your friend (just don't overuse it)

Poor Mr. Squishy working as a window stopper, since some clever folks at the property management department, after months of nagging to get blinds so that the light reflected doesn’t interfere with my (light in general, not direct sunlight).

They installed the blinds in front of the window, so it can only be opened a few centimetres… Well done! Well done! I have to choose, either slightly warmer air than I prefer, or bothersome light reflection in all of my monitors.

I don’t know if I would call it a quirk of the language or serious abuse of it :P

But I managed to get a null ref exception when comparing a local int variable to an int parameter to the same function in C#.

Since a local or parameter of type in cannot be null and I compared the variables them self and dud not try to access any property on them (and no extension method or implicit case or similar) my first thought, along with all colleagues that chipped in to help, was that this should not be possible.

Turns out the method was called through reflection and in that part it injected null as the base object to call the method on.

Since local variables actually are referenced through the parent object this was what was causing the null ref.

That took some time to figure out.

Does anyone practise code reading and comprehension? If so, are you able to share your idea?

I try to find how to read code faster with retention and comprehension. It is much like speed reading, but I am reading code.

Here is my journey so far:
Stage 1:
When reading code, I literally each word in line as comment. I though it will help me to understand better. It did, but the retention was not strong enough.

Stage 2:
After reading each line, I will close my eyes for 1-2 seconds and do a reflection what I just read. Better understanding, but comprehension still not good.

Stage 3:
After reading each line, I use my own words to describe what it does and write down as comment. I found that I have better comprehension

Stage 4:
Constantly, remind myself to describe with my own words. this speeds up the reading and understanding.

To be honest, I am still trying.

Don't remember who but someone here told me once, when I mentioned that I do java now, "wait till you get to reflection..."
Well it's time to suffer

Working for a company with solid procedures really makes me appreciate how important they are. Knowing someone will be scanning through my pull request made me *really think* about appropriate layout and commenting. Before I could submit any old code and the other programmer wouldn't give a monkeys.

I guess that's a poor reflection on my performance but, I'm working on it

We had this new guy working and we assigned him some work to do. We gave him some time to find the way into the code and figure things out on his own.

Instead of doing that, he wrote a paper of 20 pages why WPF would be way better than what we are doing now. There were many flaws in his document as well. Also on day 2 he used resharper to format some code file. Bye bye annotate! His argument was that resharper knew better. But, our code also uses some reflection, so that got broken. He didn't knew what reflection was and assumed resharper "fixed" it.

He doesn't work here anymore now, he felt he wasn't taken seriously. This is just one of many examples of him though 😂

As a junior dev from a sysadmin and security background, this is a list of software development concepts I never seemed to truly understand but hope to(rated from most intimidating to least):

1) Frontend web development and all the huge world of javascript frameworks and tools. - It's more overwhelming than the political geography of the Holy Roman Empire in the Middle Ages.

2) Machine Learning, Deep Learning and A.I- too much math that fucks with my brain.

3) low-level programming(kernel,drivers) - sounds extremely interesting but the code in assembly/C/C++ looks like Linear A Minoan hieroglyphics.

4) Rx(insert language here) - I never get why it is useful or why someone invented this. Seems interesting though.

5) Code Reflection - sounds like Thelemic magick.

6) Packaging, automation, build tools, devops, CI, Testing -seems too complicated. I just want to run an executable at the client or make a web app that does something. Why all this process?

teach meta language concepts: what is an operator, literal, constant, statment, control flow. the recursive nature of staments. then go into objects/methods vs structs/procedures. then teach some java. then go into reflection concepts. then use reflection for something simple. then teach a bit of perl. then let them build something in python. Anyone who can pass through that will know how to Program in whatever you give him/her.
I wish my teachers talked about the meta programing, instead on focusing on the minutia.

# Honestly, no intention of starting a holy war;

Been a Linux guy for over 9 years spanning school, college and my previous job years;

Now I have to use Windows at my new job. I know very little abt this os and it has never been among my strong skills (only used it for gaming);

What's more intriguing is that my current company's entire infrastructure is Windows based - which I had no idea that it could be possible at such a large scale;

I don't know about what I feel about this whole thing. But what I know is that I don't wanna shy away from it. I love the job and the role (only just if it was Linux, it'd be perfect).

Just need this for a future reflection:
Can anyone confirm if it's the same with other investment banks/financial services institutions etc. infrastructure?

Fuck me. Upgraded a java project from java 11 to java 17 and now the shitload of power mockito tests are all failing because they locked down reflection. Now I have to upgrade to junit 5 and waste my life looking at these stupid unit tests. I sense a large purge approaching.

A little reflection on the relationship between me/my dad/computer:

When i was younger my dad showed and taught me how to work on his (10 - 15yrs+ old) laptop running windows xp. Soon we got a simple desktop pc (those ones that took nearly a minute to start). i remember my dad sayin something like "don't download anything cause (the pc will brake/it will be a virus/...)", I don't remember exactly ... but i know that i still did it (being fucking nervous😅) and it went well😌. later me and my little sister would go to "spielaffe.de" several times until getting some kind of "virus"😅😅.
Time passed and i got passionate about pc's (programming, trying Ubuntu, reading about internals of a pc,...). It didn't take long that i passed my dad's knowledge and so here i am studying CS😎.
In the end, regarding my dad:
first he was the master i looked up to, then he became the buddy i talked to and asked for problems, then ... he remained the light user who would like to return to his windows xp era and asks me first as his personal google when something happens out of his "comfort-zone"😅😌.
And sometimes i believe my dad is becoming incompetent for pc's😂😅

I've realized that I was acting like an annoying asshole in the past on devRant and I apologize for that behavior.

Some people deserved it and some didn't. Some companies deserved it and some didn't.

I guess the time for a change has come. I will be more careful from now on.

On a side note: I have a different username now.

It was a very depressing experience with you, -ANGRY-CLIENT-. Have fun on the other side. :)

Every year I get more than bit wiser and every year there is more that I don't know.

Looking at my reflection on the laptop screen while it is being upgraded, and thinking that the career choice i made 11 years back was probably not a great idea.
I don't understand amazon-cloud, very little knowledge of DBs, can't write a single JS class without googling, block chain are meh, don't even know python, working with a team that abuses my framework in front of me, working 12 hour shifts for last 3 years... What is my life's purpose?

1) Never be afraid to ask questions.

There are so many instances of situations where assumptions have been made that shouldn’t have been made, resulting in an oversight that could have been rectified earlier in a process and wasn’t.

Just because no one’s asking a question doesn’t mean you’re the only person who has it.

That being said, it’s really important to figure out how to ask questions. Provide enough context so that the audience for your question understands what you’re really asking. If you’re trying to troubleshoot a problem, list out the steps you’ve already tested and what those outcomes were.

2) When you’ve learned something, try to write about it. Try to break it down as though you were explaining it to a child. It’s through breaking down a concept into its most simple terms that you really know that you understand it.

3) Don’t feel like you have to code *all of the time*. Just because this is what you’re doing for a living doesn’t mean that you have to make it your life. Burnout is real, and it happens a lot faster if it’s all you do.

4) Find hobbies outside of tech!

5) Network. There are a number of great communities. I volunteer for and am a member of Virtual Coffee, and can vouch for that community being particularly friendly and approachable.

6) Don’t let a company pay you less than industry standard and convince you that they’re doing you the favor of employing you.

7) Negotiate salary. Always.

8) If you’re a career transitioner, don’t be afraid to talk about your previous work and how it gave you experience that you can use in programming. There’s a whole lot of jobs that require time management, multi-tasking, critical thinking, etc. Those skills are relevant no matter where you got them.

9) If it takes a while for you to get a gig, it’s not necessarily a reflection on you or your abilities.

10) Despite what some people would say, coding’s not for everyone. Don’t feel like you have to continue down a road just because you started walking down it. Life’s not a straight path.

!Rant:
Why did you guys decide to become a developer?

I became a developer after finding out that I loved wrecking my brains on complicated puzzles to keep me from getting depressed. After a while I figured out that I'm the person that needs to be challenged to actually be able to enjoy something and start to overthink the little things.

Here are the things I wreck my brains over on a weekly basis.
- programming
- research on complicated subjects
- magic the gathering

Reading through one of my posts I’ve realized how much ego programmers can actually have. Guys, some of you have already mastered or grasped more than just the foundations of the industry standard languages, as well as developed a very solid intuition behind some design patterns and a solid understanding of some frameworks and libraries, say NumPy, say React... we get it.

You don’t have to be such condescending assholes and be offended by some of the jokes we, programming beginners, make to release stress or just to have fun.

You already have some amazing developer and engineering skills. Do not ruin it with such a detrimental attitude; I make this post because I myself have made this mistake, and I still do to this day. But if what I’ve felt reading your comments is what non-programming people feel when around me, I wouldn’t be surprised if I found that some people hated me or just wanted to kill me.

I don’t know if this will get downvot’d or if more people think like this. But I needed to share this, even just as a reflection of my very own attitude.

Thank you for your time,

D.

I would not consider myself an overachiever by any means, but I must say, I'm quite satisfied with my contributions this year at the new (relatively speaking) job. I got to go back to writing code almost every day, all day, and that sure as hell beats being in meetings all the goddamn time.

After doing some self reflection today, I realized that I could finish college (I passed every exam), but the amount of time I spent for college (basically the whole day each day) is too much to handle for me.

Note to future me: If you blame yourself for why you didn't continue, it's because of the lack of time, freedom and calmness of your mind. Otherwise you would have went literally insane.

Trust me, your early version is in that phase right now, and I know it better than you do.

"I don't think we should be playing with our privates {variables} like that" - framework designer

= context =
It was noticed that we have too many setter functions to change private variables just to do unit tests. So we had a small meeting to discuss what to do about this.
Options:
- don't do the test
- ignore till another time (ie: keep the functions till its a problem)
- put the variables into a provider
- use reflection (the above quote was a reaction to this option)

Have you ever had to fire someone? or get someone fired?

I’m thinking about a time when I should have made sure a guy was fired.
He had no business leading a project, and I knew this early on when he suggested connecting a public frontend straight to a clients’ ERP.
I wasn’t on his project but I ended up cleaning up his mess when shit hit the fan.

After a particularly social weekend it’s important to have a motivational buddy to get you back in the game!
You all heard of the debugging duck, meet the motivational duck...

“If your duck can see its reflection - your not developing enough” ;)

Today I just considered that Excel isn't just a random spreadsheet product name, it's the *word* excel. To _excel_ at something

I need to do more self reflection 🪞

I don't get why annotations are even allowed for local variables.

Reflection doesn't even work for local variables.

What's the entire purpose to annotate!!!
Am I missing something!!!

Things I wish I knew when I was younger:
- no matter how clean your teeth are, bad breath won't go away until you clean your tongue. Buy a tongue cleaner and use it after you brush your teeth
- whitening toothpastes don't work, while desensitizing ones work well.
- after you brush your teeth, spit but do NOT rinse!
- when brushing your teeth, keep the toothbrush angled 45 degrees. The bristle ends should touch the area where your gums meet your teeth.
- use sunscreen every morning.
- don't waste money on acne-treating products unless they contain salicylic acid, benzoyl peroxide, tretinoin or adapalene.
- if you want to lose weight, you have to eat MORE, not less. But, that “more” should be protein.
- showering every morning feels like “humanity restored” thing from Dark Souls. Also, clean your damn room and wash your damn windows.
- APS-C DSLR cameras make no sense. For their weight, you can get a full-frame camera, and for their price you can get an APS-C mirrorless cam that will be way lighter.
- If you want a damn thing, save up and buy that damn thing. Don't buy the alternative thing you don't want. You'll be asking “what if” till you either die or buy the original damn thing.
- people aren't replaceable, but many people can fit their designated role. Not being able to replace your ex-boyfriend with his exact copy doesn't mean no one else can be your boyfriend.
- try a MacBook & iPhone as soon as you can to check whether it's your thing or not, because if it is, oh boy are you in for a treat.
- added sugar is evil, but it's beneficial for the economy. It makes you fat, so you need a car, so you buy fuel. Also, you feel guilty because you're fat, so you buy diet products & things to compensate because you hate your reflection in the mirror. You also pay medical fees to treat your newly developed health problems, and you die a day before retirement. Everyone makes a buck on you eating added sugar but you.
- you can use the freshly removed sticker to remove the sticky residue left by that same sticker.
- static typing doesn't solve jack shit.

I worked on a project that used an archaic homegrown library written by a consultant that had zero documentation, tons of reflection and here is the kicker... the consultant refused to give us the source code as it was "his intellectual property" so we couldn't make any sense of how to actually use it. Moreover, he worked remotely so the timezone difference between us meant that any questions we had took ages to get answered. Glad to be away from that project now.

If there's one thing I'd gladly kill with fire, then pass it over a steamy steamroller, then burn it a tank of hot fluoroantimonic acid, is every fucking Java library that returns null instead of throwing a meaningful exception.
Is it really that difficult for you to throw an exception anyway, then let ME figure out if I can ignore it or not?
Thanks to you, now I have to do super messy reflection things just to figure why did you return a null.
I'm not your fucking psychologist trying to pull your inner secrets. But I have to be, for the sake of stability of my app. Which already has its own mess of problems on its own.

when i was still studying "web integrator", didnt know shit about programming and just went there to be with a friend.
I quickly got bored, sick and tired of it all being procedural style so i decided there must be something better...
i spend loads of time but eventually developed my own almost fully fledged oop framework, minus polymorphic relationship support, events( i was on the way to that but called it messageBus ),
implicit route bindings
and the routing was based on reflection of controller methods following rest naming.
also i hadnt discovered composer, yet.

by the time i discovered composers, i also discovered laravel, which is my now prefered framework.. :)

God damn it, if you (libGDX) have default values for public methods then make those constants public. Now I am writing wrapper and I either create my constant with same value as your private one, or do some reflection black magic which will probably break after obfuscation. *sigh* Going with my copy of the constant, not happy about that...

I know a few fascinating people. They didn't invent anything historical, they didn't start a revolution, they didn't even get their names on a newspaper. They are just very very smart. And they use their intelligence to improve the world. Each have their own companies or projects, which don't do anything magical but they work really well. And these are nice people. People who have a lot of friends, and whom their kids look up to, not because they're heroes but because they're so bright and kind that those capable of self-reflection feel inferior in their company. But most importantly, I appreciate these people because, while being conscious, intelligent and aware of civilization's problems as well as their own, they are still satisfied and sometimes even happy.

"Business owners need to realize that their design is a reflection of their business even if it is not intentional. If you don’t care about your design then your design is telling people that you don’t care about your business. " - Marco Suarez

So... I’ve recently started a new role, and luckily I’ve established myself as someone that knows his shit (more or less) TM.

I’m leading the charge on tech debt, and raising issues about it, first on my radar is the monstrosity of their approach to app config.

It’s a web app, and they store config in a key-value table in the database.

Get this. The key is the {type}.{property} path and this is fetched from the database and injected *at construction* via reflection.

Some of these objects get instantiated dozens of times per-request. Eurgh.

Not a Number by "Evil Corp". Gf at the reflection

Apple finally released my stickerpack!

can you see me?
do I look creepy?
can’t see my reflection, probably looks messy
is it spooky?
wanna see a movie?
I can walk through walls, you don’t have to pay for two seats

... worst drunk coding experience?
none. or to be more precise, all of the three of them I had. I can't code drunk, i hate doing it, i hatw even thinking about doing it when drunk.

so after those initial three attempts i don't try to do it again, ever.

BUT, best coding experience while high?
ALL OF THEM.
some of the best pieces of code I wrote i did when I was high. my mind goes into overdrive at those times, and my thinking is not lines/threads of thought, but TREES of thought, branching and branching, all nodes of each layer of the tree coming to me AT ONCE, one packet == whole layer across all of the branches.

and the best was when one day, in about 14 hour marathon of coding while high, i wrote from scratch a whole vertical slice of my AI system that i've been toying around in my head for several years prior, and I had all of the high-level concepts ALMOST down, but could never specify them into concrete implementations.

and I do mean MY ai system, my own design, from the ground up, mixing principles of neural networks and neuropsychology/human brain that I still haven't seen even mentioned anywhere.

autonomous game ai which percieves and explores its environment and tools within it via code reflection, remembers and learns, uses tools, makes decisions for itself for its own well-being.

in the end, i had a testbed with person, zombie and shotgun.
all they had pre-defined in their brains were concepts of hunger and health. nothing more.

upon launching it, zombie realized it wants to feed, approached oblivious person, and started eating it.

at which point, purely out of how the system worked, person realized: "this hurts, the hurt is caused by zombie, therefore i hate zombie, therefore i want to hurt it", then looked around, saw the shotgun, inspected its class by reflection, realized "this can hurt stuff", picked the shotgun up, and shot the zombie.

remembered all of that, and upon seeing another zombie, shot it immediately.

it was a complete system, all it needed to become full-fledged thing was adding more concepts and usable objects, and it would automatically be able to create complex multi-stage, multi-element plans to achieve its goals/needs/wants and execute them. and the system was designed in such a way that by just adding a dictionary of natural language words for the concept objects on top of it, it should have been able to generate (crude but functional) english sentences to "talk" about its memories, explain what happened when, how it reacted, what it did and why, just by exploring the memory graph the same way as when it was doing its decision process... and by reversing the function, it should have been able to recieve (crude) english sentences that would make it learn what happened somewhere else in the gameworld to someone else, how to use stuff and tell it what to do, as in, actually transfer actual actionable usable knowledge to it...

it felt amazing to code for 14 hours straight, with no testruns during that, run it for the first time after those 14 hours, and see that happen.

and it did, i swear! while i was coding, i was routinely just realizing typos and mistakes i did 5-20 minutes ago, 4 files/classes ago! the kind you (and i) usually notice only when you try to run the thing and it bugs out.

it was a transcendental experience.

and then, two days later, i don't remember anymore what happened, but i lost all of that code.

and since then, i never mustered enough strength and resolve to try and write the whole thing again.

... that was like 4 years ago.
i hope that miracle will happen again one day...

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

DynamoDbMapper ISSUE

There were multiple pojos which maps with one of our DynamoDb table with slightly different schema (leveraging nosql).

For one of the pojos, while populating one of the attributes, it was always throwing some weird exception and no one had any idea about it.
An intern was assigned to fix it in case some new pair of eyes can observe something weird about the pojo.

Later, I realized that the way DynamoDbMapper behaves inside a pojo is very particular and hidden.
A method was declared as public instead of private in the pojo, and DynamoDbMapper while mapping the pojo to the table with reflection, it said that this attribute (a substring of the method name) cannot be converted.

Finally, it was just a single word change from PUBLIC TO PRIVATE.

It's too early to be asking these questions today:

Are your DB schema changes checked into source control?

What branch are they checked into?

Why are the schema changes checked into one branch, but deployed to a completely different database?

Is my CI pipeline deploying incorrectly? Oh, you manually deployed changes.

Are your DB changes in source control an accurate reflection of what you actually put in the staging database?

Why not?

Can I just cherry-pick update my schema with your changes from the staging database?

Why is there a typo in your field name?

Oh. Why is there a typo in the customer data set? Don't they know how to spell that word?

Why is the fucking staging database schema missing three critical tables?

Is the coffee ready? I need coffee.

Why is the coffee not ready yet?

What's going on in DevRant this morning?

What project am I working on now anyway?

Did my schema update finish yet?

Yup, it finished. Crap. Where the hell do I keep those backup files?

What's the command line to restore the file again?

Why doesn't our CLI tool support automated database restores?

I can fix that. What branch name should I check the CLI tool into?

What project was I working on this morning again?

!!rant
!dev

I think I'm trash and I NEED to restart life.

Jesus Christ, Minecraft source code (with forge in this case) is such a clusterfuck of spaghetti logic. It's especially fun when it uses a lot of reflection and dynamic class lookups...

What it feels like when you tell a newbie coder about reflection and all the stuff you can do with it.

Will in the future exist a language called JavaScriptScript named because of JavaScript's popularity although it has nothing to do with it?

I lost my cool and got into a trembling furious mode yesterday. The outcome is an ugly pile of mess. After calming myself down and reflecting, this is what I end up telling myself this morning.

I let myself touched shit. When someone was throwing shit at me, I went and touch it and throw it back instead of avoiding it. I created a shit storm instead of a cleansing rain. And now not only me, everyone around me has to breath in shit air.

I reminded myself I got supporter stickers and stripe from fsfe.

I placed one on my laptop and spotted that those stickers are reflecting mirrors.

Spent next hour trying to make recursive reflection photo.

It’s damn hard to place it correctly on such small area using hands only

3am and I am thinking of building a stand.

I know that DI(dependency injection) is probably just another good pattern out there like many others, but dear lord have I been burned on it with acumatica. Acumatica just loves having friggen magic crap everywhere with no damn explanation(*may be in a blog post somewhere but that’s no replacement for good documentation).

I believe they use AutoFac in C# on an asp.net server. They love to utilize reflection and injection and in turn the server takes multiple minutes to startup whilst it dynamically registers everything, as well on any individual pages.

Development is a pain in the ass on this damn system.

I’m constantly having to dive into the damn code using dotpeek to understand what the fuck they are doing and it’s often friggen stupid shit. They like to reinvent the wheel a fair bit.

How to know if someone is C# ninja?
when you read his code you’ll find a lot of Foo<T> , TModel, TKey and a lot of reflection

I would hack the heck out of Roslyn Analyzers! Everything that could be f*ckin detected at compile-time _would_ be f*cking detected at compile-time. All those freaking config files usages, or attributes/reflection. Analyzers for everything, with sensible error messages! (Although I realize I that's overstretching the concept of unlimited time)

Six different .NET solutions using reflection to interface with each other just made OOP look a lot like spaghetti code.

For F^^k sake Microsoft give us some way to protect .net code from easy reflection / decompilation ..... Obfuscation just doesn't cut it.

WTF?
Just found this code:
"It is assumed that all 'static final String'-Attributes of this class are a key in the property file (which is validated by reflection)."

SO REFACTORING YOUR FUCKING MAGIC NUMBERS WITH A MEANINGFUL CONSTANT MADE THE APP CRASH. ASSHOLE.

Index, currIndex and i are all -1.

The real index is a postfix on a string in another class passed through several layers of reflection and delegates.

Tomorrow will be better. Tomorrow will be better. Tommorow will be better....

Bugger me Quarkus is quick. Pretty bloody quick even when not using Graal native, but with that... damn.

Looks like I need to skill up. These new Graal-native-friendly, reflection-free Java web frameworks are really coming into their own. Spring really needs to respond quickly, otherwise it's going to become the slow legacy framework of yesteryear, if it's not already.

January is always the month of feedback and reflection. I dont mind going to the office x times a week and standing still on the highway every day. But if they are asking me to spend my own time on a course now they can lick my balls. Im already working for two years without a raise. Ik not continuing like this. I understand everyone needs to improve but if im exhausted at the end of the day by all the buzz in the office i dont have energy left for additional schooling. Im learning on the job. Deal with it

So,I bought a new laptop (comes with windows preinstalled). I quite like macOS and (some) linux distro. "I'll triple boot, suffer to hackintosh it, install either Ubuntu GNOME or Elementary OS and leave Windows 10" I thought.
Upon further reflection "But why would I need win 10?"
// searches "Why use windows?"
// google "Why is windows so bad"
" Nah, I haven't used win in a long time, I'll give it a go. We were buddies when it was XP. It can't be that bad, it must be better now."

//A few days later it finally arrives
//proceeds to use win10
//unnecessarily complex registration
//makes a new 16gb i7 sluggish

"Let's see what's running on the background"

//downloads ubuntu GNOME, hastily

(1)and thee who shalt seeketh the I shalt envision the abstract reflection, a delay, a mirror, of thy future;

God bless reflection.

"And here we are, perfectly-tuned Ferraris in a demolition derby."

Just a reflection ending my 16th year as dev.

Quote from HBO's Genertion Kill miniseries - Master Sergant Brad Colbert

C++ standard commitee please give us compile time strings and reflection. Why are you taking so much time?

Thinking about a new annotation:
@JavaCondom

on function: it puts "... throws Exception " at the end
on class: reflection puts "... throws Exception" on every goddamn function

It could have global app property which makes appends every exception with a reassuring message like: "There is so much java code out there already, that this shit will never ever end"

I was about to implement a new feature (which I will call feature X), but I was not sure which branch feature X should be implemented on. Because of different products, there are a lot og branches around.

I was going to implement feature X on branch A, but that branch was currently not working, and someone was working on fixing it.

I was told by my boss to branch out from branch B as feature X would be merged in there later anyways.
And so I did.

After I am nearly finished with feature X I discover I need feature Y from branch A. Feature Y is not yet on branch B, but is scheduled to be merged in some time soon.

So I can't really finish feature X before that point, and I am told by colleague 1 I should have implemented feature X on branch C, because feature Y is there and branch C will be merged into branch B soon.

However, I found out that this has happened before.

First, colleague 1 was told to implement feature Y on branch A. This is the real implementation, the one I need. After he had spent a week implementing feature Y, he was told by colleague 2 that the feature should be implemented on branch C, which is branched off from branch B (I think). So he had to spend a day or two to move feature Y to branch C, but he still kept feature Y on branch A, because all branches will eventually be merged into branch A.

After a week or so, colleague 3 asks about feature Y and is told that the feature is on branch C. But colleague 3 need the feature on branch D, which is branched off branch B for some weeks ago.

I don't know all the details here, but colleague 3 ends up implementing a version of feature Y on branch D and he is happy.

I don't know how much time was wasted because of wrong information from management, but I have no intentions of wasting more time. I'll wait for the merge of branch C into branch B.

If this rant makes no sense, that's just my reflection of management some times.

I love management.

The number of concurrent transformations impacting more than half of the codebase in Orchid surpassed 4, so instead of walking the reference graph for each of these I'm updating the whole codebase, from lexer to runtime, in a single pass.

In this process, I also got to reread a lot of code from a year ago. This is the project I learned Rust with. It's incredible, not just how much better I've gotten at this language, but also how much better I've gotten at structuring code on general.

Interestingly though my problem-solving ability seems to be the same. I can tell this by looking at the utilities I made to solve specific well-defined abstract problems. I may have superficial issues with how the code is spelled out in text, but the logic itself is as good as anything I could come up with today.

How should you override Equals in Java?

We have model classes with lots of fields and the we override the details equals to compare all the fields. I guess like doing a deep comparison.

And in all these classes SONAR is complaining about lots of ifs, complexity, etc.

And it's killing the analysis time... Old issue never fixed because whoever setup sonar was too incompetent to bother asking, researching, or fixing...

Is there a better way to override the equals to get the same result but without triggering SONAR issues?

Pretty sure this is a solved problem. And well if the top of my head, is just create a Util method that uses reflection like
Boolean equals( Object a, b, Class class)
foreach (String f: class, getFields()) {if !compare(class.getField(f,a),class.getField(f,b)) return false; }

return true

The lack of a meta-language in c# can be a pain in the ass, I have to jump through hoops to generate something like python's decorators, not to mention having to generate il to overcome some limitations of reflection when dealing with value types.

Not a horror. I'm rewriting services.

It started as a help request. I was asked to help with completing a service dealing with push notifications which was a research prototype. It was suggested to keep core part of it, but it was so awful that I just removed all files and wrote the service from scratch.

The second service had been developed for more than a year by a junior and then by our manager who wanted to complete it as fast as possible, without taking care of code quality. Then I was asked to take over the project and after some time I agreed with one condition: I'll have 1 month on takeover. But when I looked at the code, it became clear that it's much faster and better to rewrite everything except API and database than to takeover existing code.

The third service dealing with file exchange was working, but the junior who wrote it advised to rewrite it because it was a very simple service. So, I initiated rewriting, designed a new API and reviewed the final result.

And now I'm dealing with the fourth one. It was developed in my team but not under control. Now, when I "inherited" this complicated project, I decided to rewrite it because it should be simple, but it doesn't. It features reflection, layers inside layers, strange namespaces, strange solution structure. And that's after months of refactorings and improvements. So, wish me luck because I want to keep part of the infrastructure, but I don't know if it's possible.

You're bugging me. I'd like to open an issue and fix -you- this. If you need help debugging feel free to ask, reflection might help.

As a developer who loves to do back-end work, I pause and do some self-reflection every time I'm asked to make some user interface decisions. It's not as easy for me.

Whenever the test is to see what clarifying questions they'll ask.

Give a dev in an interview setting a vague task that needs refining before it can be meaningfully attempted, and 95% of them will just plough in and start designing / writing code.

FWIW, I don't personally like these sorts of questions in interviews, as the situation is very different to reality (and therefore I don't believe it's a true reflection of what questions a user may ask in a work environment.) They are *very* common however, and a lot of devs don't seem to be aware.

Upgrading my tech skills.. Once again I feel my personal my personal dev environment and told are much more up-to-date than what I use at work.... Though the book Kim reading is on TDD and was written 3 years ago.

Maybe I should read another on in cloud services and ML... but don't have any motivation for these topics.

I need TDD for work because now we're emphasizing unit test coverage...

I usually only use manual functional tests to verify the final outputs as either the testing framework is broken (JS) or I don't have time to relearn the frameworks for the particular language...

Anyway got off topic... So questions after:

1. Do you ever feel your technologically always more ahead than what you do at work and essentially you bring skills to the job but you don't learn much out of it?

2. How do you test? I actually got into a bit of a argument/discussion with my colleagues about how to implement unit tests. Apparently there are 2 ways to test? Black box vs WhiteBox. She said she tests only Public methods using mock inputs, dependencies. She read online and seems there is an opinion that should only test public functions and if you can't then your app is designed incorrectly, not separated enough.

For me I test the private functions individually (WhiteBox/Java reflection) because the public one is like generateReport and as a whole is like a Pachinko machine, too many unique paths that would need a test case for.

So thoughts? Yes sorry for turning it into a remake I guess...

Hello word!
I'm in the middle of a C# reflection study session.
Anybody have exercises ideas to share? (:

So I am currently updating a application from play framework version 2.5 to 2.6 and am working through all the dependency updates... I feel like I am playing whack a mole.
and now there are suddenly ClassNotFoundExceptions because the classes are not in the same classloader as before and the access over reflection doesn't work anymore.

Anyone got some tips why the classloader is differing?
I think it might be because some dependency conflicts or such.

There is a new Java library very useful for building frameworks and in this library there is a particular classpath scan engine that deserves attention as it is original and powerful.
The peculiarity of this engine is the possibility to search classes over a path or the runtime classpath by concatenable and nestable criteria by exploiting the power of the lambda expressions on the native Java reflection elements such Class, Field, Method, Constructor, Module, Package, Annotation, etc ... thus giving the possibility therefore to carry out searches without limits and for any criterion that can be immaginated: this library is called Burningwave Core, it is open source and on the official wiki on github there are a lot of examples.

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