westoque

Ruby. To quote the creator Yukihiro Matsumoto:

> I believe that the purpose of life is, at least in part, to be happy. Based on this belief, Ruby is designed to make programming not only easy but also fun.

Writing Ruby code feels natural, from creating classes, all the way to its basic types. Knowing everything is an Object makes it easy to work with.

The tooling is amazing as well, from managing gems through bundler, and running simple scripts such as rake tasks.

Now, if it's performance can be further improved, say like Go-like speeds then it would be further used.

Related. I also have a similar experience when I worked as a contractor for [big ecommerce] for simply building a JavaScript loader that loaded ads on their ecommerce platform using JSONP. That ad loader got millions of views and pretty much seen everytime you shopped online at the site and surprisingly that's what gets most people excited when I tell them about my experience thinking it's such a crowning achievement as well.

as an aside, i found this bit from the link for https://microsoft.github.io/react-native-windows:

> Some build-time tools will send telemetry to Microsoft by default.

can we please stop collecting telemetry by default and ask instead? i think it's a relatively easy feature to do and not much friction for users.

I am mostly a one man shop myself but I would encourage everybody to self host their authentication. With so many open source libraries, there’s no good reason why you should use an external provider. In most cases, if the app is relatively successful you will very likely add functionality to your app, and this means you need control of your data and everything else that comes with it.

In the bigger scheme of things, I envision a world where adding auth to your app (or any functionality) is as simple as adding a docker service.

This makes a good case for decentralization no? Imagine all those items in the blockchain, you can leave for years knowing you can retrieve them anytime. The only con at the point is if you lose your keys.

Reminds me of some friends who had Bitcoin and “forgot” about it and only to come back with massive profits.

Not exactly a book but just read the "The Almanack Of Naval Ravikant: A Guide to Wealth and Happiness" and it's full of great quotes and entries by Naval who is an entrepreneur now turned philosopher. Gives sound logic on how to find wealth, contentment and purpose in todays busy world.

It's also free in ebook form. https://www.navalmanack.com

> It is extremely difficult to change a monolith’s technology or language or framework because all components are tightly coupled and dependent on each other. As a result, even relatively small changes can require lengthy development and deployment times.

I disagree with this so much. I have personally worked with Rails application monoliths and Node.js microservices and I can tell you that making changes on the monolith is muliple times easier mostly depending on the code structure. I would take a properly structured monolith any day. This not only includes code/features but also deployments. Adding more services introduces more complexity in the deployment architecture as well.

A good example of this is just by looking at the GitLab codebase https://gitlab.com/gitlab-org/gitlab, it's a monolith but has good abstractions/structure vs say the Google Microservices Demo app https://github.com/GoogleCloudPlatform/microservices-demo which is not tightly coupled but introduces more complexity from implementation to deployment.

Working on Pastly https://www.pastly.app

Fastest way to mockup screenshots and share - Copy. Paste. Edit. Share.

Still in beta but using Elixir/Phoenix/React. If anyone interested in partnering or working together please reach out.

admin@pastly.app

Personally. I'm targeting the browser. Web applications have evolved so much that we now need access to more hardware to further improve our web apps. Imagine having direct access to GPU and other things, we can then be running full apps in the browser, think Photoshop/Final Cut Pro, even games that required full 3D rendering. To an extent, this also requires us to remove the shackles from only having JavaScript as the only allowed scripting language in the browser.

> We have learned that some data was exposed to the internet due to an error in a Twitch server configuration change that was subsequently accessed by a malicious third party.

How could 1 "server" change give such a high clearance to access all that was in the leak? This includes the data for the payouts including the source code for multiple projects. I still don't understand how this could happen for a company this big.

A GitHub organization for a project I worked on for example is segmented into teams so not 1 team can access another teams account, something this simple could have mitigated the number of repos exposed unless maybe the root user is pwned. Also, given that they use AWS, it comes with security tools including one to scan your whole network for weaknesses/vulnerabilities and also gives recommendations on what to do to fix besides other things.

This is really a lesson for other companies to practice the "Principle of Least Privilege" as a default mindset.

