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 - "laymen"
-
Got a job at a great company but I have to move out (I am Canadian and I got a job at Seattle)
How do I say that to my very... "possessive" boss?
Last time someone tries to quit, he threatened to sue them....
(something to do with the NDA contract saying you can't work in a similar job for the next year)8 -
Two types of people in this world.
Those who read "ping" as a command.
And those who read it as a sound. 😂3 -
Some time ago I posted rant "I love go".
After 3 months of being interested in go community, read couple of books and a lot of articles, I got my first job in Go.
#FromJavaToGo8 -
Been trying #rust for 3 weeks now and I really like it. No hopes for a job, but it's nice to have different point of view when coding in Go.3
-
Convo b/w me & lecturer.
Me: Is one line that explains exactly what it does okay?
Him: No.
Me: Okay I'll make it a paragraph explaining it a lot more in detail...Is that okay?
Him: Nope, you need to elaborate for laymen.
I don't know what more I can add. Sick of useless documentation. Any one else have this problem?1 -
To be a Java (or other business popular language) developer
* Java 6, 8 and features up to 14
* SQL + nosql
* Caching
* Logging eg log4j2,
* Searching eg elastic stack
* Reactive
* Framework (at least 1, but hey, knowing 1 is lame..)
* Networking or at least base http knowledge
* Tomcat, jboss or other shit
* Aws, heroku, GCE or other SAAS/paas
* Rest, RPC, soap
* Business Hello World example
* Hexagonal Architecture
* TDD
* Ddd
* Cqrs
* 12 app factor
* Solid
* Patterns
* docket
* Kubernetes
* Microservices
* Security, oauth2
* concurrency
* AMPQ
* Cloud
* Eureka or consul as service Discovery
* Config server
* Hazel cast
*
*
* Endless story ...
Then we can start hello word app2 -
I wrote a whole article about it, and oh wow, it still exists. It was probably the first optimization I ever did in my life, and it was while I was learning SQL.
And writing an edu-tainment article aimed at total laymen as well as beginners was also fun.
http://swczdev.blogspot.com/2010/...
Sadly, czech language only. But... the english autotranslation actually looks readable:
https://translate.google.com/transl...
Long story short, though: 4 or 5-table join going from 7 seconds before optimization, to 0.08 seconds after optimization. Both were written by me, the optimized one was written without any reading on how to optimize SQL, based purely on me actually stopping to think about how I can reduce the DB load based on the little that I knew about how SQL servers work.
Optimization made it about 99,9999422% more efficient, based on my improvised efficiency metric of how many rows the query retrieves and produces versus how many are thrown away on the end due to the WHERE part of the query.
And that was also the day when my question of "what is there even to optimize in SQL?) was answered... by myself.3