HNHacker News
TopNewBestAskShowJobs

mrozbarry

366 karma · joined May 22, 2018

submissionscomments
mrozbarry··on My Remote Mob Programming Experience
I don't know if this is just advertising, but I'm the main developer behind https://mobti.me/ , which is a distributed mob programming timer. I'm aware of mob.sh, and have been asked if there would be any integrations. It has always seemed like it already has a timer, so I kept saying no, and now I have more definitive proof.

Anyway, I have a few mobbing tips that I use daily (have been consistently mob programming for 2+ years every day, and my previous job was pair programming all day for 2 years, as well):

- No heroes in the mob. If the mob cannot function without a specific person, then you are not mobbing. The only exception may be when a mob is first brought together to work on a new problem where only a single person has domain knowledge, but that shouldn't be relied on beyond a sessions or two.

- Respect the timer, but be flexible to finish ideas. Strict timer adherence can sometimes kill the mood, but when someone takes over, it can also kill it. Always acknowledge if the timer is up, and if you need to finish something, ask the mob if it's okay. Don't continue if people disagree.

- Prefer high level intentions. Don't tell people "make this variable, call it foo, and use it fetch from this endpoint" if instead you can say "can you fetch this data and store it?" - people can always ask for clarification, but they should be free to figure out the problem on their own.

- Ask for corrections after your coder is done writing an idea. If someone has the right idea, but is writing the wrong code, let it play out for a moment. Maybe the code being writing is considering a problem you haven't, or at the very least, the person writing the code can explain it when it's done so the team can decide if it's good or not. Trying to throw in corrections as someone is typing is a lot of cognitive overload.

- Reflect often, and honestly. After you're done a session, see how it went. It's okay to call someone out for being too bossy, or highlight if someone isn't being heard, as long as it's done for the sake of being a better team. Maybe the timer is too long, maybe there are too many people, maybe not the right people, and all these sorts of things should be thought about as a team.

mrozbarry··on Against Pair Programming
Oh, I should have mentioned, I mob program every day at my current job, and pair programmed every day at my previous job, and both were very successful and enjoyable jobs.
mrozbarry··on Covid testing firm ‘selling swabs carrying customers’ DNA’ to third parties
I can't find a definitive start, but essentially as soon as samples were being tested, it was conspiracy theory time. Even if it's not for DNA, I can assure you the swabs have many conspiracy theories behind them.

(Credentials: my wife is really into conspiracy theories)

mrozbarry··on Against Pair Programming
Just to tag along (I was going to quote and write just about all the same things), but with two developers, the HUGE value-add is codebase knowledge.

If two people on a team regularly contribute to a repo, one person likes to work on feature A, and the other feature B, and all of a sudden, the feature B person leaves and never comes back, that will kill velocity. Even if feature A person has been doing code reviews, a code review is much different than being aware of the system and continuing to improve a feature. Now person A has to either read documentation (which is, for the sake of code writing, a 0 velocity), or take larger tours through the code to figure out why a feature is how it is, and what needs to be done.

So the big question for anyone is if they want to focus on velocity/lines per day, or consistently smooth development. You can get both of those things when everyone is doing their own tickets, but that will immediately stop as soon as there is a change in your team.

I don't think pairing is perfect, or mobbing for that matter, but it does give clients a more consistent/smooth experience if they are okay with paying more for quality than speed. It does take the right kind of people and the right kind of project, just like any problem and tool set.

mrozbarry··on Ask HN: Disillusioned with the direction of society and technology
A thought I had a few years ago was what sort of technology was in Star Trek (TNG, but any of the series is a reasonable point), and what technology we have now.

Star Trek had a very utopian sense about technology, were tech giants have a much more distopian sense about it. For instance, in both cases, we want an AI that can understand regular language, and give us accurate results for our requests. In Star Trek, every ship has this tech, and it's all used without any thought of privacy concerns or what it means for a computer to be always listening. In fact, as far as I can think, Star Trek never really had self-awareness about what the technology the people of that time used and it's implications (like privacy, but there are likely many more ethical concerns).

