HN user

whsheet

58 karma
Posts1
Comments36
View on HN

OT: Am I the only one who thinks that most meetups are crap? The idea of meeting like-minded people is tempting but the reality is always different: Crowded places, stuffy air, weak talks, lame sponsors, 1-to-n presentations, no real interaction, stale drinks out of thin plastic cups, odd devs

Only when I am super addicted to HN and only when I am submitting I am going through the New Tab.

Think the current system is broken and have the feeling that in the early votes is too much bias (either through high karma folks, maybe internal hidden push votes etc from HN internal circles eg. admins, alumina).

Btw very good question and I’d love to see someone from HN giving an official statement plus comment how much HN-internal bias might influence the early votes.

Nice content marketing piece and guide for an SEO beginner but I stopped reading here:

all with a 95% SEO acquisition strategy

That's so wrong. Free organic traffic is great. But if you rely fully on organic traffic, it rather shows that your LTV is not bigger than your CAC and if Google or competition kills your search traffic, your business is done and/or you can't scale when your mighty SEO doesn't work anymore.

You are def right that I should not pack everything in a non-tech cluster and call it crap. However I'd still keep my initial statement, it's a simplicatiom but it's true.

Of course there are and must be great blogs in non-tech areas but they are not that many. Writing high quality blogs for free seems not be common in other fields. Often people rather publish the findings in a protected space, call it academic paper and I can read just a lousy abstract. Actually most academic non-tech fields fall in this category.

Apologies for the attack, couldn’t resist. However, what you wrote is common sense and you should assume that anyone lurking around on HN knows that stuff. I mean you actually described the page rank algorithm which was the foundation of Google but there are many more signals nowadays. So your post felt like a (small) attack too.

FYI, Google runs quite a large spam team which flags scammy sites manually. Sites with such a modal are usually rather on the spammy side of life and gets flagged by the team. If you get too many flags you get severe penalties slowly eating your traffic in a way that it’s not clearly obvious and it can take years to recover.

But since it’s Medium such UI seems to be tolerated.

If I ran that team I would have killed Medium's, Quora's and Pinterest's search traffic. And soon maybe StackOverflows as well.

hit the casual crowd

Forget the casual crowd. First reason: It’s always good to start with one demography and fulfilling their requirements. Second and TBH, the casual crowd sucks steel when creating short-form blog content.

Go to the Linkedin blogs, all non-tech Medium blogs, TED talks, Facebook: 99% is useless, already seen, self-help-type advice covered with click-baity titles.

Every Reddit post has more substance and authenticity than the mentioned above.

Edit: To the pro downvoters, instead of downvoting just reply and link to one eg. single useful non-tech Linkedin blog.

I disagree. Use your time to setup something smarter than a blog. A turn-key ready static site generator still takes 10x the time to set up than just using a random blog site.

Also, you waste time fiddling with CSS adjusting crappy themes. Only upside would be post editing in vim.

But again, do something smarter, too many new shiny toys wait for you: Tensorflow, Haskell, Rust, ESP32... extend the list yourself.

Able looks promising: Higher information density than Medium, syntax highlighting in code blocks, no big-ass modal interrupting when I just want to read a silly blog post.

Besides, Medium in its current state is one of the most annoying sites and I don't get why it enjoys such a strong SERP ranking. I mean blog posts are a commodity and Medium thinks they are Netflix showing the latest Disney property.

If Google search devs read this: Demote all Medium results.

Show HN: Darklang 7 years ago

I can deploy a Docker-based node backend with basic functionality from my phone's ssh client in five minutes.

Give me a bit more time, a keyboard and I could build you any API endpoint, http server, glue code between DB or even low level proxy server functionalities.

No offense but isn't the 'problem' backend solved years ago?

I agree but this might be already useful. The biggest challenge for most when they work from home is lacking social pressure leading to procrastination. When I read about Tandem's take on this, I thought that’s a smart, subtle solution. You could still game the system by just using your phone but still: Any cheating results in odd behavior on Tandem and probably to more discipline. Maybe I am wrong but I need just people who tried Tandem and share their experiences.

