Haha, most people here do tech it seems. Well, me too.
People seem to think I’d be good at maths and my entire job is like maths. I’m not and I don’t view it that way. There’s a lot of problem solving and engineering, but I find it very creative and expressive
I know, the proportion of professional tech people here shocked me. I know there’s a lot of like open source nerds and whatnot here but I only do that stuff as a hobby lol
no one QA’d this AAA game
Actually, that game breaking bug was caught weeks ago by QA. Unmoving deadlines set by upper management meant that a fix couldn’t be made in time for the content schedule.
That’s why bugs can be labeled “in shipped version.”
They know. It’s just they balanced it against everything else and it wasn’t worth spending time on or delaying the game for.
I won’t say that it’s purely a AAA problem, but it’s harder to excuse there.
Also, by the time the game has been released for 1 hour, the players have already racked up more playtime than the full QA team could reasonably achieve throughout several years of development (and for most of that time QA were playing an older version…). So, if your game has a lot of player choice, randomization, simulation, complex systems, chances are the players are seeing things that QA never did. And then the players wonder how QA could miss such an obvious bug.
I’ve mothballed multiple RCs from finding P0 issues by pure chance. In my experience, 90% of bugs are already caught by QA, 8% were isolated bugs that would realistically never get caught in QA, and 2% just slip through.
“IT is mainly introverts doing mysterious stuff no one understands”
It is a very cooperative field where everyone has different roles with different responsibilities, but everyone has a vague idea what everyone else is doing. Most of the time is spent making sure everyone else can also use the systems you build, not just yourself.
That grass is better than wild growth. Wait…
(IT support) I actually don’t know where that random setting in your application is, I’m just really fast and good at guessing from doing it a million times in applications I’ve never heard of before.
Similar to that, just because someone works in IT, doesn’t mean they can fix your computer problem. I’ve worked with a lot of developers who were great coders but couldn’t resolve networking or random OS issues.
Oh yes. I support a lot of developers, and being a good programmer is not the same as understanding networking in a corporate environment or even knowing anything about printers. That’s why I’m needed 😃
I’m a developer. Most of the time when I contact IT it’s because they broke something I rely on, like our vCenter appliance or network communications between some Linux appliances with static IPs.
That the folks in IT have any sway over microsoft or facebook’s ui plans.
NO Karen, I can not make Teams go back to the way it used to be. No matter how many times you ask.
I work with radio camera links. The number of people who get upset over the receivers is depressing. They can make the 5G conspiracy theorists look educated.
Receive equipment is incapable of radiating at all.
The part that radiates is completely safe!
Seriously, any danger would be at the camera end. I am happy to sit with it fully powered and the antenna between my legs. (It stops the camera getting knocked over). It can’t put out enough power to do any harm. It’s comparable to home WiFi and weak compared to the mobile phone you are happy to put to your head!
In any software development timeline given, triple it to be safe!
Programmers don’t just pull perfect codes from their butts.
Programming languages (yes, in some scenarios, even python) are hell to work with. And yes, I know developer experience has gotten so much better compared to 5 years ago. Still, there are too many unknowns.
It’s like trying to shush a crying baby. Trying every trick on the book to put her back to sleep. But naaah, all she does is cry (no reasons, no hints)
This makes a half-an-hour job take 2 days (hence the unknown delays and setbacks)
If you meet a programmer that pulls a rough prototype of a single module inside a program in a few seconds and works immediately. Know that he/she has 10+ years of experience in that language domain.
Like a granny that “feels the baby” and knows what it wants, making the baby calm immediately.
And even then, it just meant that whatever solution they thought up worked first try.
With experience you get better at finding good, working solutions quicker, but there will always be times when things take a bit of iteration.
Everyday I’m thankful I don’t develop software. Yall are a different breed. Thank you
LoL Buddy, I’m not.
One word: “patience”
Patience in trying and trying until a solution sticks :)
Credit card companies don’t issue credit cards, they’re middlemen for the banks and take a cut from every transaction processed.
When I lost my credit card overseas I was issued an emergency replacement by MasterCard and it only had MasterCard branding. I guess sometimes they issue cards (unless they got a bank to print it without their branding).
That’s technically not a card issuance, which in CC terms only happens when the bank associates an account on their end with a new card profile from the CC company. No actual card needs to be issued either, a token in a digital wallet works the same way.
Deactivating a lost card and activating a replacement (temporary or otherwise) are just maintenance activities on an existing card profile. They get recorded to the original profile both for record-keeping and so that the bank doesn’t get billed extra for issuing a new one.
There you go, proving exactly what the OP was asking about! I just assumed issuing and printing were the same.
I did too! Turns out there’s a lot of weirdness and jargon that gets built into the system after 44 years of continuous operation, and of course the CC companies wanted to be able to bill separately for issuing new cards and printing replacements. XD
Visa and Mastercard, yes. Amex and Discover are both network and bank.
That it all used to be like this.
What field is that?
Green.
A comedian huh?
That I could fix Windows PCs. Nope. When my work PC has issues, I call IT. I design computer chips.
Hey! Can I ask you about that? What type of chips? What are your most used skills/technologies and what helped get started when you were new? I want to work with fpgas, and I’d love to know what your experience with that has been like
I started with programming about anything that is programmable and not up on a tree at the count of three. I did industrial control units, and I worked on a Cray X-MP, and about anything between. I wrote computer games, compilers, an OS, database engines, and loads of applications. I’ve probably forgotten more programming languages than todays students have heard of. One day I ended up in embedded systems.
As our company had only one FPGA developer, I got sent on a three day course to learn VHDL from the source (Eugen Krassin, one of the original key developers of ISE). Right after that, I started developing FPGA firmware for our company. Luckily, I had some hardware experience from my work on the C64 and earlier, so I had a good understanding of clocks and signals. I know that even seasoned programmers really hit a wall when entering the world of HDLs.
I started with ISE back then on Spartan S3 and S6, then Xilinx f-ed us up so hard that the boss slammed the phone down after the last call with those guys and told me to find a more reliable company STAT. We now use Efinix FPGAs which has the big advantage that people there actually listen and help when I ask a question.
My field is isosynchronous low-latency networks for audio applications.
Woah, you’re on OG! I’m unfamiliar with a lot of those things and had to look them up. Crazy!
Hah! ISE - I used that for a hot second, and you still see tutorials using it as well.
My goodness, tell me about it, I’m new and I already find myself frustrated with Xilinx sometimes. It feels like there are very few resources from them for learning, but I thought that was just because it’s a niche subject. I’ll have to take a look at Efinix. I guess I thought it was safer to stick to the biggest name while I’m trying to get established. At the moment I’m trying to get some example projects working on a Zybo Z7. I’m finding out that it’s a lot to take in
Thanks for taking the time to reply! I feel strangely honored to hear from such an OG :) Cheers!
Whenever you are looking for a supplier for something, keep in mind that there are advantages and disadvantages when choosing one.
If you are in a small niece company, and your supplier is THE BIG OLD COMPANY, you are completely at their mercy. On the other hand, they usually have vast resources you can tap, like training capabilities and software you won’t get elsewhere, or at least nor for the price.
That was our relationship with Xilinx. Yes, you get trainings and tutorials for everything, and they have a “light” version of ModelSim thrown in for free in their IDE, but on the other hand, they basically cut us off from one day to the next. And that was not even our fault.
So we went looking and found Efinix. Small, but growing, their IDE has a few edges that need to be rounded off, and they can’t afford to throw in a free simulator, so we had to spend quite a few bucks to buy that (and it was not even ModelSim we bought, so I had to re-train). But at least they are open and helpful. You ask a question in their forum, and they come back to you to help. I’ve been talking to real people who are directly in contact with the dev team. When I had a strange compiler problem, I had a fix within 48 hours. THAT is gold in a supplier.
I’m finding out that it’s a lot to take in
Yes, indeed. The step from CPU-based programming languages to Hardware definition languages is hard for most programmers, and for some, it is even insurmountable. Once you get the hang of it, it gets way easier.
I met a student once in a Reddit sub once who had issues with her code. I helped her and gave her a few tips how to improve it, and at the end, she asked me of my opinion of the project. I told her that it was a nice little beginner project, something to pass a boring Friday afternoon. Her reply: “Thats my Bachelor Thesis!*”. What looks big and difficult to master will one day look simple and meek when you look back, so don’t let it drag you down if things don’t work on the first try.
Not so much a professional field as a field of human experience, but being homeless.
People think the main things homeless people lack are:
- food and drink
- shelter
- money
In actuality, most homeless people have at least some of that stuff. What they tend to totally lack, creating the difficulty in living a civilized life of dignity, are:
- bathrooms/hygiene facilities
- security
- storage space
We aren’t trying to screw you, the actual solutions (not bandaids) are just expensive (paying for knowledge, skill, equipment, and parts). That 5 min fix took years to know to look for and how to fix quickly, plus have the part on the truck for immediate installation. Typically a quick tech is a good tech if the problem is solved.
That you can quickly pick up coding with a few courses.
Can you learn it? Sure why not. Just keep in mind that you’ll never stop learning, so it has to fit into your lifestyle.
Further, you’ll have to be patient and be able to deal with stress well. If you can’t adjust yourself to work in a team, you’ll have difficulty finding work.
Another misconception is that coders stay alone at home in a dark room all the time. Coding is just one part of your life and people do all sorts of stuff.
Yeah lots of people who aren’t in tech think of coding as a solitary job, but it’s a very social-skills-dependent job.
Social skills required to be a coder (at least; probably forgetting many):
- Communicate complex concepts which have never been discussed before
- Deliver things on time
- Understand the tradeoffs of others’ jobs well enough to make good decisions about when it’s worth it NOT to deliver something on time (or be able to figure it out by communicating with whom you’re delivering to)
- Know the balance between asking for help and trying to figure it out yourself, including the short- and long-term tradeoffs of the two approaches
- Know whether a problem you’re encountering is your own lack of skill, your own lack of knowledge, your own lack of care, or someone else’s any of those, and then communicate with others on the basis of being unsure of this
- Deal with antisocial coworkers who can hide their shenanigans in the complexity of the code. I.e. if they’re smart enough they can screw with your work, making you look bad, in a way that is extremely difficult to explain to non-technical management (and hence get support for)
- Have the emotional stability and the hutzpah and the finesse to call things like this out when they do happen, and make those complicated explanations or deliver their abstract form
- Understand and feel the pain of users when their systems break
As an autistic person, I struggled mightily with the social skill requirements of being a coder on a team. I ultimately failed. I’d like to go back and try again, after doing some really basic shit to improve my own character.
People who think the earth is flat. I work in geographic information systems.