This led me to a bit of a split mind on technology. Using speech recognition as the example. Yes, it would be great if I could ask a computer something and it can answer me. No, it would not be great if that information was used to manipulate me or exploit my situation (like suggesting products to buy).

I do think all advancements are a two-edged sword. Is it orwellian? I definitely agree. My phone is always listening (even when there are claims it is not, or it's in standby mode), cameras are small enough to fit in a pocket and be used any time. Outside of living in a cave, you can choose what you participate in. You don't _need_ a smart phone - your emails can be answered when you sit at a computer, your calls can go to voicemail when you're not home. You don't _need_ to be on facebook - get your photos printed, save your videos to DVDs, share them with people when you invite them over.

A popular saying is vote with your wallet, but it can also be vote with your attention, too! Don't use social media if you think it sucks. Just log out, deactivate your account, and live your life. Don't share information on the internet you don't want to be used against you, and that even includes things like purchases on amazon, your address, or anything else.

It's only too late if you're not willing to do anything about it. Don't blame big tech if at the same time, you're logging in and feeding them your attention. It's not up to you how other people waste their time, either, but you can encourage different behaviour by having real-life interactions without technology in the way.

mrozbarry··on Node.js adds support for direct registry-less HTTPS imports
Yeah, a bit of hyberbole, but I think my point is it's been proven to be relatively simple, or at least simple in theory.

I think npm could improve security with two steps: 1) all packages must be user-or-organization/package-name, and 2) all packages need to be signed with a key. Have namespaced-by-default packages at least will give a path for developers to trust an author or source. Signed packages would give developers the means to trust a key. All systems that allow public packages to be published are going to have inherit security flaws, and the best security I think we can give is trust. It's easy to invalidate a key, and it's easy to flag a namespace as untrustworthy.

While there is no "dependence" on npm, most package managers ship node with npm, and the typical flow for a node app, according to most tutorials and community documentation, is to use npm. Even most of the tools a developer would use with node are npm-centric (documentation almost never recommends cloning the repository, just npm install). So I'd agree, decoupled in reality, but is perceived as reality among tutorials and the community.

mrozbarry··on Node.js adds support for direct registry-less HTTPS imports
My impression is this is really just to have some sort of comparable feature to deno. You may think this somehow is more of a vulnerability, but the reality is the npm registry is already fairly insecure, we've seen npm packages get hijacked regularly.

This also adds less dependence on npm, and maybe with all the packages that get hijacked there, this could be a reasonable move.

mrozbarry··on Ask HN: Are most of us developers lying about how much work we do?
Perhaps I worded that a little badly. They are responsible for making sure you are getting paid, or if you get fired.
mrozbarry··on Ask HN: Are most of us developers lying about how much work we do?
I think this 2-question test is very accurate.

To add to this, even if for a time, you can increase your productivity, sometimes that's not sustainable. There's nothing wrong with having ebbs and flows. On days when you have a larger workload of smaller tasks, you may find yourself to be incredibly productive, and days when you have smaller workloads, or larger tasks, and you may be less productive.

The thing is, if your boss is happy with your pace and work, then why be worried? It is literally your boss's job to notice if you aren't pulling your weight, and to ensure you are compensated fairly for your work.

The work-place hierarchy (hopefully, and usually) is set up so you don't have to govern whether you are working at the proper pace, that is the problem of your superiors, it's only up to you to accomplish the tasks you are given, or give advice about those tasks if they are wrong.

mrozbarry··on Ask HN: Is back end dev generally easier than front end?
I'm a bit of a jack of all trades developer (front/back end web, desktop/native/mobile, a little embedded), and if I were to point out the main issue here, it _sounds_ like the projects/jobs you've worked haven't either given you opportunities to be mentored in newer tech/work-flows, or haven't given you opportunities to learn on your own. These issues could be your own fault, too, I don't know. For reference, I've been a hobbyist developer since 2001, professional since 2010.

