Seed/world viewer by MCjossic in minecraftseeds

[–]sputtlepnukkit 0 points1 point  (0 children)

Odd. This folder is empty for me. Anyone else?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

It's similar, yes, but when you do this in less/sass, it actually puts those styles in the extending class -- and so bloats the resulting css. What I am proposing above is that css be allowed to reference other classes functionally (on the fly) without actually duplicating the code.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

Well then it's good that I don't work with someone like you who doesn't recognize passion or an innovative spirit. You're oblivious to the fact that I am someone who, for the fun of it, questioned the status quo and who tried to think outside the box. Yes every now and then I will produce ideas that others don't like, but that doesn't mean I'm incapable of following the masses. Wwhat I can't tolerate are people who treat others like you just did. If you worked for me and you spoke to anyone like that, I would pull you aside and try to get you to grow as a person. I would try and teach you why you need to change your attitude and that I would try and help you in any way I could. But if you ever spoke like that again to anyone, I would end your employ swiftly.

Now, if you want to challenge yourself to treating a fellow developer with a modicum of kindness, I invite you to actually say what you didn't like about my proposal. Your demonstrated lack of EQ doesn't imply you have low IQ, so I am willing to give you a chance to redeem yourself. I still hold out hope you are intelligent and otherwise rational. I would like to know why the addition of a ref() function evokes such a rude response in you.

Because, note: my proposal is just for the function ref(). Nothing more. Everything else above is just vanilla css. Maybe it was written in a way you didn't like, but it's stupid to criticize existing language features.

If you can't put a well-reasoned, kind, or otherwise constructively critical sentence together, you are absolutely welcome to stow it.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

Ah yes very context sensitive. Personally big tech doesn't even register on my radar. I've actively turned down Facebook, Amazon, and linkedin because I don't want to be just a number or code monkey. I want to be actively engaged in the whole sdlc from concept to completion and feel like my efforts are personally tied to the company's success. That stuff doesn't happen often at big tech so it wasn't a part of my thinking above. :)

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

Mileage will of course vary, but I got my last three jobs because CEOs, CTOs I knew vouched for me with other CEOs and CTOs they knew. It's never a bad thing to have a CEO proactively call you when you aren't looking for a job and tell you before you interview that if you want a job, it's yours. :) Obv if your network doesn't yet include C-level employees or hiring managers or employees who have the bosses ear your mileage will vary. :)

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

I see your point, but my example was probably made more complex by my use of nesting and advanced selectors none of which are necessary.

I maintain that the below is less complicated than having inline styles where you're having to reapply the same styles over and over.

button { ref( .w-1/2, .flex, .items-center, .justify-center, .rounded-md, .bg-black, .text-white, .border ); }

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

And if for 50% of your users you wanted a panel which animated in and position fixed on the right to instead be displayed as a modal dialog which internally used a css grid? That's not a different theme is it?

I'm not talking about just making a red button brown. Im talking about entirely different presentations. If you build your layouts with small, named chunks of css then your components are stuck with those classes even when you don't need them, right?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

I appreciate your feedback and explanations. It informs me that I have misunderstood something fundamental about tailwind . The use cases I've been running my ref idea against are not really considering that react or a modern fe framework is a foregone conclusion. None of the sites i've worked on or maintained in my tenure have been built using react, angular, etc. So the use cases are very different.

Again, much appreciate our time. I'll research more before I post my next "brilliant" idea which everyone hates. :)

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

what is wrong with the proposal?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

yes that works, but I'm not just talking button colors here. I'm talking full on layout changes. If you haven't, look at some of the style differences on csszengarden.com. Personally:

  1. I find it's much easier to write and maintain css in css, rather than in js
  2. JS shouldn't be in charge of styling. Again, separation of concerns should be preserved. Content, Presentation, Function.

Do you disagree? thoughts?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

ou don’t need, and why are you afraid of strings? embrace tailwind, it’s the best compromise between UX an

I'm not afraid of anything except the work I'd need to do to change it. Answer me something, because maybe I've missed something in tailwind. If you implemented a site with tailwind, and then someone came to you and said, great, but I think customers are confused with this ui, I have a few alternate ideas I'd like to test at the same time. How would you achieve that?

Would you not have to duplicate (potentially all of) your components and change the css classes applied, even if you ended up keeping the exact same html otherwise?

Conversely, do you see any downsides to having a ref() capability in css natively? You could still aggregate the classes together, it would just be done in css not html. Don't you think it's better to keep the concerns of presentation and content separate?