In this context: Does anyone have experiences with Tandem, especially this feature where you can see what your peers are doing (showing the app name of your focused window, I think)?

All good and sorry, maybe my initial comment was still offending.

However and what I meant is that your writing style, also looking in the comments here, is for my taste a bit too fluffy, elaborative, zealous and making it hard for the reader to grasp the essence of your statements quickly. If you can’t win people with words your lib won’t have the chance get tried.

While I like new takes in frontend, the overall wording was the reason not to read more about Connective but rather leave a snarky comment.

TypeScript 3.6 7 years ago

Not going to discuss this further. You have a dogmatic view on what is an excellent type system.

Anyone who makes serious money with his notebook moved away from Apple years ago. I can't take people serious buying Macbooks in 2019 posting a rant about, oh surprise, the broken keyboard. This is a well known fact and if you don't develop for iOS there is no single reason or lock-in forcing you to use Macs.

TypeScript 3.6 7 years ago

Disagree. TS' type system is fully featured compared to others and what you described as an disadvantage is actually an advantage or TS' killer feature: you can gradually convert a dynamic code base into a static one where needed. IDK of any other language that allows this.

TypeScript 3.6 7 years ago

For prototyping using React and TS sounds like a bad idea, because React is not that well supported by the TS community.

Not really true and guess you misunderstood me and are not on the latest state of things. You can perfectly use the TS compiler as the compiler for your JSX code. Then you can decide case by case when to use TSX or not. and many major libs (mobx, formik) are written in TS and perfectly support TS.

I'd disagree with you statement that long usage of a typed language makes you faster. It is about choosing the right tools and static typing ist not always the right answer. But this is exactly what annoys me: the urge to evangilize everyone with static typing.

TypeScript 3.6 7 years ago

While I think that TS offers probably the best type system out ther, eg way better than Go's, I'd love to see a more balanced view on TS in discussion threads like this one.

TS is a must for long-term code which should be maintainable in several years by teams. Any lead engineer with responsibility for some crucial app and dev team not using TS is doing something wrong. But using TS comes at a cost. Even when you are savvy in TS you won't bang out code like with pure JS.

But especially in prototyping phases you need this fast-paced coding. And using TS or any type system slows you down, even when you are familiar with typed languages. Often your final code faced many iterations and I sometimes like to introduce TS later, usually at a point where I just need types but not always and as default from the first key press. In early stages I still try to test ideas, algorithms and their general feasibility and a fast 'mind-to-code' interface is crucial and types would stay in the way then.

Further, finding the right type can take some time, just google what type a React's children prop should be and find long discussions. Welcome to the TS-what-type-is-actually-xy-rabbit-hole. And declaring everything as any shouldn't be the answer.

A big drawback are also TS error messages which are super hard to grasp. You get there and you even find tutorials just for understanding TS error messages but it's unecessarily infuriating.

Moreover, VSCode, its TS language server are amazing pieces of tech but here you face also strange behaviours. Types get full Intellisense support while interfaces don't which doesn't make sense. So you need still to go the definition yourself and it's not that IDE-like feeling you hoped for or people told you.

In my setups, I use TS instead of Babel but use both JS and TS files in one code base depending on the requirements and situation.

So, my message is, yes TS is great, has probably the best type system but the tonality by its community/users needs to be much more balanced and less fanboy-ish. I just can't take devs serious who praise TS to death. This is just not true. More, maintainable code is also not just created by a type system but also sane architectures (eg React) and many other factors. Types won't make bad code maintainable. So, types have their place but not everything in TS-land is shiny.

I like the header and experimented with current trends:

- Talk of AI is bullshit. Shut up and get the work done.

- Talk of Machine Learning is bullshit. Shut up and get the work done.

- Talk of VR is bullshit. Shut up and get the work done.

- Talk of Smart Contracts is bullshit. Shut up and get the work done.

- Talk of IoT is bullshit. Shut up and get the work done.

Not sure if I entirely agree with him but there's some truth.