The thing about working in tech, is no matter what you work on, technology is always advancing. There will always be newer, better, and more accepted ways than what you're doing now.

For instance, in 2007, it was perfectly reasonable to use bootstrap and jquery, and boom, you have your responsive layouts, animations, etc. You can still do that today, but I think that would be considered legacy by most developers. Now you need to have a decent grasp of raw css (v3, which has a lot more layout-related directives), and vanilla javascript.

Having knowledge on core fundamentals has a lot more value than knowledge in libraries, and that's been the case well before 2007. If you invested a lot of time in bootstrap+jquery (or whatever tech you/your company chose in 2007), those skills aren't completely wasted, but the investment in how javascript, as a language, works, or modern layouts in css are much higher value.

If you've lost your confidence/will to apply to newer jobs, that's a deeper issue than just switching from front-end to back-end. Working in software is literally having to learn and re-learn the same things over and over as technology improves, or the ways languages do tasks change. The only thing back-end may give you is slightly more stability, but even that isn't guaranteed.

So before you go all-in on switching from a front-end only to back-end only, maybe there are some questions we, as a community, can help you resolve.

- Do you have anyone mentoring/guiding you through all the changes that have happened in web tech since 2007?

- Does your job give you any opportunities to grow?

- What is the single biggest pain-point daily for you, and is that something we can help you solve?

- Are you disinterested in front-end technology, or just overwhelmed?

- What is so appealing about back-end over front-end?

I hope I haven't come across as uncaring, I truly hope we can sort out the issue you're having <3

mrozbarry··on Show HN: SingUI – compose modern front end with pure vanilla JavaScript
No problem, the JS ecosystem is so full that there is a lot of naming overlap.

Nothing should be stopping you from just making a test file, you don't _have_ to use a framework. NodeJS even comes bundled with https://nodejs.org/api/assert.html .

mrozbarry··on Modern JavaScript has made the web worse (2020)
This general topic comes up often, and the top reasons usually end up being:

- JS development has a low barrier to entry, so there is a wide/diverse range of developer skills and knowledge

- Most (webpack) tutorials don't cover build optimization, like tree-shaking, especially entry level, which is normally what people find to "just get the job done."

- There are too many options for frameworks for people to make _good_ decisions, so they often fallback to _popular_ decisions

This isn't even a recent problem. I have a few clients that wanted to use old-school template packages, like metronic, and that is a massive bloated build, and yet it's basically jquery+bootstrap with a handful of libraries.

The biggest thing is, as professional web developers, we have a responsibility to the end user to make a web page load fast and be usable quickly, and I think we often over-look that. I don't care if your framework is a no-build thing, or uses webpack/rollup/etc., the real thing is if a user doesn't have to download 50MB of javascript for a single page, especially if the end result of that page is considerably less than 50MB worth of text, styles, and images.

The flip side is, most clients just want their project done quickly so they can make money. There's nothing wrong with that, but it can't be at the expense of their users, and developers should be able to give good consultation and advice to their clients about the trade-offs of libraries/frameworks/build tools/etc. and the impact they will have on the end-users.

Personally, I like building without extra build tools. `script type="module"` is great, and smaller frameworks (my go-to is hyperapp, but there are several others) are often not awful to grab a local es6 copy and toss it in your public web directory, import it, and go to town.

mrozbarry··on Show HN: SingUI – compose modern front end with pure vanilla JavaScript
Hopefully I didn't come off aggressively, I was just trying to give you some feedback.

In terms of hyperapp, that is as much compiling as `document.createElement("a")`, which is what your library does, too.

I'm not saying write redundant tests. Tests are more than just one person's psychological comfort. Another great example is if you are accepting PRs into a larger codebase, having tests means you know other people aren't breaking previously working parts of your app. Tests can also work as documentation, since a test describes how pieces of your app should work.

I'm confused why you think any of my suggestions imply that you should make your library heavy/larger/unmanageable.