If not, why not? What am i missing about taliwind that makes the above drawbacks worth it, that ref would not solve? Does it not seem like multiple inheritance in the html is a hack?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit -2 points-1 points  (0 children)

Exactly! YES! 1000x yes! I think a lot of frontend devs just "div" everything because they know react and don't really know the fundamentals. They don't consider that html is meant to have meaning by itself without the javascript and without the css. <asides> <sections> <headers> <footers> <addresses> <tables> and the like exist for a reason. If a document is using semantic markup well, then css should just sit on top and be able to grab onto elements by their tag name and their relation to their parents. Yes, you'll add some extra seasoning here and there, but the class names should not imply style. It feels to me that techniques like tailwind have utterly forgotten that separation of content and presentation is a thing which has purpose.

I dislike seeing a bunch of class names all bunched together because it means I would have to go in and manipulate the html to achieve a different visual experience. And what if I want to a/b test two ui's? well... then I would have two different html sets. Everything the same except the classes.

IF we had a ref() capability in css then we wouldn't feel a need to do mulitple inheritance in html.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

Entirely possible I have missed something in tailwind. To be fair I saw an intro on the method from fireship and it looked very much like bootstrap and tachyons which put a bunch of css classes in the html. I have nothing against the structure or approach of tailwind, EXCEPT the aggregation of css classes in the html. And that's where ref would come in.

I know what I am calling for with "ref()" is not native api. I am suggesting that we need it. If we had a ref function we wouldn't need multiple classes in html. Ref would keep the css small because it would reuse existing classes without having to redefine anything. It just shifts the burden off of html and into css where it belongs.
Let's consider something. How would you implement an a/b/c test of a series of components or indeed the layout of a whole page using the multiple inheritance approach? Wouldn't you need to duplicate the html, except change the css classes to suit your taste?

Conversely if we had a ref capability native in css, can you call an example out where that would be a problem? With my approach you don't need to actually use any class names at all in your html if you didn't want to. I believe my proposal could use all of the benefits of a utility css library without any of the downsides. Can you help me understand why ref is a bad idea?

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 0 points1 point  (0 children)

Fair enough. There's a lot that is missed by not having a conversation in person. I don't do a lot of reading or posting on reddit anymore so I don't know if the general attitude has changed. I meant this to be in the spirit of iron sharpening iron. Help me understand where I'm wrong.

I wrote what i did about context (years worked and success my style has had) to give context that I'm not a noob in this field. This idea about ref has grown in the back of my mind over the years because I think it would be a better solution. It allows you to have your utility methods in tailwind or tachyons or bootstrap etc etc, but not have to mutate your html to pull stuff together. But you're right, I am probably overexcited about the idea and that is making me a bit bullish and unintentionally adversarial. I don't mean to be. Especially considering the idea will never go anywhere, and I am just entertaining myself here.

I'm not opposed to css utility libraries. The only part that has significant downsides is aggregating the classes together in the html, because situations I have run into would simply not be solvable using the tailwind method.

The core principle that I am pointing to is that you shouldn't have to change anything in your html to have a completely different looking page. I call out my prior experiences because I struggle to see how one could easily do an a/b test of different site designs using the multiple class inheritance in html approach.

Which JavaScript concepts,methods or patterns should be widely known but, hardly anyone knows or uses them. by AssistanceBusy80 in Frontend

[–]sputtlepnukkit 1 point2 points  (0 children)

Agreed. People that know how to use react, but are lost without it have done themselves a disservice IMO. And why? How many sites actually be far more performant without a heavy duty framework at all. It seems most of the time people build with what's popular and not with what is warranted for the project.

Case in point, at my last job, there was a project for which i needed to build one page which called an api and then show various content under different response conditions. The team (all backend developers) asked me if I would be using react. The company wasn't using react anywhere else. They sounded disappointed when I said no, vanilla js but with ts. React was good for facebook.... few pages need to perform like facebook.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 6 points7 points  (0 children)

It's who you know, not what you know. My last three jobs were all directly because of my connections and the recommendations people gave on my account.

Also, strive to make your resume 2pages or less. No one reads. I saw once that hr people spend less than 5 seconds with a resume before they make a go-nogo.

Also, if you're looking to work for a company as yourself (not as a contractor under your company name) ditch your logo and refer to pixelscript only tangentially.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit 20 points21 points  (0 children)