Isn't it ironic to use a REST API to send BTC vs say using what any cryptocurrency is intended for? To use their native APIs to transfer value. The aim of decentralization is to eliminate that third party but this puts it back. We've come full circle.

> ² According to the raw unweighted data, we surveyed 1,296 teens in the US and 1,309 teens in the UK and asked them if they experienced a range of feelings or experiences in the past month ... then asked if the feeling started on Instagram

I'm not a statistician but isn't 1,296 (US teens) + 1,309 (UK teens) such a small sample size to make these conclusions with?

A quick Google shows:

> In 2019, approximately 21.05 million young people between the ages from 15 to 19 lived in the United States.

Source: https://www.statista.com/statistics/221852/number-of-youth-a....

EDIT: Added link to US teen numbers.

EDIT 2: Thanks for the replies and further reading it's more about confidence and margin of error.

It took me awhile to find screenshots of how this looks like, so for others curious: https://wiki.mobian-project.org/doku.php?id=intro

This website looks like it got put together by a bunch of hackers, which is fine, but to attract even more contributors and other enthusiasts it might be good to at least put an intro and screenshots on the main page.

Interesting to see so much development in crypto but within my tech and personal circles, no one still really uses it. It's still hard to use as it is to send payments vs traditional means with PayPal/Venmo. I also had friends that got into the NFT craze but had a hard time in just setting up a wallet and even more to setup and use MetaMask.

I want crypto to succeed but I'm not seeing the use within the public. Really all I see is the FOMO of getting rich in crypto investments.

> Why does this matter? Why do you want this? How do you correlate what you're stating you want here with actual job performance?

It matters to me because we want to be able to show that we can think through solutions. If we're building a feature that has something to do with streaming video, it would be a plus if you've shown that you have experience building streaming services or at least some knowledge along the topic. This should correlate with job performance because of the experience and working on this topic is already known. Now, there would be a case where we have 0 experience with this problem space but again it comes down to thinking through solutions and thinking about race conditions, side-effects etc and being able to identify these.

The tech interview process is different for every company but it's definitely not broken.

As a CTO, one of the things I look for is experience. You can look up all the "basic shit" you want but if we're talking about a specific problem, I want you to be able to give/walk me through a solution even if we don't finish the problem. If I'm interviewing a senior engineer, I want you to be able to show your seniority one way or another, if we talk about architecting something, I want you to be able to talk about why we want to solve it this way, pros-cons etc. Experience also shows me that it wouldn't take you a long time to solve the problem, and in our industry, at least my experience in startups, speed is key.

In our company, our interview process goes like:

1. Paper screening the candidate. Looking at resume to see if they have skills for the job on paper. If so go to Personality Screening.

2. Personality Screening is done by talking to them and seeing if there's a cultural fit and also throw in some programming questions or feature discussions to see how they think.

3. Technical Screening by way of pair programming on a problem set that is based on the position that should show a mix of skills, tracing bugs or implementing features. If Frontend, mostly JavaScript and a Frontend Framework like React if needed.

As far as your questions go, we put weight on hobby projects but just so that we can see their code writing and some logic up front. As an example, I have seen one candidate with a recent Ruby on Rails project that had all their spaces and newlines everywhere, and I'm not talking about spaces or tabs here, think one chunk of code has 2 spaces, next had 3, another had 5, just everywhere that made the code super hard to read together with the messy logic/abstractions, from this, I assumed that they are still junior. On the contrary, I've seen a candidate that has really good code on a similar Ruby on Rails hobby project that reflected well on their work.

No worries, valid point. I have ESL (English as Second Language) but noted.

Disclaimer, I'm a CTO.

Here's how I evaluate this if I was evaluating you:

1. I already have a salary budget already allocated for this role based on industry average for position and location (but location _could_ be irrelevant depending on skill mostly).

2. I look at your skillset and put you at the bucket for the position where you are at: low-med-high

3. I make my offer based on my evaluation.

4. If you are "worth it", meaning in the high bucket, then I would go out of my way to give you a good offer, up to max of my budget or to match how much you are asking. Else, I would say the offer is where it stands and either you take it or don't.

But to answer your question, it doesn't hurt to push back as long as you are confident in your skills and know your value is worth more. That one you have to make up for yourself by evaluating yourself with peers and other factors.