mrozbarry··on Show HN: SingUI – compose modern front end with pure vanilla JavaScript
There are frameworks that already exist that don't require compiling, like hyperapp (but others, too). Even React can be written without compiling - you don't _have_ to use JSX or advanced babel.

So I read through the example, and I do get it, but I'm not a fan, but I also think you put a lot of thought into this in general.

If you want adoption, I think you need to focus on at least two things:

- Testing (part 1). Your library doesn't have tests, and was only pushed about 9 hours ago from the time of this comment. Developers don't have any way to trust that the library works the way they think it should.

- Testing (part 2). There is no obvious way to test code written with your library/framework. Developers won't be able to verify if their code is doing what they expect. I suspect you could have build return faked methods, but then how do you tell the build function that it should be in test mode?

mrozbarry··on How to Catch a Cheating Candidate in an Interview
Isn't that more-so up to your employer to decide if it's an extra advantage? I'm not saying you're wrong, but I think intentionally obscuring who you are isn't solving a problem.
mrozbarry··on Pfizer-BioNTech Booster Shot Restores Full Covid Protection in Large Trial
Oh, I know why I'm being downvoted, this isn't my first rodeo, but I appreciate the support :)

The biggest thing, as far as I understand, is people want to go back to normal, and by definition, normal was a world before covid-19, so normal must mean that covid-19 as an active virus in the world should not exist.

The problem is the covid-19 vaccine does not remove covid-19 from being transmissible in the world, as admitted by the CDC and every vaccine manufacturer [1] [2] [3]. We don't even know if these vaccines, in spite of being developed by very intelligent teams, will have any long-term serious side-effects, there are no long term tests. Guess what, the human race is the current test, and if the test goes bad, if we do have a >50% vaccination rate, in the worst case scenario, that will be very very bad for everyone.

So what problem are we solving with the vaccines? If we are solving hospitalizations, I have read many conflicting articles about the actual state of hospitals, so it is hard to know if we are actually solving that problem. If we are solving the problem of going back to normal, then the vaccines are not a good long term route.

Every solution that does not contribute to solving the problem is just busy-work at best, and creating other problems at the worst.

All that said, I'm not saying people should or shouldn't isolate, social distance, vaccinate, but I am saying that the current solutions our world leaders are pushing do not bring us back to "normal," as-in pre-covid.

[1] https://www.cdc.gov/coronavirus/2019-ncov/science/science-br...

[2] https://www.fda.gov/emergency-preparedness-and-response/coro...

[3] https://www.bbc.com/future/article/20210203-why-vaccinated-p...

mrozbarry··on Pfizer-BioNTech Booster Shot Restores Full Covid Protection in Large Trial
If the purpose of the vaccine is to stop covid-19, then hospitalization doesn't matter, only infection rate does.
mrozbarry··on Does anybody else feel overwhelmed by the JavaScript ecosystem?
If your job doesn't allow you time to learn tools that can be used in your job, that's a definite problem.

That said, like others have already said, the task of keeping up with the JS ecosystem is futile. Yeah, there might be some cool new tools, like esbuid, Vite, and Nuxt, but that doesn't mean you have to always jump on those bandwagons.

A real non-problem with ecma/javascript language is that it is almost too easy to start writing that there is always someone putting some new tool out for it. This means there is always competition with similar tools, people trying to shout about how their shiny tool X fixes problem Y better than other tool Z. It's easy to get caught up in the noise.

Here's my hot take: don't try and keep up on your own effort. Use tools that you understand and are time-tested. Sometimes, a co-worker might be using some new shiny tool, and when they do, ask them to show it to you. It doesn't mean you need to switch to it, but it gives you an opportunity to learn the top level overview/benefits without having to keep track of everything.

A big thing I try to do is avoid following JS libraries/personalities on places like twitter. Every day, they are touting their own tools and tooting their own horns - there is nothing wrong with that, but it's just noisy.

And let me say this, no one will get fired if the tools you use do the job they need to do in a easy and consistent way.

