Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "evolve"
-
True Story. Good rant bad pitched.
Just a small information before: In Germany, if you want to be a softdev and want to learn it, you can either go study IT or you can have a apprenticeship, which is 3 years with 75% of work in a company which will pay you (around 1K / month) and 25% in a school.
I work for this city-govermant company nearly 1 year now. Around 6 month into I told them I which to have a intern for 3 years (apprenticeship) at my site. Most likely because I really enjoy to teach.
My boss agreed to this very fast, told me it's a good idea, it would be a new way for our company to evolve. In Feb 2019, when we had interviews with candidates, we decided for one and I made a resource plan for most of 2019 in which I blocked 3 weeks for the start of his apprenticeship in July (2 weeks ago) because I knew he is a kid, 18 years, etc, never coded etc.
7 days into his apprenticeship my boss called me and my boss to her and told me there is a project which should be done by end of june and why it isnt finished.
It was the same project which I had ressources for 4 weeks in June but the department didn't come up with proper feature requests etc. so another department got the time from me. I told my boss exactly this: not my fault that it isn't done, showed her emails, reminders etc.
I also offered her to spend a weekend soon if everything is there now, but she told me: no. It has to be done ASAP. ASAP means, start now, don't stop until its done.
I told here, I have a intern on my site, I blocked the time.
She told me one sentence I will never forget:
"If your intern is blocking this project, he has to go. You decide. Now."
I was so surprised that I didn't even got any word out then "yes, I will start." I was shocked by this words and her decision to quit this young guy.
Just to give a a bit more background: we hired him in Feb 19 for Jul 19. If we would quit him right now, he would most likely not have any chance on the market for another apprenticeship and has to wait for Jul/Aug 20 and 1 year without job, money etc. He even moved to our city for this job...
So I moved back to my desk and today, 2pm, I finished all of the project, nearly 50h+ work done in 5 days, so he can stay.
What the actual fuck...15 -
Fuck code.org. Fuck code. Not code code, but "code" (the word "code"). I hate it. At least for teaching. Devs can use it as much as they want, they know what it means and know you can't hack facebook with 10 seconds of furiously typing "code" into a terminal. What the fuck are you thinking when you want me to hack facebook? No, when I program, it's not opening terminal, changing to green text and typing "hack <insert website name here, if none is given, this will result to facebook.com>" Can you just shut the fuck up about how you think that because you can change the font in google fucking docs you have the right to tell me what code can and can't do? No, fuck you. Now to my main point, fuck "code" (the string). It's an overused word, and it's nothing but a buzzword (to non devs, you guys know what you're talking about. how many times have you seen someone think they are a genius when they here the word "code"?) People who don't know shit don't call themselves programmers or devs, they call themselves coders. Why? It fucking sounds cool, and I won't deny that, but the way it's talked about in movies, by people, (fucking) code.org, etc, just makes people too much of a bitch for me to handle. I want everyone reading this rant who has friends who respect the fact that YOU know code (I truly believe everyone on devRant does), how it works, and it's/your limitations, AND that it takes hard work and effort, to thank god right now. If you're stuck with some people like me, I feel you. Never say "code" near them again. Say "program." I really hate people who think they know what an HTML tag is and go around calling themselves coders. Now onto my main point, code.org. FUCK IT. CAN YOU STOP RUINING MY FUCKING AP CS CLASS. NO CODE.ORG, I DON'T NEED TO WATCH YOUR TEN GODDAMN VIDEOS ON HOW TECHNOLOGY IS IMPORTANT, <sarcasm>I'VE BEEN LIVING UNDER A ROCK FOR THIRTY YEARS</sarcasm>. DO I REALLY NEED ANOTHER COPY OF SCRATCH? WAIT, NO, SCRATCH WAS BETTER. YOU HAD FUCKING MICROSOFT, GOOGLE, AND OTHER TECHNOLOGICAL GIANTS AND YOU FUCKED UP SO BAD YOU MADE IT WORSE THAT SCRATCH. JUST LETMECODE (yes I said that) AND STOP TALKING ABOUT HOW SOME IRRELEVANT ROBOT ARM DEVELOPED BY MIT IS USING AI AND MACHINE LEARNING TO MAKE SOME ROBOT EVOLVE?! IF YOU SPEND ONE MORE SECOND SAYING "INNOVATION" I'LL SHOVE THAT PRINT STATEMENT YOU HAVE A SYNTAX ERROR UP YOUR ASS. DON'T GET ME FUCKING STARTED ON HOW ITS IMPOSSIBLE TO DO ANYTHING FOR YOURSELF WHEN YOUR GETTING ALL THE ANSWERS WITHOUT DOING ANY WORK AND THE FACT THAT JAVASCRIPT IS YOUR FUCKING LANGUAGE. <sarcasm>GREAT IDEA, LETS GET THESE NEW PROGRAMMERS INTO A PROFESSIONAL ENVOIRMENT BY ADDING A DRAG AND DROP CODE (obviously we can say it) EDITOR</sarcasm> MAYBE IF YOU GOT THIS SHIT UP YOUR ASS AND TO YOUR BRAIN YOU'D ACTUALLY GET TO PRPGRAMMING IN YOUR ADVANCED AP COURSE. ITS CALLED FUCKING CODE.ORG FOR A REASON32
-
!dev && I'm fucking pissed
Bloody fucking mosquitos, FUCK YOU!!
If you couldn't evolve your shitty self over billions of years to be able to consume decent food instead of MY FUCKING BLOOD, then just let me fucking kill you already and eat my own fucking supper in peace!
MOTHERFUCKING PARASITIC ABOMINATIONS OF LIFE!!!16 -
I just released a tiny game for iPhone!
It's basically an attempt to mix 'Heroes of Might & Magic' and mtg.
In the screenshot my terminal says 'helloworld.cpp'. That's right, this is my first c++ program and I don't care how crappy you think this game is, I'm super proud of myself!
I've always worked in data science where managers assume I know how to code because there's text on my screen and I can query and wrangle data, but I actually didn't know what a class was until like 3 years into my job.
Making this game was my attempt to really evolve myself away from just statistics / data transforms into actual programming. It took me forever but I'm really happy I did it
It was brutal at first using C++ instead of R/Python that data science people usually use, but now I start to wonder why it isn't more popular. Everything is so insanely fast. You really get a better idea of what your computer is actually doing instead of just standing on engineers' shoulders. It's great.
After the game was 90% finished (LOL) I started using Swift and Spritekit to get the visuals on the screen and working on iPhone. That was less fun. I didn't understand how to use xCode at all or how to keep writing tests, so I stopped doing TDD because I was '90% done anyway' and 'surely I'll figure out how to do basic debugging'. I'll know better next time...22 -
FUCK WEB DEVELOPMENT.
Seriously, what the hell. Things evolve so goddamn fast and someone new to the field can’t even grab something to start with. Once you start understanding something it fuckin changes and something else takes it’s place.
Fuck this shit, I’m out.18 -
Me last year: Fuck yes! PWA's sound amazing! Can't wait to see what they can evolve into!
Me now: Fuck PWA, fuck those 'apps' with the thick end of a rake5 -
Some of the penguin's finest insults (Some are by me, some are by others):
Disclaimer: We all make mistakes and I typically don't give people that kind of treatment, but sometimes, when someone is really thick, arrogant or just plain stupid, the aid of the verbal sledgehammer is neccessary.
"Yeah, you do that. And once you fucked it up, you'll go get me a coffee while I fix your shit again."
"Don't add me on Facebook or anything... Because if any of your shitty code is leaked, ever, I want to be able to plausibly deny knowing you instead of doing Seppuku."
"Yep, and that's the point where some dumbass script kiddie will come, see your fuckup and turn your nice little shop into a less nice but probably rather popular porn/phishing/malware source. I'll keep some of it for you if it's good."
"I really love working with professionals. But what the fuck are YOU doing here?"
"I have NO idea what your code intended to do - but that's the first time I saw RCE and SQLi in the same piece of SHIT! Thanks for saving me the hassle."
"If you think XSS is a feature, maybe you should be cleaning our shitter instead of writing our code?"
"Dude, do I look like I have blue hair, overweight and a tumblr account? If you want someone who'd rather lie to your face than insult you, go see HR or the catholics or something."
"The only reason for me NOT to support you getting fired would be if I was getting paid per bug found!"
"Go fdisk yourself!"
"You know, I doubt the one braincell you have can ping localhost and get a response." (That one's inspired by the BOFH).
"I say we move you to the blockchain. I'd volunteer to do the cutting." (A marketing dweeb suggested to move all our (confidential) customer data to the "blockchain").
"Look, I don't say you suck as a developer, but if you were this competent as a gardener, I'd be the first one to give you a hedgetrimmer and some space and just let evolution do its thing."
"Yeah, go fetch me a unicorn while you're chasing pink elephants."
"Can you please get as high as you were when this time estimate come up? I'd love to see you overdose."
"Fuck you all, I'm a creationist from now on. This guy's so dumb, there's literally no explanation how he could evolve. Sorry Darwin."
"You know, just ignore the bloodstain that I'll put on the wall by banging my head against it once you're gone."2 -
!rant
So a few colleagues left the company leaving me as the most experienced person for our project and I hated to do all the babysitting for the new colleagues and trying to hold on against the new levels of pressure.
But I have just realized, that this is a great opportunity for me to evolve from a regukar worker to a leader.
Also this opens the door to creating my own company. I haven't felt this excited in a long time.3 -
Just received this beauty by a customer. They "made some changes to the HTML". WTF?! Also, alongside was another docx called "printscreen.docx" with only a picture and nothing more in it. I would really like to laugh, but it would evolve into sad, depressing crying.
(Sorry for the "screenshot", but this is on a very restricted Winshit laptop we got from the company who buys our stuff.)4 -
"The aim is to develop highly robust data streams so we have the flexibility to build and evolve the user interface without having to change code in the API"
Oh, is that all you need?4 -
"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot6
-
Hey Designer/Developers, I got a question for you. Yeah, you 👇🏽
When working on a project codebase that is expected to grow and evolve heavily. How do you usually split up your CSS (SASS, LESS etc) in a good way to take into account all the different device sizes?
I am not asking how it is done but more about the design of the code. This would be for a production codebase to be released.
Do you use large blocks broken down by media...
(Media width) {
~site code
}
(Other media) {
~same site code with diff sizes
}
Or do you do individual media queries inside css classes...
.className {
(Media size) {
}
(Other media) {
}
}
Or a mixture of both?
If it is a mixture of both then how do you decide which way to go about structuring the code.
I have been endeavouring to greatly improve my CSS and have done so. But this question has been bugging me. Both sides seem to be a bit sloppy and my programmer side is fighting the repeatitipve code.
Note: all code examples are gibberish and only intended for visualization.17 -
A little over a year into my job at my current company back in January, I have a yearly meeting with my manager to discuss the progress I’ve made and to talk about what’s next. This is the meeting where we are supposed to discuss a potential pay raise but it’s the last topic of a predefined agenda.
So we spend a couple hours talking about how work has been for me. I started there as a junior developer with very little experience in the field but was quickly able to jump into a project with a fairly large codebase to help out the only other developer working on the project. Before long they’re so happy with me that they actually put me in charge of the application, which means my responsibilities evolve toward a whole lot more communication with the client and everything else that comes along with being in charge, including a lot of stress. I also salvaged another application initially developed by another company but that was so bugged it should’ve just been sent to the pits and rewritten from scratch. I was also asked to develop a couple POCs that were satisfactorily delivered.
Anyway, after almost two hours of going over my accomplishments and getting praises from my manager, we finally get to the part where we’re supposed to discuss a pay raise. He immediately cuts me off by saying the subject is not on the table due to the current crisis and our company struggling to make ends meet. I tell him I understand how hard it must be for them but also explain that I know for a fact other companies in the field are still making financial efforts to reward employees they’re happy with. He responds by saying that he’s aware of that, but he also “knows” that those same companies are laying off people that don’t deserve to be laid off despite the fact that they’re receiving government aid to stay afloat.
In the weeks following that meeting, I find out our company is doing the exact same thing my manager was condemning (laying off good people, taking massive advantage of government aid) and all the while not giving anybody a raise.
In any case, I really felt like that meeting was huge waste of time. What’s the point of going over everything I’ve done, congratulating me for my great work and even promising to give me even more responsibility if you don’t want to reward me for any of it? Do you honestly think I’m working hard so I can get a pat on the back or brownie points from you? I’ve got a family to take care of and I am trying to make their lives a little better each day by putting in hard work. But if hard work and climbing the latter of responsibility does not help me achieve that, what’s the point??1 -
I grew up as internet became a thing, so I had a very early exposure to computers. There's actually a video of me crawling onto an old computer which still had a 5.25" floppy drive. By the age of 4 I actually started using it properly, my mum said I once talked about pressing enter in my sleep 😂 I'm glad I was born in
a time (94) to witness technology evolve at such a crazy scale. Kids these days will never know what kind of privilege it was to have a 128MB pendrive 😛2 -
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
/rant2 -
Hmm. So have you ever argued in a job interview? Like really standing your ground? In a technical interview?
Today I had a live coding session with a company I'm interested in. The developer was giving me tasks to evolve the feature on and on.
Everything was TDD. Splendid!
However at one point I had to test if the outcome of the method call is random. What I did is basically:
```
Provider<String> provider = new SomeProvider("aaa", "bbb", "ccc", "ddd", "eee", "fff")
for(int i=0; i<100; i++) {
String str = provider.get();
map.put(str, incrementCount(str));
}
Set<Integer> occurences = new HashSet(map.values());
occurences.removeIf(o -> o.equals(occurences.get(0)));
assertFalse(occurences.empty());
```
and I called it good enough, since I cannot verify true randomness.
But the dev argued that this is not enough and I must verify whether the output is truly random or not, and the output (considering the provider only has a finite set of values to return) occurences are almost equal (i.e. the deviation from median is the median itself).
I argued this is not possible and it beats the core principle of randomness -- non-determinism. Since if you can reliably test whether the sequence is truly random you must have an algorithm which determines what value can or cannot be next in the sequence. Which means determinism. And that the (P)RNG is then flawed. The best you can do is to test whether randomness is "good enough" for your use case.
We were arguing and he eventually said "alright, let's call it a good enough solution, since we're short on time".
I wonder whether this will have adverse effect my evaluation . So have you ever argued with your interviewer? Did it turn out to the better or to the worse?
But more importantly, was I right? :D21 -
There are a couple of them to list! But to sum my main ones(biggest personal heroes):
John McCarthy, one of the founding fathers of Artificial Intelligence and accredited with coining such term(sometimes before 1960 if memory serves right), a mathematical prodigy, the man based the original model of the Lisp programming language in lambda calculus. Many modern concepts that we have in programming where implemented in one way or another from his systems back in the day, and as a data analyst and ML nut.....well I am a big fan.
Herb Sutter: C++ programmer extraordinaire. I appreciate him more for his lectures and published articles than anything else. Incredibly smart and down to earth and manages to make C++ less intimidating while still approaching it with respect.
Rich Hickey: The mastermind behind Clojure, the Lisp dialect for the JVM. Rich is really talented and his lectures behind his motivations and reasons behind everything he does with Clojure are fascinating to see.
Ryan Dahl: Awww shit y'all know how it is. The man changed web development both in the backend and the frontend for good. The concept of people writing their own servers to run their pages was not new, but the Node JS runtime environment made it more widely available to people by means of a simple to use language that was already popular with web developers. I would venture to say that Ryan's amazing contributions to JS made the language better, as it stands, the language continues to evolve and new features that make it overall better keep being added. He is currently building Deno, which would be a runtime environment for TypeScript, in Rust.
Anders Hejlsberg: This dude was everywhere man....the original author of Turbo Pascal and the lead of Delphi back in the day. These RAD tools paved the way for what would be a revolution in the computing world. The dude is also the lead architect and designer of the C# programming language as well as TypeScript.
This fucker is everywhere and I love it.
Yukihiro "Matz" Matsumoto: Matsumoto san is the creator of the Ruby programming language. Not only am I a die hard fan of Ruby, but of the core philosophies that the man keeps as the core of his language design: Make the developer happy, principle of least surprise. Also I follow: minswan which is a term made by the Ruby community that states Mats is nice so we are nice. <---- because being cool to others is better than being a passive aggressive cunt.
Steve Wozniak: I feel as if the man does not get enough recognition...the man designed the Apple || computer which (regardless of how much most of y'all bitch and whine) paved the way for modern micro computers. Dude is also accredited with designing one of the first programmable universal remotes(which momma said was shitty) but he did none the less.
Alan Kay: Developed Smalltalk and the original OOP way of doing things. Smalltalk as a concept is really fucking interesting. If you guys ever get the chance, play with Pharo, which is a modern Smalltalk. The thing is really interesting and the overall idea of Smalltalk can be grasped in very little time. It sucks because the software scales beautifully in terms of project building, the idea of hoisting a program as its own runtime environment and ide by preserving state through images is just mind blowing to me. Makes file based programs feel....well....quaint.
Those are some of the biggest dudes for me. I know that the list is large, but I wanted to give credit to the people that inspired me the most. Honorary mention goes to other language creators and engineers of course, but it would be way too large to list!9 -
It is said that the number of programmers doubles every five years with fresh CS, CE, and EE grads. Assuming that's true, then at any one time over half the developer community are novices in the early stages of their career.
My entire life's been spent in software and I've been in it now for about 15 years and I've seen a lot of people make alot of things and I've seen a lot of people fail at alot of things. My observation is that the doers are the major thinkers, the people that really create the things that change this industry are both the thinker doer in one person. It's very easy to take credit for the thinking the doing is more concrete. It's very easy for somebody say "oh, I thought of this three years ago" but usually when you dig a little deeper you find that the people that really did it. Were also the people that really worked through the hard intellectual problems.
Many people falsely believe that a great idea constitutes 90% of the work. However, there is a significant amount of craftsmanship required to bridge the gap between a great idea and a great product. As you evolve that great idea it changes and grows it never comes out like it starts because you learn a lot more as you get into the subtleties of it and you also find there's tremendous amount of trade-offs that you have to make.
There are certain things you can't make electrons do, certain things you can't make plastic or glass, certain things you can't make factories or robots do. and as you get into all these things, Designing a product involves juggling 5,000 different concepts, fitting them together like puzzle pieces, and exploring new ways to combine them. Every day brings new challenges and opportunities to push the boundaries of what's possible, and it's this ongoing process that is the key to successful product development. That process is the "magic"4 -
*Clears throat*
To everyone who say's they won't release X for Y because Y isn't good at Z (For example, people who don't support games on Linux because Linux isn't as good at gaming compared to windows), go fuck yourself with the wide end of a rake...
Fuck me people piss me off with stupidity sometimes .-.
Thing's aren't going to evolve and get better if everyone just abandon's shit at the first fucking hurdle, remember when windows wasn't good at gaming compared to mac, well that fucking changed pretty quick didn't it...
(If anyone is curious how this came about, I'm am still holding hope for Gamemaker studio 2 to come to Linux but in the mean time though about running it's compiler through mono and building a front end to see if I can even do it but was talking to someone about it and they said I'm wasting my time because Linux is shit for games)5 -
I see a lot of rants on this platform complaining about their boss/management.
About how they don't understand how complicated the development can be of seemingly simple tasks or how they would prefer small estimations over realistic ones.
Is that really the standard in this field of work?
Am I just that lucky to find basically the ideal boss on my first try?
My boss really understands how difficult some tasks can be even if they don't initially seem like it. He listens to my ideas as if they are at least just as important as his own. He can almost think like a real developer and is prepared to give us all tools we could want to evolve.
It is a very small firm and I'm basically the only real developer on this project, but I would follow that man to the ends of the earth.
Can some people please clear my conscience and confirm there are still good managers in this field who really care about their project and their employees/colleagues?6 -
College degree.
I don't have it. Not because I don't like to study or don't like to evolve.
I tried several times go back to college, but unfortunately I don't see myself wasting money and time inside a classroom hours per day for something I can read on a book and learn by myself in few days / hours.
I know there's some subjects it's quite hard and we need some guidance for help us, but, we have the community to ask, forums and a lot information on internet.
OK, but why I'm doing this rant?
Recently I got a good job offer in a good country but my potencial employer and me is facing issues to go trough the process because the country to give me the IT visa requires the college degree.
Sometimes I regret to not have enough cold blood to finish the damn college just becuase of the piece of paper (which doesn't proff anything and we cannot even use to clean the $_@#$"@).
My home country (which is a third world country) is already noticed that and they start doing some laws and visas to ease the hiring IT professionals and they're leaving at companies expanses and responsabilities to verify is a good professional or not, but, the price is high for that. But at least the companies there's a way now to get someone.
And also I start see a loot excelent and genius programmers and others IT professionals which are skipping the degree to see and face same issues as me.
I hope our field finally put a end to this burocracies.12 -
> TheSmartGuy: listen, IHateForALiving, I know you're a frontend developer, but here in the backend...
Just so we're clear: I'm NOT a frontend developer.
I'm a full stack developer.
I just so happen to always end up working on the frontend because you bunch of handless monkeys wouldn't be able to write a webpack config file if your life depended on it.
It's not you taking care of my inability to work on the backend, it's me being relegated to using only half of my skills because you ugly things refuse to evolve. I could take your job in a breath, I wouldn't trust you with writing a css selector.7 -
are there some graphic designers here? 😎
Do you code?
Did you learn some stuff here on devRant? What did you learn?
What do you design mostly?
How do you deal with programmers who don't obey your design specs because they're lazzy fucks? muhaha 😆
how do you think this profession will evolve in the next 10 years?
and you devs, what do you think of us? what are your experiences with designers? good and bad ones?8 -
Ordered some fucking computer glasses (which filter out the blue light). Been having red eyes and excessive fatigue these last months, plus sneaky headaches.
We're in 2018, and fucking delivery companies still think that people are at home waiting for their parcel. They came yesterday, fucking saw I wasn't there, they left a fucking delivery notice when my parcel does not require a signature!! I mean, what's the use of a P.O box if it's only there to host spiders in summer?
Plus on that stupid delivery note they've put a QR code - "please use the given code or scan this QR code to change your delivery options" - which is unreadable, AND they didn't give me the fucking code.
Be flexible for fuck's sake, and evolve with your time. I hate Slowtzerland for that - conservative, late, immuable. Especially in "social" services. 99% of the population is away from home from 6 to 18, time to fucking print that in your brain and get on with it.
Now I might wait until Saturday so I can get them glasses...5 -
ProfaneDB is a database to store Protobuf objects, working on top of gRPC for cross compatibility.
May evolve anywhere towards a "Serverless" kind of solution; a GraphQL to Protobuf interface; may use SQL as backend...2 -
A story from the old days
My father had a fame around he's friends that he understood this nasty business that is computers and in the pre-windows time he was reasonably knowledgeable... But as things evolved he didn't evolve with them so when he's friends asked him to help he would take me to solve the problem...
One day he asked me to see what was the problem with a friend's personal computer. This is a 70+ year old man.
When I get to his computer I do a quick check and see it's too infected with so many viruses to the point it is better to just format and clean install, so I ask him to backup he's files and the next day I picked up the PC and clean installed and setup the all thing...
Not more than 3 months pass and the guy says to my dad the problem was back...
I get there and the antivirus was turned off and the PC was infected... Found it weird but okay, enabled the antivirus, cleaned everything... Back to as new.... This time I instructed him to keep the antivirus always updated and running...
One week later to my surprise: he reports it is all back... Now I am getting tired of this and went to he's browsing history to find out how the hell he is achieving this... Too my surprise the amount of early internet shady porn sites was over the top...
I know had to tell a 70+ year old man how to safely watch porn... But that is not my problem, so I ask him what kind of sites he's going to... He blames he's grandson for using the internet in he's computer... Only problem: he's grandson is 2 years old...
I just set up the bookmarks with some children sites and convinced my father to take a look at that and either instruct the man or the kid on how to watch porn without getting a venereal disease... -
Create something that will take humanity forward. Not just a utility software but make things that'll help solve the biggest problems humans as a society face - poverty, hunger, loneliness, pollution etc. All these problems are on my radar.
The idea is to use science to solve social problems. And not just stop at that. Make things that will help humans evolve into the next evolutionary phase.2 -
The evolving of software engineering is highly dependent on hardware engineering.
If only software engineering would evolve then there would eventually be a point where theres nothing more to do due to the lack of hardware to develop software for.
So its more a question of how you see hardware engineering evolving.
I expect that there will be a point in the future where we have techology which in big scale does dangerous or time consuming tasks. Like for example at nuclear reactors or at other high level security and high risk locations. This of course requires highly sofisticated ai software. -
has anyone written the first flagship software of a company and what happened to the software afterwards?
did you make good architecture decisions or did you just jank and roll with it? how did the software evolve over time? how was onboarding new devs to work on the software? what sorts of issues were there? did the company make it? what were external factors that made making it difficult?3 -
After going through the regular process of talking to HR/Recruitment and passing the casual interview with a team-mate for cultural compatibility, I got the task of grilling a candidate on some technical matters. This being a PHP job, we got to talking about PSRs (PHP Standards Recommendations).
As he seemed to take pride in his knowledge of PSRs, I decided to focus more closely on that.
So we got to a recomendation regarding dependency injection containers. Nothing special, and he seemed to know his stuff. At that point, he made a statement that parts of that recommendation were a bit stupid.
Now, I hate to put people in their place, but his statement did not match what that specific PSR stated. So I gently tried to correct him. The candidate, being on fire thus far, pointed out that I should trust him on this, as he clearly knew his stuff.
Again, I didn't like having to do this, but I also did not like him having a misconception about a topic he was, otherwise, really on top of...
So I asked him to trust *me*, as I was one of the writers who contributed to the standard.
The true test here, of course, wasn't if he knew all the minutia of every standard but how he would react to being corrected.
We, as developers, are wrong all the time. Its how we learn and evolve. So being able to accept that is vital.
Sadly, he did not respond too well and sunk into a bit of a sullen silence. At first I though maybe I'd scared him or that he was afraid of having made a gaff but it soon turned out he genuinly did not like being wrong.
Sadly, I had to advise against hiring him.2 -
working at an MNC is like dating the hottest girl in campus. everyone stares at you, but only you know of the tantrums and the expenses that you have to take.
Every random aunty and uncle I come across gets a wide smile on their face when i tell them my company's parent company name. i goto this temple , and there, one uncle was introducing me to his wife "meet X ji's son , he is at Y company" .
previously when i worked at a startup, most of the time , people were like "huh? what does this company do?" and when i would explain them how our DBs are sending billions of notifications and interaction each second, they would be like "oh , so you work at IT" , YES DUDE, YOU WANNA GIVE YOUR DAUGHTER'S HAND NOW?
And this mentality is sick. i loathe the place where i currently work. i loved my previous org and now am just here coz my mom is too scared to let her son live in a different state.
The only reason a person works in a company is money and WLB. Indian service based MNCs don't give a penny more than basic industry standards. and when they want their employees to be available 2 days a week + x number of days when any CEO , ED or other sugar daddy is coming to office, you get an idea of the shitty Work life balance.
my previous company was a b2b startup, it always paid me more than industry standards and we had wfh until a notification came to enforce hybrid working bh end of 2024. till now not a single person from my team has relocated. All i had to do was to *plan* for living in a state and my mom got cold feet :/
i think so much about my future. i earn decent, so i wanna spend it to live and grow.
i wanna go party at friday nights and go on night outs. i wanna meet this cute school crush at anytime after office and don't worry about the 9 pm curfew. i wanna go look for a new home in a different area and get out of this parking hellhole. i wanna prepare for exams and do a hugher studies from aborad.
everything needs money and growth mindset. money makes money and i am trying to earn every minute. but a chained mind cannot fly . a non growth mindset will not let you evolve. and someone needs to tell it to people who control my every . fucking. action
i have seen people switching from one big name to another. i personally feel that you are just too comfortable in the environment of big names and deliberately ignoring the smaller names which are doing the actual build fast and break reality stuff. reward is proportional to risk and if you are okay with just attributing to a big name, then that's on you20 -
In
https://devrant.com/rants/4221216/...
Hes discussing confidence and I wanted to talk about that for a moment, from a guy who struggled with it a lot growing up.
Half of confidence is headfaking yourself into distracting the lizard brain portion that didn't evolve for the last ten thousand years of rabid human social change and thus detects a bunch of social interactions as varying forms of threats.
Same way NLP works, or stupid shit like seduction, or sales techniques.
It's all about slowing down and distracting yourself with the process.
People that do all this dont realize the trick is you're thinking less because you've slowed down and this comes off as confidence.
Think about it. What do nervous people do? Either talk way less, and/or when they *do*, talk fast and lack certainty. What does confidence techniques and all that shit do? Causes you to slow down, follow process which makes answers clearer usually, and causes you to speak more freely (even if its more structured).
Thats the entire game.
Give yourself time to think and room to answer, to think of a question and formulate a response. Assume nothing while you do so.
One trick I use that boils *all* the other processes down is this: Anything you go to say, pause, look the person in the eye, and wait 1-2 seconds to respond. Remember to blink, and remember to gesture as you normally would.
Treat every conversation as a casual dialogue over coffee with a friend discussing colors of paint for a kitchen. Its a slow process isn't it?
Same thing with any other conversation. People will find you a lot more deliberate, confident, warm and unassuming.3 -
There are some who view software as a social construct (like Pieter Hientjes), and I think it's a valuable perspective. So if we know about the intrinsic brokenness of software, can we deduce sth about the brokenness of human interactions? Did social API's evolve to similar clusterfucks of dead entropy we have to shovel in our brains to get along?
I think the answer is an emphatic yes. And you know what's even making it worse? Software. Y'know there are all these whining about the millenials, and I too have had my experiences with stuff of that category. Like back when we searched a new roommate for our flat, we needed three rounds because people who had said yes suddenly reconsidered. Similarly now when we tried to sell our couch: people tried to push the price. Said they were interested, never showed up at the appointed time. It's like they have been spoiled by Amazon: expecting to buy with one click, for the cheapest price and send back if they don't like. And that is not a generation thing. Those old blokes ranting on the young are just as bad. They are just as lost in antisocial media as anybody else. It's a general erosion of not sticking to civility and courtesy, to the yes or no once said, coz everything is now as flexible and fluid as the digital projections of ourselves transmitted round the globe, changing in realtime.
I fucking hate it. - I'm out like this stupid Tom Cruise character in Oblivion.6 -
How many of you want to live in a world where there's no a standard way to convert numbers to strings among systems?1
-
I hate touchscreens!
Far too often, nothing at all happens when "pressing" a "button", and when something happens, it's not at all what you wanted, it's like touchscreen devices have a will of their own.
Maybe touchscreens will evolve and actually become useful in the future, with a technique for reading input that works for everybody and not just for the majority, and with tactility, i.e. through 3D morphing of buttons, switches and wheels, controls that you can grab, feel and hold on to.
Till then, I'll dismiss touchscreens as the toys they are, no good for anything serious.5 -
I see a major shift coming up im regards of how we continue to evolve the way our applications work in regards to web based solutions. Http was not meant to do the shit that we are doing today, yeah it works, but it continues to feel like a hack. The advent of A.I and WebAssembly will probably make developers more mindful about compilers and truly optimized code. Languages such as Rust are pointing in the right direction in terms of speed and safety and as our computers become more powerful so will our way to communicate with them. Eventually damn near every web based solution will include A.I even when it is not needed at all.
Regardless of what happens. Yo ass is not going to stop hearing about C++, SQL, and Javascript(top kek)1 -
A place where you can evolve your skills, competitive and that you're respected.
And NO FREAKING CLUELESS PROJECT MANAGERS that do not understand how software is "born" and expect you to catch insane deadlines... -
It is with great pleasure that I announce I have just been appointed the CEO of Garalina.
With all those amazing people we have on board, we as a company will carry on delivering what we do best — the entertainment meets therapy. With your support, we can evolve and extend our reach way beyond the select few families we had a pleasure to work with.
Stay tuned!6 -
1. Languages will evolve to make as short as possible in terms of lines of code. Shorter syntaxes all the way.
2. Each platform/part of architecture will have only 1-2 languages to code in. There will be convergence of languages. This is more to do with industry usage. Underground new languages will still continue to flourish.
3. Focus will be more on natural language. Both as research item for understanding humann languages better and possible movement of coding languages in the direction of natural languages. Natural syntax as much as possible.
4. Softwares will be self learning. Every interaction will result in the software to evolve as per your usage. That would mean the same software will behave differently for every user. This will be basis user's interaction.
5. Less physical interaction. More to do with what the user thinks. Intuitive.rant wk127 languages interaction coding coding in future software development ai to overtake humanity soon futuristic future future is now1 -
Binary combinatory logic (BCL) is gonna change the world. Yes, it's an esolang, but its easy to evolve populations of programs written in it. Then, when you have a winner, you can easily embed it in a C binary as a hardcoded arg to your interpreter function. Or use logic to translate it to any other programming language.1
-
I wad looking for a kind of 'internship', i'm an 18y/o high school self-taught programmer, and applied for a job at a small company in my town, with a mention: "I don't wanna be paid, I want just to evolve my skills, by gaining experience". When they called me, the HR girl told me exactly this: "If you can gain 2 years of experience until next month, we will hire you". My face expression changed to a poker one and I asked "How am I supposed to spend 2 years in 2 weeks?" and she responded: "I don't know, I told you what they told me to tell you"... Anyone else who got into a situation like this? How is this even possible?8
-
It's okay to be afraid of learning new things but this shouldn't stop you from actually learning it. Industry is fast changing and you need to evolve yourself with it.
-
I am getting my first apartment next Saturday, and it's awesome. And I was thinking of buying a great desktop computer because my laptop is getting old and I want a real desk with a real modern computer, also as a symbol of my new life coming. It would have costs me around 1300€, but guess what, I just spent that yesterday to pay the real estate agency, the deposit, and the first rent for that apartment 😭 I guess I'll have to wait again for that new pc...10
-
Finally made the time to chase my passion for game development. Tried with UE4 in the past but didn't have the time to evolve. Heard that Unity is easier for mobile game development so, Unity, here we go! My journey starts with an Android game project. I'm equipped with a book (of guidance) and a keyboard/mouse (of fantasy and adventure). Wish me luck!
-
Realized what the meaning of life was yesterday.
Because the real meaning of life is yet to be found, there is an interim one — to do everything to help us exist as longer as possible as a species. So spread peace, empathy and forgiveness. If we live long enough to formulate the theory of everything, understand human brain and evolve past/patch our brains to avoid being greedy violent fucks, maybe then we'll find the real meaning. The longer we exist for, the better our chances are.
So, the ideal human according to kiki is:
- one that doubts everything and is free because of that. Freedom is doubt.
- one that has a habit of denying themselves pleasures. Without restraining themselves, one turns into a greedy, violent beast.
- actively contributes to the world peace & spreads peace among their peers, as true impact is immeasurable, and who knows, maybe butterfly effect will turn one “I'm sorry, I was wrong” into avoiding nuclear catastrophe.
There are adversaries that benefit from us bickering and fighting each other. They want to divide us. Let's deny them that. I announce that I won't engage in verbal battles and teardowns anymore.
Sometimes, static typing is beneficial. Sometimes, unit tests are necessary. JS, CSS and web platform as a whole are not perfect. JS is not perfect. Apple does anti-consumer stuff. Not all rich people deserve hate. Sass has its uses. Tailwind CSS has its uses. React has its uses.
Peace10 -
Sometimes people want to be too smart. If you want to consume a handful different restful API, it might make sense to abstract away some common functionality in your client implementation — yet to assume they follow the same convention in how their URI is built is borderline insane.
All I wanted to do was to change one API to a newer version, and now the implementation breaks for at least two other because it was done in an Abstract class and now I have to untangle that mess.
In some cases code duplication wouldn't be that bad. Even if an otherwise unrelated API seemingly share the same contract, still assume it has its own contract. You never know how those API evolve and I proclaim they will evolve towards breaking your assumptions.1 -
at one point documents were useful things to align people to the relevant information to the tasks they must complete for everything to work out
now documents are a ritual, and relevant information is even forgotten or omitted and considered secondary to the document existing and looking like a professional document
I wonder if this is how all industries evolve
at one point there were people who knew what they were doing, they created processes so nobody is left behind
and over time, whoever made the processes, the spirit for their existence, is forgotten
and you're left with empty rituals, so devoid of their original function, the humans subjected to these things, crushed by them, can't even discern what their usage is
evidently if you put monkeys in an enclosure with some apples up a tree with a mechanism that if a monkey goes up the tree and takes an apple it sprays all the other monkeys in the enclosure with water
the monkeys will learn to pull down any monkey trying to go up the tree, because they don't wanna get sprayed
and this will keep going, generations will change and yet they'll still religiously pull down the monkeys, in a ritual... nobody remembers why only that their parents did this to them, so they do it to others
if you take the trap away, they never figure it out, which is how this story is typically told
but regardless of if the trap is there or not
wouldn't you wanna know and see it for yourself instead of following empty rituals?!
and what of people who erroneously view things as traps, and pull people down, but they were just seeing things?!
self limiting myths to doom the ages! -
Nothing much to ready today, keep scrolling..
I just asked you to keep scrolling, I am using this space to think out loud...
Damn you bloody rebel.. whatever..
Finally after a rough week, festivals, interviews, work stress, and pending tasks, I got a free weekend for myself to be with myself.
I managed to do bare minimum at work. My new line manager isn't quite pleased with how team and I am functioning but whatever.
On Fridays, I usually end the day early and start with personal tasks. I managed to finish some long pending activities.
Today, I was able to do a deep cleaning of digital housekeeping. Sorted some clashes with parents. manage to de-stress and relax my stiff neck muscles.
Apart from that I guess, I am all prepared to interview and get hired for a company on foreign land. I am confident that I can relocate to EU.
And for now, I am actively pursuing two of my hobbies, Music and Finances. I love managing my finances and learning more about technical aspects of audio and listening to more and more music.
I feel happier, relaxed, and calm. Having things under control is such a wonderful feeling.
And I am slowly building a framework to earn, manage, invest, and grow my finances. It's turning out really well. I have setup the base infrastructure.
For music, I have figured the fundamentals and now I will go out buy myself an DAC/AMP to build a portable rig.
This shit is so awesome and makes me happy. I am able to socialise at the end of each day so that keeps me going during the lock-down phase.
I have figured the top key and important things to do at work for my profile and I actually enjoy those.
1. Product discovery - talking to users/customers and finding their pain areas and opportunities to build the solution
2. Product vision/strategy - Dreaming on how the product would evolve and laying out a solid plan to materialise those dreams.
3. Roadmap and prioritisation - this should be self explanatory
4. Success metrics - I really want to get into data and I am getting opportunities to do so. This is super fun. This will help me analyse and show the impact of the what we are building and measuring it while making sure that LT recognises my and my teams' efforts.
I want to and I will excel these 4 keys skills of my profile and be more efficient at my job.
This will give me more time to pursue my hobbies (which will change over time and want to enjoy them the most while I am at them).
Guys, after a rough 2021, the end of the year seems promising with a lot of leaves and short vacation coming up.
Apart from all this, what is more important here is that I got the career and life clarity that I was struggling with for past few months.
For whoever has read till here, YOU ARE BLOODY AWESOME and thank you from the bottom of my heart for being there for me always.
I am grateful to be a part of this community and have awesome friends like you all who have been with me though my ups and downs since 2016.
LOVE YOU ALL :)3 -
Here is my problem. The team I'm on has developers from other areas that were "put" into a new team. Two use "structured programming" but the requirements make me think we need "domain driven design". How in the world can I get them to evolve into another mindset while still meeting the deadline?1
-
ChatGPT is blocked in my country, I had to get creative to finally create an account but holy shit it was worth the effort. That thing is freaking fast and I am honestly a bit worried about how these technologies will evolve in the future. Well time to make my boy GPT write me some code 🤪12
-
So... An MVP is nothing that a prof of concept that you have to develop for yesterday but then it should evolve and be maintained and upgraded forever (keeping the profit and ahead of competition) .
No wonder developers quit!3 -
Vinegar didn't work, time to test honey.
Let's see if autocomplete is nice enough to persuade some of these mongrels to evolve from dogs to chimps and actually document the code they write.1 -
Next year goals:
1. Learn how to use Macintosh.
2. Learn better Linux.
3. Finish an android app that I am too bored to finish.
4. Evolve social skills for Humans. -
It took 8 million years for a monkey to evolve into a man. But still, a monkey went to space before a man.
-The Internet2 -
Design in Motion: Real-Time Rendering's Impact on Architecture
Architecture, a discipline that once relied heavily on blueprints, models, and lengthy render times, has undergone a revolutionary transformation in recent years. The advent of real-time rendering technology has fundamentally altered the way architects visualize, present, and interact with their designs. This paradigm shift has not only enhanced the creative process but has also empowered architects to make more informed decisions and create immersive experiences for clients and stakeholders.
Real-time rendering, a technological marvel that harnesses the power of high-performance graphics hardware and advanced software algorithms, allows architects to generate photorealistic visualizations of their designs in a matter of milliseconds. Gone are the days of waiting hours or even days for a single rendering to complete. This acceleration in rendering time has not only expedited the design process but has also encouraged architects to explore multiple design iterations rapidly.
One of the most significant impacts of real-time rendering on architecture is the ability to visualize a design in various lighting conditions and environmental settings. Architects can now instantly switch between daytime and nighttime lighting scenarios, experiment with different materials, and observe how their designs respond to different seasons or weather conditions. This level of dynamic visualization offers insights into how a building's appearance and functionality evolve throughout the day, contributing to more holistic and thoughtful design solutions.
Moreover, real-time rendering has transformed client presentations. Architectural concepts can now be communicated with unprecedented clarity and realism. Clients can virtually walk through spaces, observing intricate details, exploring different angles, and even experiencing the play of light and shadow in real-time. This immersive experience fosters a deeper understanding of the design intent, enabling clients to provide more targeted feedback and make informed decisions.
The impact of real-time rendering on collaboration within architectural teams cannot be overstated. Traditionally, architects and designers would need to wait for a rendering to complete before discussing design changes or improvements. With real-time rendering, team members can make adjustments on the fly, observing the immediate effects of their decisions. This seamless collaboration not only enhances efficiency but also encourages interdisciplinary collaboration as architects, engineers, and other stakeholders can work together in real-time to refine designs.
The integration of virtual reality (VR) and augmented reality (AR) into the architectural workflow is another transformative aspect of real-time rendering. Architects can now create VR environments that allow clients to step inside their designs and explore every nook and cranny. This not only enhances client engagement but also enables architects to identify potential design flaws or spatial issues that might not be apparent in 2D drawings. AR, on the other hand, overlays digital information onto the physical world, facilitating on-site decision-making and construction supervision.
Real-time rendering's impact extends beyond the design phase. It has proven to be a valuable tool for public engagement and community involvement in architectural projects. By creating virtual walkthroughs of proposed structures, architects can offer the public an opportunity to experience the design before construction begins. This transparency fosters a sense of ownership and allows for constructive feedback, contributing to the development of designs that resonate with the community's needs and aspirations.
The environmental implications of real-time rendering are also noteworthy. The ability to visualize designs in various environmental contexts contributes to more sustainable architecture. Architects can assess how natural light interacts with interior spaces, optimizing energy efficiency and reducing the need for artificial lighting during the day.
In conclusion, real-time rendering has ushered in a new era of architectural design, propelling the industry into a realm of dynamic visualization, immersive experiences, and enhanced collaboration. The ability to witness designs in motion, explore different lighting conditions, and interact with virtual environments has redefined how architects approach their craft. From facilitating client presentations to fostering sustainable design solutions, real-time rendering's impact on architecture is profound and multifaceted. As the technology continues to evolve, architects have an unprecedented opportunity to push the boundaries of creativity, efficiency, and sustainability in the built environment. -
What if, the newly added JSON datatype in mysql is a way to provide mysql with no-sql-like capabilities.
I mean, some would prefer no-sql cuz they beleive that the tables schema will evolve a lot.
An extra column in mysql table with json datatype called "custom_fields" would do the trick.
What do u think ?8 -
I am a web dev. I got a job as a tech lead 6 months ago and I was very happy about it... But now I don't think I made the right decision. What should a dev evolve into? Any tech leads here that started as devs ( I mention I have 12 yrs+ of experience as a dev ).4