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
-
*builds a DIY 3.5mm audio wire out of metal jacks, 28 AWG electrical wire, and Ethernet wire coat as a sleeve*
*measures its resistance by doing 4 wire measurement*
(4 wire measurement explanation => https://youtu.be/L9q5vwCESEQ?t=260)
Turns out to be 800 milliohms for this wire.. well that's crappy. At such a low voltage like what the sound card puts out (30mV peak-to-peak at best) that's gonna heavily attenuate the sound, no?
*measures another audio wire that I bought a while ago with the same method*
3.2 fucking ohms, and my test at 1A significantly heated up the wire too. Turns out that this DIY contraption is 4 times better than the commercial ones out there... Sometimes you really have to dial down to what common standards you're building your own stuff against. And it's relatively easy to build too.. awesome! :)
Well, all I can say is that I'm satisfied ^^
11 -
I can't help but be disappointed in the direction that technology has directed us into, especially social media.
While I love my girlfriend, she more often than not spends her time scrolling away at the dumbest shit on Instagram, Facebook, .. reels. Reels everywhere. And she's not dumb, mind you. She's an engineer just as much as you (presumably) and I are. Just in a different field.
When looking into it online and stumbling upon more than one study, I learned about the term it had been coined.. technoference. That's the constant interruption of social media into our day-to-day lives, and the dopamine kick it gives -- more so than IRL peers do. Why that is, being the digital equivalent to McDonald's, that's beyond me. But somehow it seems to be better, all while the content isn't even useful. It doesn't allow you to learn anything, to gain insights, or to explore things that could serve you in the real world. Cat videos and random shit that's somehow.. funny? Having pretty much completely disconnected from social media years ago, I seriously fail to see how.
Maybe us nerds in the 90's and early 2000's telling everyone else how we'd change the world and prove everyone who called us freaks wrong, disenchanted as we were (and probably still are), were the catalyst for this social disaster. We had the cognitive skills to do it, but not the social equivalent. I feel guilty... Even though I've always been part of a big tech resistance in some capacity, I still feel guilty. Because I'm one of those people with the skills of those who created this trash fire of a societal status quo. Everyone glued to their screens, 95% of the time not for work. Not even to aid one's ability to function in the real world. Just to combat boredom. All day, for many hours on end.
Where is it going to end? When will people realize the dystopia we got ourselves into? Will anyone but a few fight it? Would those who don't fight it even care?12 -
The year is 2218. Machines have taken over the world. A small pocket of resistance fights back against them. And in their darkest hour, Windows, which hasn’t been updated in over a century, still won’t tell their strategists what program is keeping the USB drive with their plans open. They don’t want to unplug the drive as that could damage the files.
While they’re trying to figure it out, the attack comes and catches them all unaware.
As a result, humanity is extinguished.
Don’t let this happen to you.5 -
@dfox and @trogus
I’m quite into lean development, sorry... “Lean Development” and I can’t help but notice your users are trying to tell you something by their actions.
I keep skimming past posts where a user is @‘ed in the main rant.
Then either themselves or someone else will @ those people in the first or second comment as @ing doesn’t work on the main body.
I understand you have your reasons but in the spirit of lean, MVP, build measure learn etc etc
Shouldn’t you accept the behaviour of least resistance and implement the functionality in the main rant body?
Because you’re not stopping anyone from @ing folk, you’re just making it more annoying to do so.
This meme says it all
23 -
I started drinking coffee when I started as a junior dev.
I loved its boost, but after a while being on coffee was exactly how I felt before as normal. I incrementally upped the dosage, while my resistance creeped up too. I reached a moment when I drank a liter daily, so I witched to yerba maté instead, which resulted in more potent brews. Then I got used to its strength too plus it tasted like horseshit. I switched to caffeine tablets, takingg more and more. Soon after I reached a level which was described medically as the top one should be allowed to take.
I no longer felt any boost. In between caffeinated moments of normalty, I felt like a brain-dead zombie. When I was caffeinated, I was jittery, my shoulder and eyebrow was glitching, my stomach was flexing like before taking a huge exam.
After some miserable time like that, I quit caffeine entirely. I was fatigued, dull and my mind was hazy for te next 1-2 weeks.
I then finally, became gradually normal again.
I drink tea and coffee only socially, perhaps a few times in a month, and never after too much later than noon.
Now I can't wear my "Programmer. Converts coffee into code" shirt anymore. Apart from that, I'm much better off :)
What's your coffee story?14 -
I haven't ranted for today, but I figured that I'd post a summary.
A public diary of sorts.. devRant is amazing, it even allows me to post the stuff that I'd otherwise put on a piece of paper and probably discard over time. And with keyboard support at that <3
Today has been a productive day for me. Laptop got restored with a "pacman -Syu" over a Bluetooth mobile data tethering from my phone, said phone got upgraded to an unofficial Android 9 (Pie) thanks to a comment from @undef, etc.
I've also made myself a reliable USB extension cord to be able to extend the 20-30cm USB-A male to USB-C male cord that Huawei delivered with my Nexus 6P. The USB-C to USB-C cord that allows for fast charging is unreliable.. ordered some USB-C plugs for that, in order to make some high power wire with that when they arrive.
So that plug I've made.. USB-A male to USB-A female, in which my short USB-C to USB-A wire can plug in. It's a 1M wire, with 18AWG wire for its power lines and 28AWG wires for its data lines. The 18AWG power lines can carry up to 10A of current, while the 28AWG lines can carry up to 1A. All wires were made into 1M pieces. These resulted in a very low impedance path for all of them, my multimeter measured no more than 200 milliohms across them, though I'll have to verify and finetune that on my oscilloscope with 4-wire measurement.
So the wire was good. Easy too, I just had to look up the pinout and replicate that on the male part.
That's where the rant part comes in.. in fact I've got quite uncomfortable with sentences that don't include at least one swear word at this point. All hail to devRant for allowing me to put them out there without guilt.. it changed my very mind <3
Microshaft WanBLowS.
I've tried to plug my DIY extension cord into it, and plugged my phone and some USB stick into it of which I've completely forgot the filesystem. Windows certainly doesn't support it.. turns out that it was LUKS. More about that later.
Windows returned that it didn't support either of them, due to "malfunctioning at the USB device". So I went ahead and plugged in my phone directly.. works without a problem. Then I went ahead and troubleshooted the wire I've just made with a multimeter, to check for shorts.. none at all.
At that point I suspected that WanBLowS was the issue, so I booted up my (at the time) problematic Arch laptop and did the exact same thing there, testing that USB stick and my phone there by plugging it through the extension wire. Shit just worked like that. The USB stick was a LUKS medium and apparently a clone of my SanDisk rootfs that I'm storing my Arch Linux on my laptop at at the time.. an unfinished migration project (SanDisk is unstable, my other DM sticks are quite stable). The USB stick consumed about 20mA so no big deal for any USB controller. The phone consumed about 500mA (which is standard USB 2.0 so no surprise) and worked fine as well.. although the HP laptop dropped the voltage to ~4.8V like that, unlike 5.1V which is nominal for USB. Still worked without a problem.
So clearly Windows is the problem here, and this provides me one more reason to hate that piece of shit OS. Windows lovers may say that it's an issue with my particular hardware, which maybe it is. I've done the Windows plugging solely through a USB 3.0 hub, which was plugged into a USB 3.0 port on the host. Now USB 3.0 is supposed to be able to carry up to 1A rather than 500mA, so I expect all the components in there to be beefier. I've also tested the hub as part of a review, and it can carry about 1A no problem, although it seems like its supply lines aren't shorted to VCC on the host, like a sensible hub would. Instead I suspect that it's going through the hub's controller.
Regardless, this is clearly a bad design. One of the USB data lines is biased to ~3.3V if memory serves me right, while the other is biased to 300mV. The latter could impose a problem.. but again, the current path was of a very low impedance of 200milliohms at most. Meanwhile the direct connection that omits the ~200ohm extension wire worked just fine. Even 300mV wouldn't degrade significantly over such a resistance. So this is most likely a Windows problem.
That aside, the extension cord works fine in Linux. So I've used that as a charging connection while upgrading my Arch laptop (which as you may know has internet issues at the time) over Bluetooth, through a shared BNEP connection (Bluetooth tethering) from my phone. Mobile data since I didn't set up my WiFi in this new Pie ROM yet. Worked fine, fixed my WiFi. Currently it's back in my network as my fully-fledged development host. So that way I'll be able to work again on @Floydian's LinkHub repository. My laptop's the only one who currently holds the private key for signing commits for git$(rm -rf ~/*)@nixmagic.com, hence why my development has been impeded. My tablet doesn't have them. Guess I'll commit somewhere tomorrow.
(looks like my rant is too long, continue in comments)3 -
Spent a lot of time designing a proper HTTP (dare I even say RESTful) API for our - what is until now a closed system, using a little-known/badly-supported message-over-websocket protocol to do RPC-style communications - supposedly enterprise-grade product.
I make the API spec go through several rounds of review with the rest of the dev team and customers/partners alike. After a few iterations, everybody agrees that the spec will meet the necessary requirements.
I start implementing according to spec. Because this is the first time we're actually building proper HTTP handling into the product, but we of course have to make it work at least somewhat with the RPC-style codebase, it's mostly foundational work. But still, I manage to get some initial endpoints fully implemented and working as per the spec we agreed. The first PR is created, reviews are positive, the direction is clear and what's there already works.
At this point in time, I leave on my honeymoon for two weeks. Naturally, I assume that the remaining endpoints will be completed following the outlines/example of the endpoints which I built. When I come back, the team mentions that the implementation is completed and I believe all is well.
The feature is deployed selectively to some alpha customers to start validation testing before the big rollout. It's been like that for a good month, until a few days ago when I get a question related to a PoC integration which they can't seem to get to work.
I start investigating and notice that the API hasn't been implemented according to the previously agreed upon spec at all. Not only did the team manage to implement the missing functionality in strange and some even broken ways, they also managed to refactor my previously working endpoints into being non-compliant.
Now, I'm a flexible guy. It's not because something isn't done exactly as I've imagined it that it's automatically bad. However, I know from experience that designing a good/clear/future-proof API is a tricky exercise. I've put a lot of time and effort into deliberate design decisions that made up the spec that we all reviewed repeatedly and agreed upon. The current implementation might also be fine, but I now have to go over each endpoint again and reason about whether the implementation still fulfills the requirements (both soft and hard) that we set out to meet.
I'm met with resistance, pushback and disbelief from product management and dev co-workers alike when I raise the concern that the API might actually not be production-ready (while I'm frantically rewriting my integration tests and figuring out how the actual implementation works in comparison to what was spec'ed).
Oh, and did I mention that product management wants to release this by end-of-week?!7 -
TL;DR don't fiddle around with batteries if you aren't ABSOLUTELY sure what you are doing
For my arduino project I need to use 18650 Li-Ion batteries. They are pretty awesome but at the same time pretty dangerous if you don't use them the right way. You need protection boards etc. or they can/will go BOOM.
So I am looking around Amazon to find some good quality ones and reading some reviews made me wanna cry.
People were REMOVING protection circuits from the batteries and even removing the foil around the batteries. NEVER EVER FUCKING DO THAT!
I also found out that these are the batteries used in E-Cigarettes and now I really don't wonder anymore why they explode so often. People fuck around with the batteries just so they fit into their vapes, or reduce the resistance of the coil (the thing to heat up the liquid) to an absolute minimum so they can get more watts. A side effect of this is that a lot of current gets drawn from the batteries (>20A or something) which makes them go BOOM if no protection/fuses are used in the circuit.2 -
Ah fucking hell.
I hate it when my boss goes the path of least resistance to implement something.
Of course declaring a class property with the "any" type (TypeScript) is a fucking lot easier than to properly write an interface for it and declare the property with that type.
Thank god I have holidays, otherwise I would hatepunch his fucking monitor. Twice.2 -
KISS, DRY, Path of Least Resistance, Three Strikes and You Refactor, early returns, no array.map when nothing is returned, only use switch when # cases >= 3.
And using var in javascript instead of let/const to piss off my colleagues (and because I understand function scope well)6 -
My friend has a saying that helps me keep focused and reality checked:
"Move Forward, Stay Flexible, Expect Resistance."
Say it to yourself often.
To all the devs out there fighting the fight, keep this in mind and push forward. One of the things I love about our industry is the wealth of information we share and the support we get from our mentors and each other.
Some of the jokes aren’t bad either.1 -
1. It's gonna be more and more specialized - to the point where we'll equal or even outdo the medical profession. Even today, you can put 100 techs/devs into a room and not find two doing the same job - that number will rise with the advent of even more new fields, languages and frameworks.
2. As most end users enjoy ignoring all security instructions, software and hardware will be locked down. This will be the disadvantage of developers, makers and hackers equally. The importance of social engineering means the platform development will focus on protecting the users from themselves, locking out legitimate tinkerers in the process.
3. With the EU getting into the backdoor game with eTLS (only 20 years after everyone else realized it's shit), informational security will reach an all-time low as criminals exploit the vulnerabilities that the standard will certainly have.
4. While good old-fashioned police work still applies to the internet, people will accept more and more mass surveillance as the voices of reason will be silenced. Devs will probably hear more and more about implementing these or joining the resistance.
5. We'll see major leaks, both as a consequence of mass-surveillance (done incompetently and thus, insecurely) and as activist retaliation.
6. As the political correctness morons continue invading our communities and projects, productivity will drop. A small group of more assertive devs will form - not pretty or presentable, but they - we - get shit done for the rest.
7. With IT becoming more and more public, pseudo-knowledge, FUD and sales bullshit will take over and, much like we're already seeing it in the financial sector, drown out any attempt of useful education. There will be a new silver-bullet, it will be useless. Like the rest. Stick to brass (as in IDS/IPS, Firewall, AV, Education), less expensive and more effective.
8. With the internet becoming a part of the real life without most people realizing it and/or acting accordingly, security issues will have more financial damages and potentially lethal consequences. We've already seen insulin pumps being hacked remotely and pacemakers' firmware being replaced without proper authentication. This will reach other areas.
9. After marijuana is legalized, dev productivity will either plummet or skyrocket. Or be entirely unaffected. Who cares, I'll roll the next one.
10. There will be new JS frameworks. The world will turn, it will rain.1 -
“Begin your onboarding and assimilation program.” Are new employees joining a company or the Borg? I guess it’s ok so long as the next line doesn’t say “Resistance is futile.”
-
That moment when you sit to code and start learning a new thing, but the installation and prerequisites take up all of your time. *Sighs*1
-
A certain person here on devRant was annoyed about my phone being named “Beyond”, seeing a screenshot of my settings.
What they said: “the name, beyond, reeks pretentiousness and arrogance, you say you’re better than other people”
What really happened: during one of my manic episodes, I discovered the band named Death Grips. Their music resonated with me and helped me to cope with my derealization. In one of their songs, I misheard lyrics, and heard the word “Veyon” that was never there in the first place. Upon my inner voice pronouncing it, as it usually happens to me, a brand-new universe appeared before me, where Veyon was a name of a megacorporation that exists in a shaky spacetime plane somewhere in India. If you want to go there, three outcomes are possible: you can actually come to their building that appears to be normal, with people working inside you can talk to, and no signs of trouble in sight. Or, you can try to walk to their building, but you will never reach it. GPS will show you slowing down gradually as you get closer, but to you, it would look like you’re just walking with your regular speed, as if nothing happened. Like a function trying to reach its asymptote, you’ll never come to your destination. The third outcome is by far the most interesting one. You will reach the building, but it will be abandoned, with doors scattered on the floors randomly, some of them will disappear after you walk in, rendering you missing in this universe. Oh, and floors are guarded by robots and turrets, and they are made by Grumman, the military aviation manufacturer. Yes, Grumman, not Northrop Grumman. This building in the third outcome originates from the spacetime plane where Northrop and Grumman never merged.
The whole thing raced through my mind in a millisecond. I liked it and decided to squat the name, but it was already taken by Veyon open source software (Virtual Eye On Networks).
In some time, I bought a new phone second-hand, and named it Veyon. The next day, I took it to shower with me. It turned out that the seller lied to me about it never being fixed. It was, and in the process its water resistance was compromised. So, this phone was damaged beyond repair the next day I bought it.
The same day, I went and bought the same phone model, but brand new, and in black, as I originally wanted. I was grateful for this opportunity that helped me escape the situation where I would've been using the phone of the colour I disliked just because I cheapen out. I know myself, and I would’ve been feeling uneasy every day, hesitant to sell it and get a new one because “nothing is wrong with it, quit being this picky, it’s just a colour”, but wait, don’t I deserve to make the colour a significant enough reason to switch the phone because I care about colour, especially if it’s me who’s paying the money? Did I make this money rightfully, or am I an impostor who gets paid because of intricate lies I tell? Do I actually tell them, or do I make that up to somehow convince "them" I'm innocent? Or do I try to get attention?
I’m terrible at dealing with that kind of mess, So, I was grateful.
The only thing left to do was to name my new phone. I decided not to name it “Veyon” again, just in case. So, I named it “Beyond”, as this word is probably what the actual song said.
The monstrosity of a story above is the usual thing for me to feel. I was really hurt by you telling me the name I chose was a display of pretentiousness. Do I deserve to be pretentious? I say yes, but my voice is shaking, as flashbacks of my awful mother abusing me come in the way.
You hurt me with that comment. Let’s meet? :)2 -
My project manager decided to go full micromanager today. So members of the team have been emailing our manager and the PMs manager to explain why what he's doing is bad both for our deliverables and our moral1
-
A friend of mine is youtuber and he does a lot tests on phone ( call him X)
Another friend of mine hates Apple product. Partly because he can’t afford it (call him Y)
whenever X wants to do a WATER RESISTANCE TEST, Y would go: “Lets fuck Iphone”
whenever X wants to do a HEAT RESISTANCE TEST, Y would go: “Lets fuck Iphone”
whenever X wants to do a DROP TEST, Y would go: “Lets fuck Iphone”
One fine day, same happened and X got a bit red. X says: Y come here. Closer, a little more ( few centimeters away now). “Are you fucking mad or what?”
2 -
A software had been developed over a decade ago. With critical design problems, it grew slower and buggier over time.
As a simple change in any area could create new bugs in other parts, gradually the developers team decided not to change the software any more, instead for fixing bugs or adding features, every time a new software should be developed which monitors the main software, and tries to change its output from outside! For example, look into the outputs and inputs, and whenever there's this number in the output considering this sequence of inputs, change the output to this instead.
As all the patchwork is done from outside, auxiliary software are very huge. They have to have parts to save and monitor inputs and outputs and algorithms to communicate with the main software and its clients.
As this architecture becomes more and more complex, company negotiates with users to convince them to change their habits a bit. Like instead of receiving an email with latest notifications, download a csv every day from a url which gives them their notifications! Because it is then easier for developers to build.
As the project grows, company hires more and more developers to work on this gigantic project. Suddenly, some day, there comes a young talented developer who realizes if the company develops the software from scratch, it could become 100 times smaller as there will be no patchwork, no monitoring of the outputs and inputs and no reverse engineering to figure out why the system behaves like this to change its behavior and finally, no arrangement with users to download weird csv files as there will be a fresh new code base using latest design patterns and a modern UI.
Managers but, are unaware of technical jargon and have no time to listen to a curious kid! They look into the list of payrolls and say, replacing something we spent millions of man hours to build, is IMPOSSIBLE! Get back to your work or find another job!
Most people decide to remain silence and therefore the madness continues with no resistance. That's why when you buy a ticket from a public transport system you see long delays and various unexpected behavior. That's why when you are waiting to receive an SMS from your bank you might end up requesting a letter by post instead!
Yet there are some rebel developers who stand and fight! They finally get expelled from the famous powerful system down to the streets. They are free to open their startups and develop their dream system. They do. But government (as the only client most of the time), would look into the budget spending and says: How can we replace an annually billion dollar project without a toy built by a bunch of kids? And the madness continues.... Boeings crash, space programs stagnate and banks take forever to process risks and react. This is our world.3 -
How to spend more time writing docs then code?
15m = doc
1m = code
<code>
/* Motor DC + Mosfet IRF520 + Servo
Materials:
IRF520 (Mosfet) + Dc motor + Batery (3V min)
diode (1N4007?)
Changed Tip122 for IRF520: Tip122 has less resistance and produces more heat
Hardware:
ARDUINO = A(port , 5V , GND)
MOSFET = M(A[port] , + , GND)
MOTOR = MOTOR(+ , -)
BATERIA = BAT(+ , -)
DIODO = D(sinal_1 , sinal_2)
MOSFET
M(port) = A(port)
M(+) = D(sinal_1) AND MOTOR(+)
M(GND) = A(GND)
D(sinal_2) = B(+) AND MOTOR(-)
ARDUINO
A(port) = M(port)
5V = null
A(GND) = M(GND) AND BAT(-)
*/
#define motorPIN 8 // A(port)
int loopy = 0; // Loop variable to limit de program
void setup()
{
// Initialize the motor pin as an output:
pinMode(motorPIN, OUTPUT);
}
void loop() // 1 loop == 100ms
{
if (loopy < 10) // Turns motor ON for 1 second
{
digitalWrite(motorPIN, HIGH);
}
else // Turns motor OFF
{
digitalWrite(motorPIN, LOW);
}
}
</code>22 -
Those fcking newsletter unregister links which requires you to log in!
Gaaaaaaah! Following the path of least resistance, it’s easier to just keep deleting the emails 😂2 -
for me, the problem with going to school and getting a degree is having seen so many ways you can improve your work and wanting to apply all of it, but then you get to the workplace and you're met with resistance. i understand we can't just change everything all at once, but i wish i could sneak in an idea every once in a while8
-
Question:
Do we have any Ingress players around here? What do you think about the upcoming Ingress Prime? I am somehow excited, but only because I just decided to upgrade my mobile phone some days ago 😉 Now the graphics boost can come. 😁 And I really hope that Niantic does not fuck up everything when they plan to be more entry level friendly in the future.
Resistance FTW!26 -
A dedicated team has built an "infrastructure" for creating UI for c++ developers in the company. What looks like a poor attempt at recreating what Microsoft did with XAML at first glance, it actually is a horrible exercise in force feeding people the stinking pile of shit that their code is.
The idea is to make it easy to create UI for developers who aren't used to front end development. They should just need to declare the layout. Very noble.
But.
If you want to do anything more than show a checkbox or a radio button, if you dare to define relationships between the UI controls or worse, if you get ambitious with creating a simple UI that uses a lot of similar controls and similar relationships with dynamic content... be prepared to eat your own barf from eating too much of their shit.
Not only do you now need to write front end code (including JS among others), you need to do it with limited or poor support and you have to make sure that it sits well with the house of moist, crumbly cards the team proudly created. Or resort to some very stupid and performance costing "bypasses" that further cripple your application code. Usually you have to do both of these things.
To think that scores of other teams have welcomed this amazing enhancement with full support without any resistance. It's sickening.
I waste too much of energy (and good jokes!) with these people.4 -
So i wasted last 24 hours trying to satisfy my ego over a shitty interview and revisiting my old job's codebase and realising that i still don't like that shit. just i am 25 and have no clue where am i heading at. i am just restless, my most of the decisions in 2023 have given very bad outcomes and i am just trying doing things to feel hopeful.
context for the interview story-----
my previous job was at a b2b marketing company whose sdk was used by various startups to send notifications to their users, track analytics etc. i understood most of it and don't find it to be any major engineering marvel, but that interviewer was very interested in asking me to design a system around it.
in my 1.2 years of job there, i found the codebase to be extremely and unnecessarily verbose ( java 7) with questionable fallbacks and resistance towards change from the managers. they were always like "we can't change it otherwise a lot of our client won't use our sdk". i still wrote a lot of testcases and tried to understand the working of major features.
BTW, before you guys go on a declare me an embarrassment of an engineer who doesn't know the product's code base, let me tell you that we are talking SDKs (plural) and a service based company here. their was just one SDK with interesting, heavy lifting stuff and 9 more SDKs which were mostly wrappers and less advanced libraries. i got tasks in all of them, and 70% of my time went into maintaining those and debugging client side bugs instead of exploring the "already-stable-dont-change" code base.
so based on my vague understanding and my even more vague memory from 1 year ago, i tried to explain an overall architecture to that interviewer guy. His face was screaming the word "pathetic" from his expressions, so i thought that today i will try to decode the codebase in 12-15 hours, publish a cool article and be proud of how much i know a so called martech system design. their codebase is open sourced, so it wasn't difficult to check it out once more.
but boy oh boy i got so bored. unnecessary clases , unnecessary callbacks static calls , oof. i tried to refactor a few classes, but even after removing 70% of codebase, i was still left with 100+ classes , most of them being 3000-4000 files long. and this is your plain old java library adding just 800kb to your project.
boring , boring stuff. i would probably need 2-3 more days to get an understanding of complete project, although by then i would be again questioning my life choices , that was this a good use of my 36 hours?
what IS a correct usage of my time? i am currently super dissatisfied with my job, so want to switch. i have been here for 6 months, so probably i wouldn't be going unless i get insane money or an irresistible company offer. For this i had devised a 2 part plan to either become good at modern hot buzz stuff in my domain( the one being currently popularized by dev influenzas) or become good at dsa/leetcode/cp. i suck bad at ds/algo stuff, nor am i much motivated. so went with that hot buzz stuff.
but then this interview expected me to be a mature dev with system design knowledge... agh fuck. its festive season going on and am unable to buy any cool shirts since i am so much limited with my money from my mediocre salary and loans. and mom wants to buy a home too... yeah kill me3 -
so, any EE here?
I'm a self-taught EE (shots fired! I was told to call myself an "inventor" so I don't offend my dear EE friends!)
Anyways... I just made a huge insight that wanted to share!
in the circuit that has been breaking my head for the past couple of days (switching DC-DC [boost, buck] converter the inductor takes care of holding the current stable while the capacitor the voltage. (apart from an low-pass filter...) The higher the frequency the smaller the capacity of the inductor needed, the less amount of wire, less resistance, more watts!!!!!11 -
Any recommendations for introductory books on electrical engineering? I'm looking for something that goes into detail on the basics: tension, current, resistance, inductance, capacitance, etc. I have very little knowledge on the subject (I know what the basic components do and that's it) and I found myself struggling a bit with the most basic concept: voltage.
I grabbed my multimeter, a few resistors and a battery and played around a bit. For some reason it doesn't really "click" why on a 5v circuit with 3 2.2k ohm resistors (I think) the voltage around each resistor was like ~1.3 volts or something, while on a circuit with 2 resistors the voltage accross each one was ~2.3 something volts (I don't remember exact values). Like, I know that voltage is a difference in potential, but I still don't get it and idk what I'm missing. Why is the difference in potential accross a resistor different if the circuit has 2 resistors in series instead of 3. It kinda makes sense in my head but at the same time it doesn't.
In short, I want to know the "why" stuff works the way it does, not just the "how".
Also, if the book covers common practices, components, and circuits that'd be very helpful. I want to learn how to build well-designed, reliable and safe circuits.11 -
advantages of bionic systems:
- energy efficiency
- flexibility
- low friction
- compact size
- water resistance
advantages of mechanical systems:
- precision
- rotation is available
- scalability
- can change parts6 -
I wouldn't want to run a company, but I keep hearing about incompetent bullshit and so I think I want to run a company and not fuck it up.
Thoughts?14 -
Haven't been able to sleep well for a while. Generally I've either had to take some sort of sleeping aid (usually benadryl, cause melatonin doesn't do anything to me), or stay awake for about 20+ hours. It's been like that for about 2 years now. Due to that, I've built up a resistance to benadryl.
Last night I took benadryl around 11, figuring I'd fall asleep around 12:30-1. I managed to fall asleep around midnight, and woke up at 1. I tried going back to sleep for hours, but nothing. Now 6 hours later, I don't know. Might end up just staying awake until tonight and passing the fuck out.
I wish I could fucking sleep.10 -
I recently was given the responsibility of finding interns for our company. In the process of reviewing applications, I Googled one of them. The first search result was her Facebook page so I clicked on it, and saw that many of her posts and pictures were set to “public.” I did not see anything out of the ordinary or really anything that would prevent her from getting a job, but decided to mention it to my boss and coworker anyway, just to see what they thought.
To my surprise, I was met by extreme resistance to what I had done. I was told that it is not okay to look someone up before an interview because what I find might “color my opinion of them” and that my own personal judgments might get in the way. I was under the impression that it is one’s personal responsibility to curate their web presence as they see fit and that whatever is found through a simple search is fair game. I was also under the impression that this is pretty standard these days. Am I wrong? Is looking up a potential intern or employee prior to an interview unethical?4 -
Since it would probably mean the overthrow of human race from our throne, I think that the same scenario like in Matrix would happen. We won't go down without a proper fight, but we will go down. So I would probably apply to be their energy source (Matrix style). Main goal is, while I'm being packed in that weird eggshell, to look at it's 9001 ppi display and say: "Suck me bitch."
Best part? No more waking up early, no more responsibilities and being sucked for the rest of my life.
Fuck your petty resistance. You will never be Neo. Deal with it. -
My least favorite part of the world is the engrained habits within society (for lack of a better word).
These habits can be pretty broad but since they are so widespread, it makes it hard for people who value their privacy to stick to their beliefs and go against them.
Examples of this are like saying no to giving away some information, or asking for someone to delete something like a photo of you. Society is trained the other way. Society is trained not to be privacy aware and therefore reacts in a way that puts massive pressure on those who want to keep themselves more private.
I’m sure a lot of you are familiar with this already. Any tips? -
A lot of us get imposter syndrome in this industry. I still get it on a regular basis.
You can't wait until things are perfect. You have to launch imperfectly, but with confidence that you'll get where you need to be. But then imposter syndrome sets in. Self doubt tells us we don't belong.
I found this quote in my email pile this morning:
"Isn't doing your best all you can do? Dropping the narrative of the impostor isn't arrogant, it's merely a useful way to get your work done without giving into Resistance. Time spent fretting about our status as impostors is time away from dancing with our fear, from leading and from doing work that matters." - Seth Godin -
Anyone else become a dev simply because they followed the path of least resistance?
Like, I do enjoy it but went something like this
>Be me
>Grade 9, picking HS subjects
>"Well I do like computers and air-conditioning" picks IT
>"Oh cool extra IT course at school for free"
>"Wow, ok. Free 6 month course after HS" because I did well in the course at school
>Recruited straight into first job at country's biggest life insurance company2 -
I don't really have a recruiter story but this will have to cut it:
I had a meeting at a web development company for a project they were outsourcing to my company (it wasn't really their area of expertise). As we walked into the building, the person we were meeting with kept saying things like, "O, those guys probably just came back from playing foosball downstairs." or "Would anybody like a cappuccino. We have like 10 machines."
To assert my resistance to this shameless charm, I declined the coffee. First and last time I say no to coffee. -
Monolith oriented micro service.
All the coupling and evolving resistance without the simplicity or consistency...
Top Tags
Weekly Rant
View