mrozbarry··on A notable JavaScript developer shamelessly copied one of my most downloaded nod
While I think you have a valid point about the javascript community reinventing the wheel often, the problem in this thread is simply that some people are inconsiderate, rude, and hostile, and that is in every software community and ecosystem in some way or another.
mrozbarry··on Ask HN: What are your opinions on modern BASIC dialects?
I was pretty heavy into the QBasic community in the 2000s, and move into the FreeBASIC community once it was stable.

I'd highly recommend FreeBASIC, especially if you enjoy C-style programming. Lots of good libraries and good C library support (give or take writing the headers by hand or translating)

I tried QB64, but I'd only recommend that if you want nostalgia. By default, it gives that classic QBasic IDE interface, and feels very self contained.

mrozbarry··on Ask HN: Where can you apply for a programming job when you are a Class A asshole
Yeah, that's a solid plan. At my work, we've brought people in for the day, or for a smaller work session so they get a feel for how we work.
mrozbarry··on Ask HN: Where can you apply for a programming job when you are a Class A asshole
Anytime someone has given me a whiteboard and I ask questions, I usually get frustrating answers, like "I guess you could try that" and not actual concrete answers. I live near Waterloo, ON, which has a tech hub and big university that leans towards tech, so maybe it's a univeristy culture thing.

Anyway, that's why my policy is to just say no to whiteboarding during interviews. I'd rather sit at a computer with another human who wants to see me succeed over stand at a whiteboard with people that want to dissect how I think.

mrozbarry··on Ask HN: Where can you apply for a programming job when you are a Class A asshole
https://vehikl.com
mrozbarry··on Ask HN: Where can you apply for a programming job when you are a Class A asshole
I have a few rules that have helped me land good jobs:

1. If they want me to napkin code, I call it quits immediately, even if I know the code they want me to write be heart. Watching me write code on a whiteboard or piece of paper has no demonstratable connection to how I work day-in and day-out. Places like this would be both a waste of their time to hire me, and a waste of my time to interview for. I always ask up front about this if I'm unsure how the interview goes.

2. I set myself up to control the interview. I bring my laptop, ready with a bunch of work I've done that I can show off. When I sit down, I ask "Hey, I brought a bunch of interesting projects that I can show off, is that alright?" If they aren't interested in seeing that, they are clearly not interested in the sort of work I do, and not interested to see how I can fit into their team.

3. Ask what their typical day is like. This includes asking what the most painful part of their day is.

4. I want to know specifically who I need to talk to and who would need to talk to me to finish my work. The higher the number of people I need to talk to, and the lower the number of people who talk to me is a real bad sign. Reporting to and trying to appease multiple bosses with completely different goals and timelines is bad. Also, if there is no one under me, then job clearly doesn't respect or desire mentorship.

Sometimes I skip some of these steps, and obviously your mileage will vary, but always ask the questions that give you answers to how you like to work. For instance, if you want a cubical and want to put on headphones, ask about the office layout, and what expectations the company has for your communication abilities.

mrozbarry··on Anti-Vaxxers Got Fooled by Fake ‘Snitch on Your Unvaccinated Friends’ Site
So, a governor is essentially letting people submit private information about other people, and are potentially storing it somewhere. On top of that, the main landing page and submit forms have no indication that it's satire at all. Yes, I see the about page does, but most alarmists aren't going to dig much further than the landing and submit pages.

So what was the end goal of this site? To add people to a mailing list they don't want to be on? To make some people on social media spread a lie? Fear mongering?

mrozbarry··on Launch HN: BlackOakTV (YC S21) – Netflix for black people
I guess something to ask is if black content creators are among the most creative, and black consumers are among the most energetic and prolific users, are you only attributing their lack of success(?) on youtube because of algorithms?

If it's just a question of likes/subscriptions/shares, then the statement that they are the most energetic and prolific users seems incorrect.

If it's something else, can we identify what the problem is with some other algorithm that is not likes/subscribes/shares?

