Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "terminology"
After months of tedious research, I finally feel like I understand machine learning.
All of my programmer buddies are in envy, but I keep trying to explain that what I finally get is that it's not as hard as it's presented to be.
I feel like a lot of the terminology in machine learning is really pretentious and unnecessary, and just keeps new people from the field.
For example: I could say: "Yeah, I'm training a classification model with two input neurons, a hidden activation layer, and an output neuron", and you might think I was hot shit. But that just gets translated into "I'm putting in two inputs, sorting them, and outputting one thing".
I feel like if there was a plain language guide to machine learning, the field would be a lot more attractive to a lot more people. I know that's why it was hard for me to get in. Maybe I'll write one.28
most pissed off? Old team I was on ported 40000 lines of my beautiful c++ code to java. First of all they ported it from a good language to a bad language, and did an awful job of it. and then when I rejoined them I fought them for months to port it back, they wanted a good reason to port it back. Weren’t convinced there was any gain from it. Oh... but apparently it was okay to waste their time porting my beautiful code into shitty java code, a language that narrowly avoided extinction because google saved it from the jaws of death and even they regret it. And they used reflection!!! My eyes were twitching again at this point. I was like DHDHRIFNFBRISKSKFHDI There was no good reason for you to change it in the first place and now the burden of proof is on me? Closest I ever came to actually flipping a desk. I was on my feet and everything. Nearly exploded. My blood pressure must have been 200/150 I wanted to fucking slit their throats but I suppressed my rage using the Vulcan practice of kolinahr (it would be sad if I had to explain that this is a joke) I rewrote it in c++ anyway and wiped any trace of the java code from the company servers. Want me back? We’re doing it my way asswipes, not the fucking stupid shit way. Shut the fuck up and leave.
Second Most pissed off ive been? Forced to code in c# in visual studio for two weeks. Literally almost quit my job over that. They got the message haven’t asked me to touch windows since.
congratulations on using the terminology ‘pissed off’ instead of angry. Sure to be a good week18
When there are no widely approved Swedish translations of big data terminology, such as "big data" itself. When discussing this kind of terms you have to resort to using the English words for them, which results in a horrible language mix, Swenglish.42
Anyone else's blood boil when TV shows abuse tech terminology? Like the 'hacker' saying "connecting the virtual TCP to the neural net."14
I've been hunting for a new job for several months because my current company isn't growing my skills any further. There have been many setbacks, a few rejections, and that awful lingering imposter syndrome. So I finally dug myself out of my self pity and began learning things that my current company doesn't implement – JS frameworks, UX practices, etc. Today I had an interview that felt more like a conversation and collaboration than getting grilled about terminology and bug fixes. No matter what the result, I've been inspired to learn again 😌13
"You know what really grinds my gears?":
Please stop saying your a coder!!!
Also don't say others are 'coders'…
This irritates me so much...
Sure you write code... Your a programmer not a coder...
Damn horrid term coder! The correct terminology is programmer!22
Spent the last days trying to reach paypal tech support, hung on the phone across the globe, with people at paypal CS, who weren't even familiar with their own terminology, read tons of VERY 'straightforward' documentation and it kept me up two nights straight.
ALL because I REFUSED to believe that it is like I understood it between the lines that I read.
Today I got my answer. You can create Billing Plans (rules on which you'll base your subscriptions, i.e. amount, intervals, duration..) ONLY over the rest api, and only when a customer purchases a first subscription, you're able to EDIT the plan on Paypal dashboard!
What fuckery is that!? You have a edit form, but you can not provide a create form?! TY paypal for making me build a whole billing plan manager for usually a one time transaction per website.
I AM SENDING YOU MY PHONE BILL.2
Once upon a time, received a call whose intro was "I have a new production machine and I want to set up the Exchange server."
Person wanted to set up Outlook on a new personal computer.
Terminology can be dangerous.2
When your co-worker uses needless terminology. It’s your day off and you’re texting from bed.
cw: Do you have access to the email client?
me: You mean the work email? Yes.
cw: Did you set up access to the database or an FTP protocol for userX?
me: You mean an admin account? Yes.
cw: Were we planning on adding more calls to action on projectX?
me: You mean site links? Yes.2
Got my first Linux magazine with real worth tips for noobs with advanced stuff (like mounting a web mail server using Nmap, create personalized distros ssh, terminology and stuff , you don't see that in most noob magazines).
First point... Comes with a CD with 4 distros (OK... I perfer to download the latest for my VMs) and 200 euros worth of.. Linux software?
And I ripped this beautiful cover before even reading it... Killing a wasp. So, worth the 10 euros even before opening it6
4 years ago I made a personal goal/plan to be a full stack developer. Meaning a good understanding of any development between os level code and web/front end user experience.
So now, devRant collective I ask you. What do you call a developer with good skills in:
- os level code (c, c++ and os apis)
- database level tech (advanced querying and db aglo/modeling)
- software architecture
- application level (workflow and business logic)
- transport level (protocol design and usage)
- front end tech (graphics programming and event driven paradigm)
- user experience14
I conducted my first "technical" interview today. Let's just say the chap needs to brush up on his terminology...
Q: What's a class and an object? And what's the difference between each?
A: Ummm... Errr... The one holds static information and the other can change its values.
OK, in his defence, he was nervous and English isn't his first language either, but then brush up on your terminology at the very least so that you can speak the lingo when asked questions about programming.1
New question to ask potential employers: What makes this work so difficult? is it innovative or in a challenging domain? Or is it because of a poorly documented, poorly maintained code base between multiple groups that can't agree on terminology?
Though if you ask, you should probably be more polite than I am hearing this in my head.2
Back in the days, i was on my way back home, after visiting my wife who brought our little son to life, it once blew my mind.
The terminology "inherit" is complete bullshit.
Why is that?
Because, a child isn't able to do anything the parents can, immediately.
It has to learn every single ability from it's parents or who knows else.
Maybe a kid won't be able to learn a specific ability from it's parents at all.
Furthermore, a child doesn't have a single parent.
There are always mom and dad.
Ok. Besides that, there is the option of a solo parentship, if a woman decides to breed based on frozen code ;)
Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.
Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).
When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).
FUCK THIS SHIT
*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending
Once upon a time aka last week,
Was trying to fix an industrial automation software coded in Codesys. My company's standard library is riddled with bad documentation with a mix of English and German terminology.
Had to find out why a program kept crashing the program upon start up. Long story short and many stressful hours later, I found two functions in the standard library that caused an endless terminal process loop. Had to wrap the function in an 'if statement' so it would only run once. Function should have done this by default.
If html and css are not really considered as programming languages, then how do we call the job? I've 'coded' the design? I've front-end designed the design? I've 'sliced' the design? (last one is sure old fashioned enough to exist..)
p.s. and while front-end devs nowadays are required to have angular, react, etc as their skillset, I feel like html and css are also shifting to be required for designers..1
My thoughts on how progression goes from top to bottom:
I'm going to use the terms all wrong because I don't know correct terminology but this is just how I make sense of a good workflow in programming.
From top to bottom:
Variablizing (is this a word? I use it to myself)
Abstracting the function
Adding an interface to the abstracted function (another layer of abstraction saves so much effort later)
Testing each step if possible.
Then when I feel a bit of code is good, giving it some more time and more testing then finding bugs I didn't see before and improving things.
If I get tripped up and spend too much time on some issue, I'll just let it sit for a little bit and take a walk or think of something else. The problem is still being worked on subconsciously and when I return after a rest usually is more apparent.
Testing, testing, testing and more testing!1
Im going through my router config yestersay and realize that in the security part an ip address is set to permitted.
Iplocation its a company that owns this other company which is my ISP.
Is it normal for an ISP to provide a router with a permitted ip address set by default?
Is this not calles a “porte derobee” (sorry i just know the french terminology，“sneaky doorway”)???4
Lecturer : Today you can save data into the internet.
The internet is not a storage device 🤦♂️
Correct terminology when talking to computer science finalists too much to ask?
And we complain about the government.