I definitely remember Hotline! Got me into trouble in college...a friend and I opened up Hotline servers on our machines and threw a piece of software on there (probably a cracked version of Macromedia Flash or something like that...) and a README that said "please leave something if you take something". A few weeks later, we both got calls from the sys admin at our school asking us to come in for a little chat...we hadn't really been paying too much attention, and apparently people had put all kinds of software/games etc. on there and that we had been serving up from our machines (I believe the admin said "millions of dollars"...but he may have been trying to scare us straight...). We didn't end up getting into too much trouble for it (I believe we were banned from using the internet for a few weeks) and ultimately I got hired to work in the IT department, so it worked out for me at least...
Heh, in HS I convinced the Drafting Department (1988) that if we were ever going to draw anything in the "real world" (I was in 8th grade, but took HS level drafting) that we would only ever do it on a computer.
I pitched the school board and we were funded to set up a CAD dept - which of course I needed a server to share cad files etc...
I setup the system, and then my buddy and I setup a BBS on the server and were running a warez site frm the HS CAD Lab.
So just today I was wondering if there was a cli tool (or maybe a clever use of existing tools...) that could watch the output of one command for a certain string, parse bits of that out, and then execute another command with that parsed bit as input. For example, I have a command I run that spits out a log line with a url on it, I need to usually manually copy out that url and then paste it as an arg to my other command. There are other times when I simply want to wait for something to start up (you'll usually get a line like "Dev server started on port 8080") and then execute another command.
I know that I could obviously grep the output of the first command, and then use sed or awk to manipulate the line I want to get just the url, but I'm not sure about the best way to go about the rest. In addition, I usually want to see all the output of the first command (in this case, it's not done executing, it continues to run after printing out the url), so maybe there's a way to do that with tee? But I usually ALSO don't want to intermix 2 commands in the same shell, i.e. I don't want to just have a big series of pipes, Ideally I could run the 2 commands separately in their own terminals but the 2nd command that needs the url would effectively block until it received the url output from the first command. I have a feeling maybe you could do this with named pipes or something but that's pretty far out of my league...would love to hear if this is something other folks have done or have a need for.
$ mkfifo myfifo
$ while true; do sed -rune 's/^Dev server started on port (.*)/\1/p' myfifo | xargs -n1 -I{} echo "Execute other command here with argument {}"; done
In the other terminal, run your server and tee the output to the fifo you just created:
A named pipe sounds like a good way to fulfill your requirement of having the command runs on separate shells.. In the first terminal, shove the output of commend A into the named pipe. In the second terminal, have a loop that reads from the named pipe line by line and invokes command B with the appropriate arguments.
You can create a named pipe using "mkfifo", which creates a pipe "file" with the specified name. Then, you can tell your programs to read and write to the pipe the same way you'd tell them to read and write from a normal file. You can use "<" and ">" to redirect stdout/stderr, or you can pass the file name if it's a program that expects a file name.
1. Run one command with output to a file, possibly in the background. Since you want to watch the output, run “tail --follow=name filename.log”.
2. In a second terminal, run a second tail --follow on the same log file but pipe the output to a command sequence to find and extract the URL, and then pipe that into a shell while loop; something like “while read -r url; do do-thing-with "$url"; done”.
So, maybe? But these products already exist. Your company doesn't need to pay Microsoft to get that data, they can install stuff on your work machine and get all that info right now.
I've had similar really good experiences, but it's probably just luck. The last place I went to they used https://pos.toasttab.com/. It was quick, easy, everyone at the table was able to pay for their own food without having to worry about dividing up the bill, it was easy to order additional items without having to wait for the waiter to come around, etc. And, fwiw, it didn't seem to affect the social aspect of my dinner at all. Normally we all would have been sitting quietly looking at the menu, instead we all sat quietly and looked at our phones. After we ordered, everyone put their phones away and we had a good time.
> I doubt you are actually working together on a common goal though, if you do not see value in standups for example.
It sounds like you're assuming the only way to sync up with folks is a stand up, which is just ridiculous. I'd even make the argument that if you think you need a stand up so that team members actually communicate with each other then you're not working on an actual team, you're working with other people that are loosely grouped together. Any good team I've ever worked on, people just organically collaborate as needed. You don't have to wait for some arbitrary sync-up time to let each other know what's going on.
In general, I'm not necessarily against stand-ups, as long as they're quick and don't turn into status meetings. In my mind, a perfectly reasonable stand up could be "does everyone know what they're doing? Does anyone need help?" and if the answers to those are "yes" and "no" respectively, then we can be on our way. But more often these things turn into minor status report meetings, where everyone starts saying "this is what I did yesterday; this is what I'm doing today..." and often those details are not relevant for everyone on the team and could just as easily be communicated elsewhere in an async fashion.
I feel like a lot of things like stand-ups exist for the lowest common denominator teams. Bad teams don't organically communicate, people slack off if you don't micromanage them, etc., and so for those teams you NEED a stand-up. But then it gets forced on everyone and is a drag for high-performing teams, and good people end up leaving because they just don't want to deal with all the BS. So you end up with a self-fulfilling prophecy where what you're mostly left with is bad teams and so it feels like stand-up is necessary or is working. It's kind of maddening.
That was on HN earlier this year. Basically it's software that you run and set up to detect when certain peripherals connect/disconnect and have it switch the input on the monitor automatically. I've been using it and, while not always perfect, it actually works pretty well, especially considering the price.
If you don't always want the monitor to switch inputs (sometimes I just want to quickly switch my keyboard/mouse to my laptop to do something but don't want to switch monitor inputs) you can also just set up shortcuts or scripts (I created an Alfred workflow, for example) and use something like https://github.com/kfix/ddcctl to switch monitor inputs.
Yeah, exactly. There was something I was reading/watching the other day that was advising that you not trust information unless it comes from a credible/legitimate source. But isn't that the problem? I mean, a large percentage of the US thinks that Fox news is a credible source (including our President...). People think they're doing research by watching videos on YouTube.
I don't really know how you fix this either. It seems to me that it's not whether you're ABLE to think critically that's the problem, it's whether you WANT to. It feels like a large portion of our population just doesn't want to put in the effort.
Exactly. But also remember that watching YouTube videos can be good research. The medium isn't important, but you need to be careful that the content is coming from a reputable origin and cross-reference with independent sources. Typing the fact that you want to be true into the search box and watching the first 3 videos is not good research.
This is admittedly nit-picky, but you're not managing 60k DOM nodes if you're using a virtual list, that's the whole point of virtualization. You might have 60k items in your list but you're only ever rendering a tiny subset of those items based on what is visible (with some overlap).
It's not virtualized. It's not even a list. It's a very large SVG with lots of foreignObject bits in it. The app is a diagramming tool - imagine Visio but for lawyers to map out contracts and ownerships between hundreds of corporations.
Where I work, we have Architects but they often play a supporting/consulting role and the teams are expected to learn and implement most of the things listed in this article. They will push you to make good decisions, and will want to vet your designs, but they aren't dictating this stuff from on high (unless of course you're making really poor choices). It's been great because no matter who you are or what role you play on the team (I'm primarily a FE dev) you can learn as much of this stuff as you want. I have to imagine its the same at other companies, so anyway, what I'm saying is you can get a ton of experience in all of this kind of stuff without being an actual Architect at some places (we're a large company). The flip side of that coin here is that it's VERY difficult to get the actual title of Architect; it's a very limited role and it takes a lot more than just systems knowledge to get there (i.e. politics). A lot of the people I've worked with who are Senior level could probably easily transition into a systems architect position at other companies. I'm not sure if this is the best way to get there if that's what you're interested in though, just giving you some food for thought. I don't know how you identify companies where you can get this kind of experience, but if you're interviewing you should ask about "you build it you run it" or stuff like that to see how they manage their infrastructure, that might give you a hint.