Oh. And if you do push back, make sure to give a good reason why it is so. For example, if I happened to put you in the low bucket, I might have evaluated you wrong or the tests did not show much of your skill, then make sure to outline why you deserve that salary increase with good reason. As a quick example, if the industry average in where you are is $50,000 and you are offered $30,000 which is the starting for a junior, you can say that you've been developing for awhile with at least 5 years experience and that $50,000 would be a fair salary etc etc.

It's not really about the user spying though, it's about the decision of making the user default of "yes, please track my usage so you can make your product better". I would rather have you ask the question first even though I mostly say yes, but transparency is key here.

This is an oversimplification and Docker is easy from a basic usage standpoint like most tutorials are. The hard part is when you start configuring and configuring to your own requirements. What baseimage should you use? How about logging? How about PID 1 problem? Do I need an init system? How about SSH? Remote Docker containers cannot be accessed remotely for ex AWS Fargate. How about restarting servers? I need to do it gracefully. How about migrations? One-off scripts?

Personally, I love using Docker but it’s those small things that make it hard and all the complexity around setting them up.

> We can befriend you for years, and then bite off your arm just as you’re offering us a treat. We can’t help it. It’s the nature of the job.

Something about this line irks me. I have a love-hate relationship with journalism because of this. I like that we are able to share stories through good communication and writing but on the other hand, being honest could (as the author said) "bite" you back. I just wish that we were honest about the interaction from the get go and not waiting for that a-ha moment to catch the person off-guard so they can support their own initiative, bias or story.

I hope we again see the value of using systems like Wordpress for it’s simplicity in getting a blog/website setup and easily modify content.

Lately most of the modern marketing websites I see is built using gatsby and next.js. Having been talking to different content/marketing teams, they hate it so much because of the complexity it brings. Editing content? Sign in to this headless CRM app, want a form? Go sign in to another app. It might be a fun project for devs but the actual users if these systems will almost always have a hard time using it.

thanks for correcting my mistakes :)

yes! my path to "expert" was more in the lines of questioning my commonly used editing functions:

1. how to delete text inside a double quote and go to insert mode? - c+i+"

2. how to move to the end of line? - $

3. how to delete everything before "x" character and go insert mode" - c+t+x

...

EDIT: updated mistakes.

I agree with quantifying managers' performance is a bit harder than software engineers. Take it for what its worth but what I learned from Intels Andrew Groves book "High Output Management" book is that the output of a manager is the output of his team/org and team/org under their influence.

> Finally, CEOs are terrible examples. More than any other title, CEO is an echelon which once reached, by whatever means, seems to ensure that the title holder can almost do no wrong.

I disagree here. I think the CEO is a very good example since if they do something wrong, it would be very visible and that's why even high profile CEOs get fired. See Uber or WeWork or even now, Intel for example.

> What does bother me a bit is seeing managers who frankly use less of their brains getting paid as much or more.

The statement "use less of their brains" does not necessarily do managers justice. Managers are good at (guess what) managing people, and that takes relationship skills that some people might not have or not good at. Having being both a software engineer and a manager, I would say it takes some special skill to do either work, who gets paid more is up for debate but not necessarily that an engineer should be paid more because they use their "brains" more.

Another example is a CEO who is non-technical. What skills do they have that make them have higher salaries or even bonuses? Guess what, they can make deals happen. They can secure a funding round, they can close an enterprise deal and it takes some special skills to do that as well.

using macports wouldn't make it such that "more things will work". it's really about the applications now needing to be compiled in the ARM architecture.

here are some examples:

aom: https://github.com/Homebrew/homebrew-core/pull/57976

boost: https://github.com/Homebrew/homebrew-core/pull/59257

...

if you notice the code changes for the items above, they make changes to detect if the compile target is ARM and make the necessary changes so it would compile.

more importantly. we need physical video kill switches as well! i have dealt with so many apps just opening the camera out of nowhere and it’s also mostly unexpected.

> >Are you willing to pay 50-100 euros/dollars per year to keep MDN afloat?

Yes as well. I consider myself pretty conservative with my spending but with regards to free things that benefit me, I am thankful, so I donate. I believe people should do more.