Details
-
AboutI'm a beginner in terms of programming, but very curious about learning new things :D
-
LocationGermany
Joined devRant on 11/23/2018
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
-
Yusuke Endoh: This is a Ruby program that generates Rust program that generates Scala program that generates ...(through 128 languages in total)... REXX program that generates the original Ruby code again.
Me: OH MAH GAWWD! WHY!!
https://github.com/mame/quine-relay5 -
Windows containers with Kubernetes on AWS and Azure are thing now.
What does that mean? Is it now possible to containerize system critical windows 3.1 legacy software from the 90ties (like the ticketing software at Airport Paris Orly) and orchestrate it in the cloud?
Do you know any use cases for Microsoft Windows in the cloud?2 -
Anyone who's interested in cyber security, go follow Binni Shah (@binitamshah) on Twitter. The amount of tutorials and guides she retweets is crazy and very informative.
Also if you're not on Twitter you're missing out on a lot of content to learn from ✌️18 -
> Last year wrote a unittest - I was asked to delete it
> no design patterns. Not a single one
> no encapsulation
> fucked up inheritance [I had no idea it was possible at all...]
> generics every-fucking-where
> I could go on...
this month the lead dev was not in and I had to make a new feature. Guess what I did :)
tdd [coverage >90%], a couple of builders, a factory or two, two composites, one decorator, only a few generics - only where really needed. Private fields, not a single @Autowired field [they were fucking my tdd], nicely abstracted integrations, and so on. Everything is writen according to clean code: max 10loc methods, <140col lines, reusable constants and utils, SOLID as a rock, etc.
Due date is next week. Took me 3 weeks to craft it.
Guess who's gonna be piiiiiiiiiiiiisssedd 😁
the best part - I don't even work there, our company was hired for xx hours as helping hands 😁
that's not all. They have like 6 envs and their deployment is all-fucking-manual. Will try to learn how to dockerize that app and deploy it on docker. Gosh I wish I could see his face when he's back 😁
p.S. From ethical point of view, he's the only dev who believes his code is perfect. No other dev in the team agrees. AND he once said: 'it's gonna be my way or no way at all'. So I don't think I did wrong... Did I? :)8 -
When you realize that "O&O ShutUp10" (AntiSpy tool for Windows) creator company is a Gold Microsoft Partner
-
Great background music, pretty much a pinned tab of mine now: https://generative.fm/
"Endlessly unique ambient music"
"The pieces featured on this site are not recordings. The music is generated by a different system created for each piece. These systems have been designed such that each performance is unique and plays continuously without repetition."2 -
Customer support story time: (swearing in Dutch because it sounds more fun but it's general swearing so no translation needed I think (will translate the non obvious parts)
Me: good morning, how can I help you?
Client: hello, I have a question for you.
Me: go ahead!
Client: alright so.... one sec, let me turn off my music.
Client: hey Google
.
.
.
Client: hey Google
.
Client: Heeeey Gooooooogle
.
Client: HEY GOOGLE, GODVERREDOMME
.
Me: 😆
.
Client: REAGEER GODVERDOMME. "HEY GOOOOGLE"
.
.
Client: VIES VUIL TYFUS DING, LUISTEREN. HEEEEEY GOOOOOOGLE
.
.
Client: JA GODVERREROMME, LUISTER GEWOON, FUCKING KUT DING. *SHOUTS WITH ANGRY VOICE* "HEY GOOGLE HALLOOOO LUISTEEEEEREEEEEN" (oh for fucks sake, LISTEN fucking piece of shit)
Me: *desperately trying to keep it together*
Client: IK DOE HET ZELF WEL JEZUS GODDOMME *FOOTSTEPS, MUSIC STOPS* (Translation: I'll do it myself, fucking hell)
.
.
.
Client: finally, sorry for that 😅
Me: *still trying to control myself* no problem!15 -
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23 -
Got this for a friend around 39$ last week, so he called and told me the book is awesome. Recommending this book for any beginner. 😁✌7
-
1. The quality of the coffee and toilet paper you encounter during an interview tells you more than promises about table tennis or fruit baskets.
2. Try to determine who their primary client is: subscribers, app buyers, advertisers, etc. It's a major influence on the company dynamic.
3. Before an interview, you can just say: "I would like to sit down with a PO and run through one backlog feature and one bug, to get a feel for the type of tasks at the company". Such an activity immediately reveals team structure, whether they have product owners & scrum masters, what a sprint looks like, how they prioritize tasks, and how organized/chaotic your work experience will be.16 -
If some of you still have problems understanding Quick sort, I've got you covered. This is masterpiece.
https://youtube.com/watch/...2 -
Created a fast and resource-efficient REST API client built entirely with UWP for Windows 10. Would love to get more feedback: https://jeniusapps.wordpress.com/ni...29
-
I created a script with power shell that notifies me before I leave the office if my train is on time or isn’t. See the comment for another image of when the service isn’t on time!26