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
-
Its that time of the morning again where I get nothing done and moan about the past ... thats right its practiseSafeHex's most incompetent co-worker!!!
Today I'd like to tell you the story of "i". Interesting about "I" is that he was actually a colleague of yesterdays nominee "G" (and was present at the "java interface" video call, and agreed with G!): https://devrant.com/rants/1152317/...
"I" was the spearhead of a project to end all projects in that company. It was suppose to be a cross-platform thing but ended up only working for iOS. It was actually quite similar to this: https://jasonette.com/ (so similar i'm convinced G / I were part of this but I can't find their github ID's in it).
To briefly explain the above + what they built ... this is the worst piece of shit you can imagine ... and thats a pretty strong statement looking back at the rest of this series so far!
"I" thought this would solve all of our problems of having to build similar-ish apps for multiple customers by letting us re-use more code / UI across apps. His main solution, was every developers favourite part of writing code. I mean how often do you sit back and say:
"God damn I wish more of this development revolved around passing strings back and forth. Screw autocomplete, enums and typed classes / variables, I want more code / variables inside strings in this library!"
Yes thats right, the main part of this bullshittery was putting your entire app, into JSON, into a string and downloading it over http ... what could possibly go wrong!
Some of my issues were:
- Everything was a string, meaning we had no autocomplete. Every type and property had to be remembered and spelled perfectly.
- Everything was a string so we had no way to cmd + click / ctrl + click something to see somethings definition.
- Everything was a string so any business logic methods had to be remembered, all possible overloaded versions, no hints at param types no nothing.
- There was no specific tooling for any of this, it was literally open up xcode, create a json file and start writing strings.
- We couldn't use any of the native UI builders ... cause strings!
- We couldn't use any of the native UI layout constructs and we had to use these god awful custom layout managers, with a weird CSS feel to them.
What angered me a lot was their insistence that "You can download a new app over http and it will update instantly" ... except you can't because you can't download new business logic only UI. So its a new app, but must do 100% exactly the same thing as before.
His other achievements include:
- Deciding he didn't like apple's viewController and navigationBar classes and built his own, which was great when iOS 7 was released (changed the UI to allow drawing under the status bar) and we had no access to any of apples new code or methods, meaning everything had to be re-built from scratch.
- On my first week, my manager noticed he fucked up the login error handling on the app I was taking over. He noticed this as I was about to leave for the evening. I stayed so we could call him (he was in an earlier timezone). Rather than deal with his fucked up, he convinced the manager it would be a "great learning experience" for me to do it ... and stay in late ... while he goes home early.
- He once argued with me in front of the CEO, that his frankenstein cross-platform stuff was the right choice and that my way of using apples storyboards (and well thought out code) wasn't appropriate. So I challenged him to prove it, we got 2 clients who needed similar apps, we each did it our own way. He went 8 man weeks over, I came in 2 days under and his got slated in the app store for poor performance / issues. #result.
But rather than let it die he practically sucked off the CEO to let him improve the cross platform tooling instead.
... in that office you couldn't swing a cat without hitting a retard.
Having had to spend a lot more time working with him and more closely than most of the other nominees, at a minimum "I" is on the top of my list for needing a good punch in the face. Not for being an idiot (which he is), not for ruining so much (which he did), but for just being such an arrogant bastard about it all, despite constant failure.
Will "I" make it to most incompetent? Theres some pretty stiff competition so far
Tune in later for more practiceSafeHex's most incompetent co-worker!!!7 -
People who use drag and drop website builders and call themselves front end developers should just die!8
-
Fun fact: "wix" of wix.com in German language phonetically translates to a vulgar word for masturbation. Not only describes my feeling towards services like these but also gives new meaning to the "do it yourself" mentality.8
-
It's frustrating when you know so many programming languages and your boss likes you to use drag and drop website builders.10
-
Still trying to get good.
The requirements are forever shifting, and so do the applied paradigms.
I think the first layer is learning about each paradigm.
You learn 5-10 languages/technologies, get a feeling for procedural/functional/OOP programming. You mess around with some electronics engineering, write a bit of assembly. You write an ugly GTK program, an Android todo app, check how OpenGL works. You learn about relational models, about graph databases, time series storage and key value caches. You learn about networking and protocols. You void the warranty of all the devices in your house at some point. You develop preferences for languages and systems. For certain periods of time, you even become an insufferable fanboy who claims that all databases should be replaced by MongoDB, or all applications should be written in C# -- no exceptions in your mind are possible, because you found the Perfect Thing. Temporarily.
Eventually, you get to the second layer: Instead of being a champion for a single cause, you start to see patterns of applicability.
You might have grown to prefer serverless microservice architectures driven by pub/sub event busses, but realize that some MVC framework is probably more suitable for a 5-employee company. You realize that development is not just about picking the best language and best architecture -- It's about pros and cons for every situation. You start to value consistency over hard rules. You realize that even respected books about computer science can sometimes contain lies -- or represent solutions which are only applicable to "spherical cows in a vacuum".
Then you get to the third layer: Which is about orchestrating migrations between paradigms without creating a bigger mess.
Your company started with a tiny MVC webshop written in PHP. There are now 300 employees and a few million lines of code, the framework more often gets in the way than it helps, the database is terribly strained. Big rewrite? Gradual refactor? Introduce new languages within the company or stick with what people know? Educate people about paradigms which might be more suitable, but which will feel unfamiliar? What leads to a better product, someone who is experienced with PHP, or someone just learning to use Typescript?
All that theoretical knowledge about superior paradigms won't help you now -- No clean slates! You have to build a skyscraper city to replace a swamp village while keeping the economy running, together with builders who have no clue what concrete even looks like. You might think "I'll throw my superior engineering against this, no harm done if it doesn't stick", but 9 out of 10 times that will just end in a mix of concrete rubble, corpses and mud.
I think I'm somewhere between 2 and 3.
I think I have most of the important knowledge about a wide array of languages, technologies and architectures.
I think I know how to come to a conclusion about what to use in which scenario -- most of the time.
But dealing with a giant legacy mess, transforming things into something better, without creating an ugly amalgamation of old and new systems blended together into an even bigger abomination? Nah, I don't think I'm fully there yet.8 -
CEO calls the Android team in for a congratulatory speech. Likens us to tower builders in the age of cellular tech, building the infrastructure of something great. Then finishes his talk with “and when they were finished, they fired all the tower builders”
I think he was trying to joke, but it sure as hell didn’t feel like it.5 -
"If builders built houses the way programmers built programs, the first woodpecker to come along would destroy civilization." Gerald weinberg.
-
!dev
So the ceiling in our (upstairs) laundry room started leaking. After some troubleshooting, we determined it was the A/C, and not the water pipes. (The house is cheap as hell and fucking stupid.) We did some troubleshooting and research, and tried fixing it ourselves; no luck. Cleaning the pipes from outside: no joy. Cleaning the pipes from inside: no access. The attic is ... small. Maybe half a small closet? and doesn’t give access to fucking anything. The builders must have installed everything before putting up the walls and ceilings, sealing everything off, because there is no access. It’s fucking stupid. Also, the usual maintenance openings aren’t even there either because why the fuck would they be?
But fucking whatever.
We called an a/c repair guy, who never showed. We assumed he was busy (it’s fucking hot), so we called him again the next day; two days later he showed.
Busy. Whatever.
Guy didn’t bring a ladder. Whatever, we have one right there in the hallway because we’ve been trying in vain to fix it.
Guy didn’t bring a wrench of any kind. Guy didn’t bring a screwdriver. Guy didn’t bring a bucket. Guy didn’t bring any pipe. Or any pipe sealant. Or fucking anything but his sagging fucking pants, fat belly, and fat stench. We had to supply everything, which fortunately we had on hand as we were already trying to fix it. Hoorah for being proactive.
Guy said he drained both primary and secondary pans. Somehow. Without access. I’m not even convinced it HAS a secondary pan. Guy said he cleaned out the pipes, too. From inside the house. Without access. Somehow. Maybe he did that from outside, without tools, while I was chasing the brats and someone else was watching the fat bastard. Who knows; I wasn’t with him most of the time.
When he was done, the guy said “pay whatever you think it’s worth” (or whatever). Fine, if he actually cleaned the pipes out and it isn’t leaking anymore, that’s great.
Guy leaves.
We go up to check. AND THE FUCKING A/C IS STILL LEAKING. BUT NOW IT’S FROM BEFORE THE PIPES, TOO. AND HALF AN HOUR LATER, THE LAUDRY ROOM CEILING IS ALSO LEAKING, WHICH MEANS THE PIPES ARE STILL LEAKING.
It turns out the asshole broke the pan.
We call him back, he goes blah blah blah, we send him a video. Drip, drip, drip.
His response?
“The pan must be rusted.” IT’S FUCKING PLASTIC.
“Oh, in that case, it’s probably a rusted coil that’s leaking.”
a) HOW DID YOU NOT KNOW IT WAS FUCKING PLASTIC IF YOU DRAINED IT?
b) THE COILS CARRY FREON, NOT WATER, AND THE A/C IS STILL WORKING. IF THERE WAS A LEAK, SHIT WOULD BE HOT. AND RANK. FREON SMELLS NASTY AND DOESN’T CAUSE IT TO RAIN IN THE FUCKING HOUSE.
REPLACING A COIL IS ALSO A $2000 FUCKING REPAIR.
THE FAT BASTARD PROBABLY BROKE THE PAN INTENTIONALLY JUST TO UPSELL. I WANT TO FUCKING MURDER HIS LYING FUCKING FACE OFF.
It’s possible he didn’t break the pan intentionally, so I’ll tentatively remove that from his charges. BUT TO FUCKING LIE?
LIE AND DIE, FUCKER.7 -
Fuck brand builders, or, how I learned to start giving a shit and love devrant.
Brand builders are people who generally have very little experience and are attempting to obfuscate their dearth of ability behind a wall of non-academic content generation. Subscribe, like, build a following and everyone will happily overlook the fact that your primary contribution to society is spreading facile content that further obfuscates the need for fundamentals. Their carefully crafted presence is designed promote themselves and their success while chipping away at the apparent value of professional ability. At one point, I thought medium would be the bottom of the barrel; a glorified blog that provides people with scant knowledge, little experience and routinely low integrity a platform to build an echo chamber of replayed or copied content, techno-mysticism and best-practice-superstition they mistake for a brand in an environment where there's little chance of peer review. I thought it couldn't get any worse.
Then I found dev.to
Dev.to is what happens when all the absence of ability and skills insecurity on the internet gets together to form a censorship mob to ensure that no criticism, reality or peer review will ever filter into the ramblings of people intent on forever remaining at the peak of the dunning-kreuger curve. It's the long tail of YMCA trophy culture.
Take for example this article:
https://dev.to/davidepacilio/...
It's a shit post listicle by someone claiming to be "senior," who confidently states that "you are only as good as the tools you use." Meanwhile all the great minds of history are giving him the side-eye because they understand tools are just a magnifier of ability. If you're an amazing carpenter, power tools will help you produce at an exponential rate. If you're a shitty carpenter, your work will still be shit, there will just be more of it. The actual phrase that's being butchered here is "you're only as good as the tools you create." There's no moral superiority to be had in being dependent on a tool, that's just a crutch. A true expert or professional is someone who can create tools to aid in their craft. Being a professional is having a thorough enough understanding of the thing you are doing so as to be able to craft force multipliers that make your work easier, not just someone who uses them.
Ok, so what?
I'm sure he's a plenty fine human to grab drinks with, no ill will to him as a human. That said, were you to comment something to that effect on dev.to, you'd be reported by all the hangers-on pretty much immediately, regardless of how much complimentary padding and passive, welcoming language you wrap your message in. The problem with a bunch of weak people ganging up on the voice of reason and deciding they don't want things like constructive criticism, peer review, academic process or the scientific method is, after you remove all of that, you're just left with a formless sea of ideas and thoughts with no categorization, no order. You find a lot of opinions and nothing to challenge them and thereby are left with no mechanism for strong ideas to rise to the top. In that system, the "correct" ideas are by default those posited by the strongest personality.
We all need some degree of positive reinforcement. We also need to be smacked upside the head when we're totally off in the weeds. It's all about balance. The forums of ancient Greece weren't filled with people fervently agreeing with one another and shouting down new ideas en masse. We need discourse, not demagoguery.
Dev.to, medium, etc are all the fast fashion of the tech industry. Personally, I'd prefer something designed to last a little longer.31 -
I am much too tired to go into details, probably because I left the office at 11:15pm, but I finally finished a feature. It doesn't even sound like a particularly large or complicated feature. It sounds like a simple, 1-2 day feature until you look at it closely.
It took me an entire fucking week. and all the while I was coaching a junior dev who had just picked up Rails and was building something very similar.
It's the model, controller, and UI for creating a parent object along with 0-n child objects, with default children suggestions, a fancy ui including the ability to dynamically add/remove children via buttons. and have the entire happy family save nicely and atomically on the backend. Plus a detailed-but-simple listing for non-technicals including some absolutely nontrivial css acrobatics.
After getting about 90% of everything built and working and beautiful, I learned that Rails does quite a bit of this for you, through `accepts_nested_params_for :collection`. But that requires very specific form input namespacing, and building that out correctly is flipping difficult. It's not like I could find good examples anywhere, either. I looked for hours. I finally found a rails tutorial vide linked from a comment on a SO answer from five years ago, and mashed its oversimplified and dated examples with the newer documentation, and worked around the issues that of course arose from that disasterous paring.
like.
I needed to store a template of the child object markup somewhere, yeah? The video had me trying to store all of the markup in a `data-fields=" "` attrib. wth? I tried storing it as a string and injecting it into javascript, but that didn't work either. parsing errors! yay! good job, you two.
So I ended up storing the markup (rendered from a rails partial) in an html comment of all things, and pulling the markup out of the comment and gsubbing its IDs on document load. This has the annoying effect of preventing me from using html comments in that partial (not that i really use them anyway, but.)
Just.
Every step of the way on building this was another mountain climb.
* singular vs plural naming and routing, and named routes. and dealing with issues arising from existing incorrect pluralization.
* reverse polymorphic relation (child -> x parent)
* The testing suite is incompatible with the new rails6. There is no fix. None. I checked. Nope. Not happening.
* Rails6 randomly and constantly crashes and/or caches random things (including arbitrary code changes) in development mode (and only development mode) when working with multiple databases.
* nested form builders
* styling a fucking checkbox
* Making that checkbox (rather, its label and container div) into a sexy animated slider
* passing data and locals to and between partials
* misleading documentation
* building the partials to be self-contained and reusable
* coercing form builders into namespacing nested html inputs the way Rails expects
* input namespacing redux, now with nested form builders too!
* Figuring out how to generate markup for an empty child when I'm no longer rendering the children myself
* Figuring out where the fuck to put the blank child template markup so it's accessible, has the right namespacing, and is not submitted with everything else
* Figuring out how the fuck to read an html comment with JS
* nested strong params
* nested strong params
* nested fucking strong params
* caching parsed children's data on parent when the whole thing is bloody atomic.
* Converting datetimes from/to milliseconds on save/load
* CSS and bootstrap collisions
* CSS and bootstrap stupidity
* Reinventing the entire multi-child / nested params / atomic creating/updating/deleting feature on my own before discovering Rails can do that for you.
Just.
I am so glad it's working.
I don't even feel relieved. I just feel exhausted.
But it's done.
finally.
and it's done well. It's all self-contained and reusable, it's easy to read, has separate styling and reusable partials, etc. It's a two line copy/paste drop-in for any other model that needs it. Two lines and it just works, and even tells you if you screwed up.
I'm incredibly proud of everything that went into this.
But mostly I'm just incredibly tired.
Time for some well-deserved sleep.7 -
I really hate fucking Wordpress!
I hate it's stupid API, with it's stupid hooks and actions and all those stupid functions and no fucking logic to any of it!
I hate it's stupid plugin system, with all that fucking overhead that brings no real value and adds all that complexity for nothing!
I hate stupid fucking multiple calls for the same fucking assets, loading them over and over again because every stupid plugin calls them again and again!
I hate motherfucking SHORTTAGS, or whatever the fuck they are called!
I hate that every stupid fucking plugin and shortcode and fucking every little fucking piece of HTML comes from a different fucking place, with different fucking structure and different fucking classes and stupid fucking loading seaquences that make no fucking sense!
And I hate fucking page builders !!!!!
Fuck!!!!
I should be fucking coding on this fucking peace of shit, but I just cannot fucking take it any more!!!
IT NEEDS TO FUCKING DIE!
It should be relegated to the darkest corners of the internet and all the servers that have it's fucking code anyware on their systems should be disconnected and buried in the deepest pits of hell, just to be sure it never, EVER, surfaces again!!!
AAARRRRGGGHHHHHHH !!!!!!!!!5 -
> 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 -
I might be fucked up, but I have a tendency to gravitate towards the shit that everyone else dislikes for the sake of knowing if their bias against is actually because shit is truly fucked up or if shit is legit plain WRONG.
From all technologies that I have worked with professionally I can count:
Java(currently in the form of old JSP services for an "enterprise level application")
Java for Android development - i was the lead engineer for a mobile project
Swift with IOS dev, same gig as the above.
C++ for Android development in the form of OpenCV with Java as well.
Javascript in all possible forms, basic input validation, ajax services, jquery datatables, jquery animations and builders.
Css/sass heavily
Clojure for an ldap active directory application
Python for glue scripts
Classic ASP with JScript and VBScript
VB Net forms
C# For ASP.NET MVC
Bootstrap for multiple intranet frontends
Node+Express for a logistics warehouse management tool
Ruby on Rails freelancing small gigs
Php in all ways possible from complete standalone php apps to Laravel and just php+composer apps aaaaall the way to wordpress
Django consulting
I have found that the one that I dislike the most is wordpress. And the one that I like working with the most is Node. Don't know why, i just do really fucking like messing around with Javascript, the language has changed a fuckload throughout the years and continues to increase and change. It was my first scripting language following a stint in me trying to learn cpp way when i was starting and royally FAILING
Never really got the hate for it, even when I used JScript with classic ASP i just enjoy working with Javascript a lil too much. And from all the above mentioned stacks safe from Php is the one, or one of the ones in which i don't royally suck :V3 -
- Fuck mobile apps that open links in embedded browser windows
- Fuck Wordpress page builders that use the single content field as an embedded IDrag&DropE.
- Fuck unindented HTML markup
- Fuck plugins with "pro" versions that provide more than 50% of the advertised features.
- Fuck building an app with a SPA framework and then adding SSR cuz ur SEO is fucked.
- Fuck Javascript transitions that are meant to make a site look fancy but slow it the fuck down.
Fuck it.
Vent your frustrations9 -
Really getting tired of these web design ads. I would turn on Adblock but I want to support YouTubers that are actually interesting to watch. I saw this ad today, Divi. A plugin of some sort for WordPress and the lady in the video is talking about how building a website is like painting a master piece but not really. And then goes on about "creating" a website with their tool on the page itself. (Like a Wix or Weebly but on the actual page and live). I watch the video to the end and decide to check the comments and someone said "or you know, learn HTML and stop being lazy" *liked* then one smart ass replied, "or use Wix, or use Weebly, or use any other thing online that lets you design a website without typing code". It annoys me how ignorant people can be about designing, but I don't blame them. People are lazy in general and would want to do things the easy way even though it's not the best way. You know the saying, give a man a CMS or WYSIWYG builder and he'll make a website, but teach a man to code and he'll make more, improved websites.4
-
While reviewing a PR from one of our newer FE devs, I ended up spending more time than I would like mulling over its composition. The work was acceptable for the most part; the code worked. The part that got me was the heavy usage of options objects.
When encountering the options object pattern (or anti-pattern, at times) in complex scenarios, I have to resist the urge to stop whatever I'm doing and convert it to the builder pattern/smack them in the head with a software design manual. As much as I would like to, code janitor is one of the least valuable activities I engage in daily, and consistently telling someone to go back to the drawing board for work that is functional, but not excellent is a great way to kill morale. Usually, I'll add a note on the PR, approve it, add a brown bag or two on that sort of thing, and make attendance mandatory for repeat slackers. Skills building and catharsis all rolled up in a tiny ball of investing in your people.
Builders make things so much cleaner; they inform users what actions are available in a context; they tend to be immutable, and when done well, provide an intuitive fluent interface for configuration that removes the guesswork. As a bonus, they're naturally compositional, so you can pass it around and accumulate data and only execute the heavy lifting bits when you need to. As a bonus, with typescript, the boilerplate is generally reduced as well, even without any code generation. And they're not just a dumping ground for whatever shit someone was too lazy to figure out how to integrate into the API neatly.
They're more work in js-land, sure; you can't annotate @builder like with Lombok, but they're generally not all that much work and friendlier to use.
9 -
I just remembered that when I was a kid, it was really popular to make personal websites with those simple website builders. Wanna know the funny thing? My parents wouldn't let me build my own website. Well look what I'm doing with my life now mom 😂
-
Get an email from a client, who has been stringing me along for about 6 months, but ringing me up for advice on tonnes of different shit for free. Basically did his original website but his business model has changed to make his existing site irrelevant. Suggested months back doing a simple one pager as a stop gap with key messages. The bastard said no to that "just take it down for now and redirect to my LinkedIn page". He keeps saying we are getting stuff together and we hope to get together in September. However, yesterday he sends an email "we are getting a student in over the summer (not a Dev or designer or anything). Could you recommend any "web builders" so we can get on with the website in August. By that he means those drag and drop fucking pieces of shit website templates full of wysiwyg editors for creating shit typography. I give them free help and guidance and they think that I'm not going to want to smash him in his fucking face for his last email. The cunt.
I have an idea for 'having the last laugh' but I am open to suggestions from some devRanters, all legal of course.
P.S. I post quite a bit here about shitty clients, but I do have a number of really good clients who value my work and experience and have been with me for many years. It's just some that treat the profession with disdain and that they can easily do it themselves if only they had the time. These fuckers then wonder why their businesses fail.1 -
From the Chromium mailing list:
TL;DR - 32 bit is no more (?)
Hi, chromium devs,
TL:DR;
I will remove following 4 builders next week.
Linux Builder (dbg)(32)
Linux Tests (dbg)(1)(32)
linux_chromium_compile_dbg_32_ng
linux_chromium_dbg_32_ng
More explanation:
For now, chromium does not support 32 bit Linux
https://support.google.com/chrome/...
and all 32 bit x86 devices for chromeos is EOL too.
https://chromium.org/chromium-os/...
Considering that, I was not able to find any reason we have builders for not supported platform now.
If you have any comments about this builder removal, please let me know.
I will start removing process of the builders next week if there is no concern from you.
Note: This removal does not include 32 bit android/windows/libfuzzer or other than chromium builders.
Thanks,
Takuto
--
Takuto Ikuta
Software Engineer in Tokyo
Chrome Ops (goma team)8 -
A story about RAM and being... well... not so clever...
I've built a mid-range gaming PC for a friend, based on skylake, with 8GB DDR4 RAM. So I filled up only 2 slots to leave 2 more for upgrade. So he decided to do so.
Later he calls me and says "Hey, can you visit me? My PC won't boot".
So I came and he told me what happened: he found a random RAM stick and decited to put it in. He somehow(wait for it) managed to do it and PC refused to boot. He removed this stick, but PC won't boot anyway.
Soo, when I came, he showed me a stick he found: a random ddr2-533mhz 512 mb stick. Ofc, MB was shocked to see "grandfather" and refused to boot. I looked at the post code, which said ram error, cleared the cmos and it booted just fine.
Check compatability, young builders, and use Google if you're unsure :)9 -
All those website builders, tools and frameworks were designed to make tech illiterate people be able to create websites, so how fucking dense are all those people that publish jobs to create a website with a literal click & drag tool or website builder?!
Example: http://grapesjs.com/ is very popular amongst those searching - though this seems would have to be published manually after creating it, so I would understand help with publishing, but theres websites also mentioned like squarespace, which has seriously no excuses besides being that lazy and forcing somebody to chew it for you
I see maintainability of the website later on of course as a handy argument for them to use those kinda tools and websites, but what do you need somebody to do it for you from the start, if you plan on later then manage it the same way?
4 -
Any other Screeps players here?
for the people running into a "Screeps is not defined":
Screeps is a MMO RTS where you code your "army" to do stuff in Javascript (a la NodeJS).
Code how your harvesters should behave, how your soldiers should behave, how your builders should behave etc. etc.
So far, it is quite a fun game, tho my (Intel Nehalem based) laptop has issues handling it (thanks to a awfully slow GPU...) so it's difficult to play for me at the moment (I'm on holiday, my home PC is a LOT faster).
It costs about 15 euro on steam, and if you're into this stuff, it's well worth it.
Just make sure you finish the tutorial first... I didn't and I regretted it when I bought the game (it's a huge pain in the buttocks to get started if you don't understand the API and such).
Currently just playing on my own localhosted private server to discover how the game works and such, but will be setting up a public server later down the road to play with others.
Tho it would be nice if Screeps would allow for "team-based" gameplay as well so it'll be slightly harder for early players to bully the newer ones.2 -
!rant;
Just started a new react-native project :O Someone has build an app to help app builders build apps :O
You start the node process, scan a QR code and BOOM app is on your phone...7 -
Applying Occam's razor and I might be wrong..
Hiring a candidate and job hunt, both are fucking exhaustive process.
We, as a human race, have aimed for Moon and Mars but are unable to solve the problem at hand which can save millions of hours each year reflecting in immediate cost savings.
Here's my (idealistic) solution:
A product to connect job seekers and recruiters eliminating all the shitty complexities.
LinkedIn solved it, but then hired some PMs who started chasing metrics and bloated the fuck out of the product.
Here are some features of the product I am envisioning:
1. Job seeker signs up and builds their entire profile.
2. Ability to add/remove different sections (limited choices like certifications, projects, etc.), no custom shit allowed because each will have their own shit.
3. By default accept GDPR, Gender Identity, US equality laws, Vetran, yada yada..
4. No resume needed. Profile serves as resume. Eliminate the need to build a resume in word or resume builders.
5. Easy updates and no external resume, saves the job seeker time and gives a standard structure to recruiters to scan through eliminating cognitive load.
6. Recruiters can post their jobs and have similar sections (limited categories again).
7. Add GDPR, Vetran, etc. check boxes need basis.
8. No social shit. Recruiters can see profiles of job seekers and job seekers can see jobs. Period.
9. Employee working in Google? Awesome. Will not show Google recruiters thier profile and employee such job posts.
10. No need to apply or hunt heads. System will automatch and recommend because we are fucking in AI generation and how hard it is to match keywords!!
11. Saves job seekers and recruiters a fuck ton of time hunting the best fit.
12. This system gets you the best job that fits your profile.
Yes, there are flaws in this idea.
Yes, not all use cases are covered.
Yes, shit can be improved and this is hypothetical.
But hey! Surely doable with high impact than going on Moon or Mars right now.
Start-up world has lost its way.12 -
So, it was kinda a reversed effect?
My parents didn't give me access to computer for a long time, the only option was to play games with my dad. I also didn't have a phone for a quite long. And, when I see what is happening today with the kids that get their first own phone/tablet at age of 4, I am really happy about it.
But, somehow, that made me really interested in what runs all the squares on the screen etc. When I convinced my parents to give me my first laptop — to play Minecraft with classmates — almost the first thing I did after installing the game was searching "how to make a website". I played with some shitty builders, then I discovered HTML (which was :o for me then). Small steps into PHP, then some JS. I really enjoyed it, but PHP gave me headache each time I wrote something bigger (I was writing a super spaghetti code then, I was inexperienced), so I thought of trying something else...
Minecraft plugins!
I fallen in love with Java.
And after that the real journey began.5 -
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along wound destroy civilization." - Gerald Weinberg3
-
our school says...
This school homepage was developed in 2008 as a builder.
IE7 was the main browser at the time of 2008, but now IE11 is being used as the main browser.
We are currently working on developing a school website builder that is suitable for modern browsers and sequentially converting all schools into new builders by December 2017.
Therefore, please use the Chrome browser to use and operate stable website when accessing the school website.
Oh...
But WHY ISN'T IT WORKING IN CHROME, EITHER???!!!!1 -
"Non-technical" users must have some magic skill that goes beyond my understanding. How can anyone work with no-code page builders? I tried Wix, Webflow, Gutenberg, Elementor, Divi, and Semplice. Each one sucks in their way, but they have one thing in common: their UI behaves even more erratically than Microsoft Word.
Is there a "non-technical personal computer user" class where people learn that logic? How did they manage to hide their secret understanding from developers? Or what did I miss?10 -
I hope this book finally makes me understand factories that make builders that make classes that make fucking objects.
Sorry for the bad light btw.
8 -
My worst habit(?) is probably loving to "waste" time, making api uri builders.
so I can chain a couple of methods instead of just typing out an uri :p -
Yes WP sites can be bad.
But as bad as it can be, just as easy it can serve as a good kickstarter for the next website.
If just the developer behind said website has some kind of dignity about the code they produce and respect for their fucking job!
1. Don't use bloated plugins.
2. Always vheck out alternatives.
3. Don't ever use paid plugins/themes... just don't.
I for one, whenever installing a plugin, if said plugin generates any kind of unexpected output such as a notice it's an immidiate uninstall, and then rolling my own.
I also use a bare minimum boilerplate theme which does not bundle any frameworks, additional libaries or other kinds of that bloatware for all my wp sites, this ensures that every site is somewhay unique.
I've seen so many "devs" being lazy as fuck, using the wrong themes/plugins to "code" the site.
No! using page builders such as visual composer or bloatware slideshows does not count as good tools.
If you buy a theme from themeforest thinking it will save you hours of custom development, then fuck you... go drown in acid.. because guess fucking what?
It will save you absolutely jack shit in the long run..
Anything stating otherwhise is marketing bullcrap4 -
Looking further into Rust, the macros are quite sexy. My first reaction was "omg really"? But then I learned that macros in Rust are nothing like macros in C++.
Again, comparing with my favorite language Swift, it feels like Rust macros are somewhat similar to result builders (formerly named function builders). Or they they have a similar purpose. Both evaluate to some type safe result at compile time and are a perfect tool to make DSLs.
But Rust’s macros can do even more than that. It’s truly amazing.2 -
I started learning WordPress out of curiosity.
Configuration and deployment was easy peesy.
Site is up and running, BUT
Real challenge is, customize it according to clients requirement.
I purchased paid theme as well. It has theme builders installed to.
But I couldn't make it according to client requirements.
I neither found any resource where I could learn WP site customization.
What I'm doing wrong?18 -
Guidewire is the work of satan. It is the worst framework I have ever worked with. OOTB code is full of antipatterns, creating gui is a pain, and it has its own language that is a pure joke. Every task I had had to have some sort of workarounds. You cant junit test it. Entity builders are a mess and you cant mock gosu classes. I hate it so much.
-
Ok so, Android devs/Unix kernel builders I have a question.
How can I set `make` command to speed up the building process?
I'm very confused because of the N in the `-jN` parameter.
I read someone suggesting N=n_cores+1, btw I have an old dual core PC without hyperthreading eoth 4gb RAM.
If someone can explain me how this parameter works and how ti use it in order to minimize the building time I would be really grateful.
Thanks :)1 -
Sometimes I wonder we make too much or at least the devs at corps.... (Not a bad thing...)
But compared to everyone else like chefs, teachers, builders, scientists, etc that actually need to revert physical labor... We just push buttons all day or half the day...
Just looking over this month's income... Basically only spent 10%...
An I really worth that much... To me the work I do isn't hard... Or don't see how it connected to the bottom line...11
Top Tags
Weekly Rant
View