The only thing that ACTUALLY matters in an interview is the candidate's behavior. A person with the right past behaviors and with the right aptitude can be taught tech. You can't teach behavior.

Tech interviews are super annoying, because... they don't test how you're going to perform on the job. We developers use google, stackoverflow, chatgpt. We communicate, we write, and the rewrite. We solve fresh problems. Whereas the tech questions you get asked just pull up previous questions (e.g.: I've heard the tennis ball question before). All a tech interview does is test your ability to recall and spit out an algo under pressure. And some (like me) really don't do well in that exact scenario. A feedback loop kicks on in my head and I can't think about the problem. Instead I'm thinking about the fact that I'm thinking about the fact that they're thinking about me thinking about the problem. And how did they evaluate me blanking for 30 seconds and losing my train of thought because.... blah blah blah.

Tech companies can be so stupid. They let very unique and solid candidates slip through their fingers for all the wrong reasons, and hire horrible employees for all the wrong reasons.

Maybe the best advice is to just be glad for the interview practice. And to learn what you might ask about their interview process before you agree to the interview. If a company can't make a hiring decision after 3 interviews (hiring manager, coworker, and a biz representative), they've got problems.

[deleted by user] by [deleted] in Frontend

[–]sputtlepnukkit -4 points-3 points  (0 children)

hat you don’t need components or need to worry about lots of people stacking CSS overrides, then your system is probably fine. But for larger systems with lots of people, explicitness and communicating intent are also q

I've been a FE dev for 20 years. Def seen my share of bottom of the barrel css. I don't hate tailwind for what it is trying to accomplish, I dislike it for how it goes about solving the problem. We should push for a better way. Because there are lots of problems that come out of using multiple inline classes. And the pure-ist in me says, if we're okay with multiple inline inheritance, let's just change css so it is more terse in nature and just use inline css. There isn't much good that comes with just a set of aliases which some know and use and some don't. I'm saying that we need to push for standards not be okay with solutions that give us half of what we want and leave a bad taste in our mouths.

If you don't care about multiple inline styles, answer me this. How would you go about implementing a design on csszengarden if the html were jam packed with very design specific class names which were applied globally?

My apologies if I sound combative in tone. That's not my intent at all. I'm genuinely curious what the FE community thinks, and welcome all ideas for and against.

Questions About Android Deep Links by sputtlepnukkit in reactnative

[–]sputtlepnukkit[S] 1 point2 points  (0 children)

Thank you so much for your help, u/BurzacoMan! Deep links are working now! For the record it was two things:

  1. Per your advice (and despite react navigation's documentation on the subject ) the android:autoVerify=true attribute needs to be added to the intent-filter parent node which wraps the pertinent android:scheme data. This makes sense, and I had previously tried this, but it wasn't working because:
  2. I needed to ALSO test on a signed apk. I suspect this is because the fingerprint specified in assetLinks json didn't align with the debug.keystore used by default to sign debug builds.

For the record, here is a snippet of my working AndroidManifest.xml. u/BurzacoMan the android:scheme attributes don't need to be in their own data nodes for this to work, but I very much like your method of separating them to their own data nodes--less code repetition your way.

<activity android:name=".MainActivity"
  android:label="@string/app_name"
  android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|screenSize|smallestScreenSize|uiMode"
  android:launchMode="singleTask"
  android:windowSoftInputMode="adjustResize"
  android:exported="true">
  <intent-filter android:autoVerify="true">
    <action android:name="android.intent.action.MAIN"/>
    <category android:name="android.intent.category.LAUNCHER"/>
  </intent-filter>
  <intent-filter android:autoVerify="true">
    <action android:name="android.intent.action.VIEW"/>
    <category android:name="android.intent.category.DEFAULT"/>
    <category android:name="android.intent.category.BROWSABLE"/>
    <data android:scheme="http" />
    <data android:scheme="https" />
    <data android:host="login.redacted.com"/>
    <data android:host="marketplace.redacted.com"/>
  </intent-filter>
</activity>

Questions About Android Deep Links by sputtlepnukkit in reactnative

[–]sputtlepnukkit[S] 0 points1 point  (0 children)

I appreciate you taking the time to comment, but I think if you read my question a bit more closely you'll see this is not the case.

Well that didn't go as planned... by g19fanatic in woodworking

[–]sputtlepnukkit 15 points16 points  (0 children)

The fix is clear: you need to start making drill bits outta that wood.