I hope your plans for blackoak is successful, but I'm not sure it solves the problem you're describing. The biggest issue is places like netflix and youtube have a huge market share, and if you are just hosting/moving content off those platforms, you risk your content creators having less recognition unless you can gain enough traction. On top of that, if you're competing in the paid streaming market, like netflix/hulu/prime/disney/etc., now you're telling your market to pay for another service on top of the things they already subscribe to.

So again, best of luck, hopefully you have plans to solve or mitigate what I just described.

mrozbarry··on Had Covid? You’ll probably make antibodies for a lifetime
The main issue is that there is a very ill-defined wall between vaccines from science and a political agenda.

The average human (except maybe the elderly?) does not have the same problems with flu season and vaccination in the same way we view covid. Granted, covid is a big problem, but the mortality rate is about 10% [0]. The main difference here is that the flu season is mostly dictated by science, there are no public restrictions and people go about their lives mostly without consequence. Covid is a different beast for a bunch of reasons, and one major one is politics.

I have never up until this point in my life saw the amount of political pressure that everyone needs to be vaccinated. Probably going more off opinion that fact at this point, but I can't foresee any place in the world going back to normal once n% of people get vaccinated. At least the mayo clinic doesn't seem certain on what the long term effects of the current vaccines will be [1], specifically around "A COVID-19 vaccine might...Prevent you from getting COVID-19 or from becoming seriously ill or dying due to COVID-19." The CDC website seems to have more confident information, but I'm not convinced that we actually have the long-term data yet to back that up, but I'm open to being corrected with any studies that last more than 2 months, and use saline for control groups (and not another vaccine, which seems to be the popular method, which I'm also interested in opinions on). So _if_ the vaccines don't provided long term protection from being sick AND spreading the disease, don't expect vaccinated percentages to change the state of the current lockdowns.

I've been told I'm a bad citizen for just waiting for data that proves that shooting this vaccine in my body will actually support a good long term solution.

[0] https://coronavirus.jhu.edu/data/mortality [1] https://www.mayoclinic.org/diseases-conditions/coronavirus/i...

mrozbarry··on The mortifying ordeal of pairing all day
The whole team definitely needs to buy into the full-day pairing/mobbing. I'm definitely more on the introverted side of the scale, and I can handle things as a daily thing, but I do need a break once an hour or so, and that's the sort of thing your pair-team needs to figure out.

And another thing that's super important to talk about is the metric you mention:

> can believe that some people can be productive with the distraction of someone else constantly there, but I'm nowhere near as productive as I am working on my own.

Productivity is an interesting thing in software. What is productivity? Is it writing code fast? Is that the most important thing you can do for your company/client?

Pairing and mobbing aren't necessarily performance-oriented, but more on transfer of knowledge. If you work in a company that just wants pure churn of new code without a large amount of knowledge transfer between members, then pairing is just a gimmick and not useful to that company. This is really a case of "use the right tool for the job" - pairing and mobbing won't always make sense if it conflicts with the goals and values of the company.

mrozbarry··on The mortifying ordeal of pairing all day
It's not that I don't trust the burnout, but I want to know what aspect is causing burnout. Is it talking all day? Is there stress because someone is watching you work? Are you not taking enough breaks? These things aren't all specific to pairing, which means that pairing wouldn't always be the issue.

Sure, some people are just not the type of people that are good at pairing, and that's valid, but it's important to identify the problem. That's where trust and support comes in. If you can't talk about why you are feeling burnt out with your team, then there is a deeper issue that your team needs to figure out.

mrozbarry··on The mortifying ordeal of pairing all day
I've worked on teams historically that did pairing (even pairing all day), and mobbing all day, and I don't get the hate.

If the main issue is burnout, then what's up? Even working solo you can burn out, so I don't think that's a valid argument unless someone can convince me that specifically pairing is causing the burn out.

The biggest thing is you need a team that can trust and support each other.

← PreviousPage 4 of 6Next →