Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "visibility"
-
One of my favorite aspects of devRant has always been getting to learn more about the awesome people who use it. Beyond just the awesome stories posted by many here, one of my favorite ways to learn about and feel connected to the people here has always been desk/setup reveals. I personally love seeing different kinds of setups from all over the world, knowing that’s what the people here use to do their work and compute in general.
As an experiment, we want to try a few different things to highlight desk/setup/remote coding location posts. First, we’ve created the first devRant Instagram account, which is completely focused on developer desks/setups/workstations/remote coding. Please check it out here and follow: https://www.instagram.com/devdesks/
I want to use the account to bring more attention to the wide assortment of setups the awesome members of the devRant community post from all over the world. We’ll promote cool desk/setup/remote work images that are posted on devRant to the Instagram account for more exposure/additional audience.
Beyond that, I also want to try to come up with a way to better organize all of the desk/setup posts on devRant and encourage more of them. One kind we don’t see that often that I personally really enjoy is people coding with their laptops in locations that show the culture of their country or something special about the region they are from. Personally, I’m going to try to post some of those for where I live and work.
So how can you help with this effort? It’s easy! We encourage people to post their setups/working remotely pics and we will start featuring them on the Instagram account and hopefully elsewhere in the devRant app for some increased visibility/searchabilty over what we have now (since pics are kind of hard to search).
Also, we plan to make the weekly rant this week “post your setup,” so maybe wait until then to post, and you can work now on getting that awesome shot :) I know a lot of people here love photography like I do, so I think that part is fun too.
Please let me know if you have any ideas or questions about this, and I’m looking forward to seeing the desks/setups of many more devRanters in the next few days!
P.S. not a requirement, but one thing I think makes these photos better looking through a lot of them is when there is code visible in some way.44 -
My friend is a css guy and he told me this
.illuminati {
position: absolute;
visibility: hidden;
}11 -
A friend of mine: Look at this nice app I made 😎
*shows me a normal looking app with tabs and different views"
Me: Hmmm… looks good.
Friend: Do you know how I made the navigation between views? 😏
Me: I'm afraid to ask…
Friend: Since I didn't know how to use the piece of code I found on internet, I made multiple views one above another with visibility set to false, and during the navigation I just change the visibility. 😁
Me: WTF? Man… this isn't something you should be proud of… it shouldn't be done.
Friend: Do you also want to know how I backup the code?
Me: No…
Friend: I send it to myself via email.
Me: FUCK!
Friend: I also never use while loops, I prefer to use for instead with a break inside. 😊
*blocked*17 -
6pm - arrive home from work, log into my computer and start working on side projects.
4am - Finally go to sleep after staying up all night setting up arch in a vm.
7am - Start drive to work in the snow and ice.
7:20am - car runs out of wiper fluid.
7:30am - round corner so that I’m driving towards the sun, windshield is covered in mud and I have 2% visibility.
7:35am - take off ramp towards gas station so I can buy fluid and wash window.
7:36am - Car mysteriously parked in center of off ramp, nearly smash it but have a narrow miss.
7:40am - can’t find the freaking pully in new car to pop hood
7:41am - found it.
7:50am - drove the back way to work because it cuts out traffic, but includes many steep hills that I forgot existed, come to a skid at bottom of one and am pushed out into the main road, luckily nobody is coming and I’m able to continue on my merry way.
8:01am - sit down in desk, lead staff person comes over evoking Lumbergh from Office Space and lets me know I need to be on time to work and that the snow doesn’t give me an excuse. I agree and smile and suck up and he leaves.
8:02am - pull out phone to write down notes about personal project that I thought of on drive here, phone dies. I forgot to plug it in last night.
8:04am - found power bank charger thing in desk but it uses a micro-b type usb and I only have usb type c on me.
8:10am - borrow usb from old headset in office surplus.
8:11am - writing notes. Have sudden realization that I didn’t shut down my vm and that when my computer went to sleep and subsequently locked it probably halted virtualbox and everything would be lost for the second time.
8:12am - got on devRant.4 -
Some dumb puns to cheer you up after reading/ranting about "part of your workflow you dislike"
#tower-of-pisa {
font-style: italic;
}
#titanic {
float: none;
}
.yomama {
width: 99999999px;
}
.ikea {
display: table;
}
#bigbang::before {
content: " "
}
.illuminati {
position: absolute;
visibility: hidden;
}
I'd rate these horrible puns a C++20 -
"Please make the splash screen longer, 3-5 seconds at least"
So you are the "mobile UX expert"? Do you realize people want to achieve things without wasting time and patience? In 5 seconds I may get distracted with a notification or anything else IRL and I I'll even forget I ever opened your app. Puf, you lost a potentially paying user.
All this just to give some fu***** visibility to some small logos of your sponsors. What about an about page so everybody is happy?4 -
Senior Manager: I have to use your app today, how do I do that?
Dev: Well first you log in, and then you clic—
Senior Manager: That’s way too low level, I only deal with things on high level! Explain it to me from a high level.
Dev: Use the app to orchestrate the visibility of action items to stakeholders and pivot the leverage towards buy-in.
Senior Manager: Hmmmm….
Dev: Agile.
Senior Manager: Aha! I understand how to use the app perfectly now!
Senior Manager’s Account: Last Login - Never.4 -
"Ad targeters are pulling data from your browser’s password manager"
---
Well, fuck.
"It won't be easy to fix, but it's worth doing"
Just check for visibility or like other password managers handle it iirc: assign a unique identifier based on form content and fill that identifier only.
---
"Nearly every web browser now comes with a password manager tool, a lightweight version of the same service offered by plugins like LastPass and 1Password. But according to new research from Princeton's Center for Information Technology Policy, those same managers are being exploited as a way to track users from site to site.
The researchers examined two different scripts — AdThink and OnAudience — both of are designed to get identifiable information out of browser-based password managers. The scripts work by injecting invisible login forms in the background of the webpage and scooping up whatever the browsers autofill into the available slots. That information can then be used as a persistent ID to track users from page to page, a potentially valuable tool in targeting advertising."
Source: https://theverge.com/2017/12/...14 -
"I want visibility in the sprint", "Information for everyone! When you do even a small refactoring, you should add a card to the sprint, clear?"
Those were the words of the product manager.
That sounds reasonable but when there is a bug to investigate, he just pops to the chat channel throw a request with a bit of information and asks to check/fix that.
So to keep my sanity, I asked him to create a ticket with relevant information and additional observations so we can have visibility as he was advocating for it ;)
It felt just good to see him going silent :D3 -
Text a random number, 'I hid the body. What's next?'. When cops come knocking on your front door, show them this,
body {
visibility: hidden;
}2 -
Ever fuckinn "townhall meeting" at previous workplace. It was such an utter waste of time that even after leaving that place I still rage when thinking about it.
Every 4-6 months they would setup this useless crap of a meeting that drags on for over 1-1.5 hours of execs talking themselves up and trying to convince how great they are. And since they were cheapskates they would send out an email asking everyone to not join from their desks but congregate in the conference rooms to save on the dial-in. The conference rooms didn't have adequate chairs, vantilation or good enough aircon to handle twice/thrice the capacity of people standing in the room.
The marketing exec would go on and on about how great the media visibility is, how many views/likes they had on a linkedin post last month. The sales exec would blabber on about how their team is great and that the customers themselves are lining up and there is no competitor. Straight after the CFO would lecture on how the year is still difficult financially (in disguise justifying the peanuts of pay). The last exec, no matter who that is would specifically raise a point that the previous speakers didn't mention his/her team while thanking others.
This is also not a small company, the total headcount was just over 900 and roughly 500-700 people would be attending these townhalls. Imagine the amount of man hours wasted on that shitshow.6 -
I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.
My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.
For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.
Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)
Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”
Dev X: “I don’t know how to access Jenkins.”
And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.
But the next day, I lost my shit.
I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.
For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.
Two stood out to me. I read them slowly.
“I think you should name this unit test better” (That unit test existed before my PR)
“This function was deleted and moved to this other file, just so people know”
A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.3 -
We are required to use corporate SSO for any authenticated internal websites, and one of the features they require you to implement is a "logout" button.
They provide a whole slew of specifications, including size and placement/visibility, etc. They provide an SSO logout URL you must redirect to after you take care of your own application logout tasks.
Makes sense... except the logout URL they provide to serve the actual SSO logout function broke over 3 months ago, and remains non-functional to this day.
Apparently I'm the first person (and perhaps one of the only people) who reported it, and was told "just not to worry about it".
So, we have a standing feature request to provide a button... that doesn't actually work.
Corporate Security - Making your corporation _appear_ more secure every day...2 -
PM: I don't like the number of meetings we have
Me: Oh I agree. We have too..
PM: We don't have enough of them.
Me: (oh... I was going to say that we need to cut back... But ok)
PM: I need better visibility into what everyone is doing.
Me: (so you wanna micromanage. Got it...)
Me: ... Gotcha, yup... Writing that down.3 -
I feel guilty for using YouTube Vanced and being unable to support content creators.
Shouldn't there be a feature that allows you to toggle ads on certain channels you want to support?
I really want to support such folks who are creating valuable educational content but Google being the biggest piece of corporate shit, makes me angry when it comes to compensating the creators fairly when they make Billions off their hard work.
The world is a better place because of such teachers who spend time, energy, and efforts to create valuable and useful content for rest of the world.
Funnily, back in days when we had awesome stuff, the tech was shit to document all of it. Now when we have advanced and easily accessible tech, we have shitty TikToks.
Why can't the creators of good content get more visibility and why is the world so fucked?16 -
Learning [framework of your choice] wouldn’t be that hard if the internet were not full of (unnecessarily long) articles, tutorials and answers written with the only purpose of gaining visibility instead of informing the reader.
-
Caller: Hi, I work with Google. Can I talk to the decision maker of [your company]?
Me: I am. (Ho, my god, this is finally happening, I'm the chosen one!)
Caller: Would you like to improve your visibility on Google by ...
Me cutting short: Thanks but I'm not interested.
*Click*
To myself: Raaah, me too I work "with" Google!
(no my phone doesn't do *click*, it does *bee doooom*, but well)1 -
Have a Monday Cat, all. Don't forget to wake up this morning!
(Image was dark, so had to edit into visibility. Yes, this is one of my cats.)1 -
Fucking android framework. Sucks my huge ass balls. What is wrong with the people that wrote this?
You implement a fba and hide it when the recyclerview in the corresponding is scrolled down.
Then you change to API level 25 and they fucking decide it would be a good idea to refuse to send the onNestedScroll when the visibility for a fba is set to GONE which is itself not bad, but they also think setting the visibility for the fba when you call the hide() method to... yea you guessed it FUCKING GONE would be an amazing decision. Oh yea you smart ass nice decision I'm so glad you did it.5 -
Reposting this rant for more visibility. I do not like to repost, but this is really important, people's privacy is threatened.
https://devrant.com/rants/2436082/...9 -
One elementary school teacher of mine once said:
"In a football (soccer) game, the goalkeeper can be a very good player. He can make some incredible saves during the match. If he concedes a howler, people will remember him by that.
The forward can do everything wrong during the match. If he manages to score one goal, this is sufficient to justify why he was playing."
A team without a forward will have a harder time trying to win, but it is possible. A team without a goalkeeper will certainly lose. If you think into it, it's possible to conclude that the goalkeeper is more important than the forward. But football isn't rational; it isn't about fairness or importance. It is about emotions: forwards get all the visibility and fame because they get to do the "fun" part of the job.
Why people subject themselves to be goalkeepers then? Well, not every one is the same. In this game, if you, for any reason, aren't good playing with your foot, and still want to play, there is only one position you can take.
I think about this all the time because feel that in our work environment, managers are forwards and devs/scientists/technicians are goalkeepers.9 -
<rant>
I was once a pure server side developer. Then came full stack development. So in order to keep up with the competition, I had to brave through front-end development.
But goddamn javascript, make up your mind between functions, and “Objects”.
Also variable visibility. Goddamnit. I thought ES6 was widely supported. I was happy doing const and let bbut goddamn testing frameworks, grunt and shit. Can’t make up it’s mind to support it unitedly.
And lastly, IE. Goddamn it, why the fuck are you not supporting Promise by default. We’re fucking 2017. [insert slowpoke meme]
</rant>
One good thing though, I like the library vuejs.
Bad thing is, this is just the beginning of a much more upcoming headache.4 -
My employer found out that I used to do WordPress development. Now I have to setup and maintain the company blog, including custom theme and plugin development. And I don't get paid extra to do this shit.
On the plus side, it might give me better visibility within the office as the blog would be written by VP, directors and other senior folks. I'll have more interaction with them.
I'm curious to see how this goes.1 -
I've accidentally submited a wpf bool-to-visibility converter with inversed rules. On SVN, right to the trunk.
-
I always find reading small configuration files way more difficult than reading a big codebase.
I accept config files do really help in writing a better flexible code and separating the logic and settings but always offer a stiff learning curve.
And often, people make changes in config either unintentionally or with half knowledge which works in local but later blows up the entire system.
Wondering how config files can be presented in a way that the learning curve is minimal and the understandability of its impact is more visible.
I do really like annotations or decorators which provides a closer visibility between config and code. -
First job while in college... Was working for web dev team lamp set up before lamp was lamp (year was 2000).
Had deadline one week after summer vacation. Worked non stop a couple of days to get shit done and didn't make it. Got in a conflict with my manager in front of the team and I blew my steam off. Quit on the spot.
Lessons learned:
1. Don't be a fucking idiot when estimating work.
2. Be cool with other teammates, nobody cares about drama and nobody has to feel sorry for you.
3. Uhm, plan? Had entire fucking vacation to get work done. I was a fucking moron.
4. Burning out is stupid and unproductive.
5. Your manager can be as poor in management as you are. Your job is to try to make them better at it, as they have less visibility in the details.
Next job in grad school. Worked for a security company. Direct manager had the bright idea to make execs sign the change requests. WTF. Code was in Perl/php, a mess. Team rewrote back end DB access , taking over six months, or more, failing twice the deadline. After a final 48 hour burn out, we ship and get laid off the week after.
Lessons learned:
1. Don't work for dicks.
2. Don't be a dick yourself.
3. Don't work for dicks.
Third job was in silicon valley. It was a great company, and I stayed there for five years. -
Boss : make me a project with serverless and vue js
Me: you renounce to the SEO
Boss: no i need full visibility on search engines
Me: i will prerender it :'(
Rant :what i can do to save de seo of an vuejs application ? ... My html file have div id app ... End XD3 -
So I figure since I straight up don't care about the Ada community anymore, and my programming focus is languages and language tooling, I'd rant a bit about some stupid things the language did. Necessary disclaimer though, I still really like the language, I just take issue with defense of things that are straight up bad. Just admit at the time it was good, but in hindsight it wasn't. That's okay.
For the many of you unfamiliar, Ada is a high security / mission critical focused language designed in the 80's. So you'd expect it to be pretty damn resilient.
Inheritance is implemented through "tagged records" rather than contained in classes, but dispatching basically works as you'd expect. Only problem is, there's no sealing of these types. So you, always, have to design everything with the assumption that someone can inherit from your type and manipulate it. There's also limited accessibility modifiers and it's not granular, so if you inherit from the type you have access to _everything_ as if they were all protected/friend.
Switch/case statements are only checked that all valid values are handled. Read that carefully. All _valid_ values are handled. You don't need a "default" (what Ada calls "when others" ). Unchecked conversions, view overlays, deserialization, and more can introduce invalid values. The default case is meant to handle this, but Ada just goes "nah you're good bro, you handled everything you said would be passed to me".
Like I alluded to earlier, there's limited accessibility modifiers. It uses sections, which is fine, but not my preference. But it also only has three options and it's bizarre. One is publicly in the specification, just like "public" normally. One is in the "private" part of the specification, but this is actually just "protected/friend". And one is in the implementation, which is the actual" private". Now Ada doesn't use classes, so the accessibility blocks are in the package (namespace). So guess what? Everything in your type has exactly the same visibility! Better hope people don't modify things you wanted to keep hidden.
That brings me to another bad decision. There is no "read-only" protection. Granted this is only a compiler check and can be bypassed, but it still helps prevent a lot of errors. There is const and it works well, better than in most languages I feel. But if you want a field within a record to not be changeable? Yeah too bad.
And if you think properties could fix this? Yeah no. Transparent functions that do validation on superficial fields? Nah.
The community loves to praise the language for being highly resilient and "for serious engineers", but oh my god. These are awful decisions.
Now again there's a lot of reasons why I still like the language, but holy shit does it scare me when I see things like an auto maker switching over to it.
The leading Ada compiler is literally the buggiest compiler I've ever used in my life. The leading Ada IDE is literally the buggiest IDE I've ever used in my life. And they are written in Ada.
Side note: good resilient systems are a byproduct of knowledge, diligence, and discipline, not the tool you used. -
personal projects, of course, but let's count the only one that could actually be considered finished and released.
which was a local social network site. i was making and running it for about three years as a replacement for a site that its original admin took down without warning because he got fed up with the community. i loved the community and missed it, so that was my motivation to learn web stack (html, css, php, mysql, js).
first version was done and up in a week, single flat php file, no oop, just ifs. was about 5k lines long and was missing 90% of features, but i got it out and by word of mouth/mail is started gathering the community back.
right as i put it up, i learned about include directive, so i started re-coding it from scratch, and "this time properly", separated into one file per page.
that took about a month, got to about 10k lines of code, with about 30% of planned functionality.
i put it up, and then i learned that php can do objects, so i started another rewrite from scratch. two or three months later, about 15k lines of code, and 60% of the intended functionality.
i put it up, and learned about ajax (which was a pretty new thing since this was 2006), so i started another rewrite, this time not completely from scratch i think.
three months later, final length about 30k lines of code, and 120% of originally intended functionality (since i got some new features ideas along the way).
put it up, was very happy with it, and since i gathered quite a lot of user-generated data already through all of that time, i started seeing patterns, and started to think about some crazy stuff like auto-tagging posts based on their content (tags like positive, negative, angry, sad, family issues, health issues, etc), rewarding users based on auto-detection whether their comments stirred more (and good) discussion, or stifled it, tracking user's mental health and life situation (scale of great to horrible, something like that) based on the analysis of the texts of their posts...
... never got around to that though, missed two months hosting payments and in that time the admin of the original site put it back up, so i just told people to move back there.
awesome experience, though. worth every second.
to this day probably the project i'm most proud of (which is sad, i suppose) - the final version had its own builtin forum section with proper topics, reply threads, wysiwyg post editor, personal diaries where people could set per-post visibility (everyone, only logged in users, only my friends), mental health questionnaires that tracked user's results in time and showed them in a cool flash charts, questionnaire editor where users could make their own tests/quizzes, article section, like/dislike voting on everything, page-global ajax chat of all users that would stay open in bottom right corner, hangouts-style, private messages, even a "pointer" system where sending special commands to the chat aimed at a specific user would cause page elements to highlight on their client, meaning if someone asked "how do i do this thing on the page?", i could send that command and the button to the subpage would get highlighted, after they clicked it and the subpage loaded, the next step in the process would get highlighted, with a custom explanation text, etc...
dammit, now i got seriously nostalgic. it was an awesome piece of work, if i may say so. and i wasn't the only one thinking that, since showing the page off landed me my first two or three programming jobs, right out of highschool. 10 minutes of smalltalk, then they asked about my knowledge, i whipped up that site and gave a short walkthrough talking a bit about how the most interesting pieces were implemented, done, hired XD
those were good times, when I still felt like the programmer whiz kid =D
as i said, worth every second, every drop of sweat, every torn hair, several times over, even though "actual net financial profit" was around minus two hundred euro paid for those two or three years of hosting. -
Dear AWS, your Elasticsearch service is a bogus pile of shit-engorged horse fly larvae. Not only do you give no useful visibility into what's happening with the cluster (making diagnosis a sadistic guessing game), you lock down the fucking settings API, making it impossible to debug!! But your excellent support is on it! I wonder if I'll hear back from them this week with another inane suggestion like "increase the node count". Meanwhile the rest of my system is limping along, sometimes getting data where it's supposed to be while I keep fake-smiling and reassuring management and customers that "I'm working on it". If you're going to offer a service either make sure it works or get the fuck out of my way. I'll be moving my cluster back to EC2 and you can go do a back flip off a skyscraper. I need a drink2
-
Why the hell does my Samsung phone prevent me from uninstalling the Facebook app and instead offers me to disable it? WTF, NO, i want it freakin gone.
Bitch, Visibility: Hidden & Visibility: Gone are two different things.2 -
YouTube... for video creation.
Now I know I was a really amateurist video maker trying to make tutorials and videos about his coding creations in Mugen (you know, CNS state controllers and stuff,...), but this is the kind that's hard to get views from if you don't have a reach long enough to appear in search pages. I've had fun tagging my videos with plenties of tags just so they appear someday as a relevant result. EVEN in search pages for videos in the week, they barely appear and are sunk under videos of your Nth Mugen KOF clone with broken chars, Mugen ryona, Mugen hentai,... Speaking of which, did you know someone got to one of my videos from one of these?! How does YouTube's recommendation system work at this point?!
In the meantime (more like recently), I've been more interested in Ikemen, still kinda Mugen, still a DSL for a game engine, but still fascinating and there's material for tutorial making. But if I ever went back on video making, that won't be on YouTube. I'll just stick on Twitter and Discord if I were to share my content. At least, I got people following me there and a base visibility over there to start with. I could consider forums as well, why not, but YouTube is a no-go for me now.3 -
Ok, so currently in my Java course on Udemy we are going more in-depth into scope and visibility, and I'm currently doing the challenge for it.
So I'm doing it and the challenge is to have every single name of a variable or method be called 'x' (just to better understand scope and vis, he mentions how this is not a good practice AT ALL) with the exceptions of the classes and scanner var (but there is an optional challenge to also make them named x).
Now that I progressed into it, I noticed something. This challenge is literally making me make my code so DRY and outside-the-box-thinking that, what if, this could be a practice?
Not the naming everything in your code the same var name, but doing that at the start and then renaming the variables after coding. Because right now, I feel as though I am using SO MUCH less code than if I had the liberty of naming my classes, methods, and variables different things, it's actually kinda cool.
I'll attach my code from the challenge to this after by it really amazed me how well my code looked compared to my previous challenges and even personal projects!1 -
Anyone ever stay on a set of projects they knew were going to fail? I got pulled off of 3 major projects to help another team that was failing at their very high visibility project. I got that back on track, but then they needed to keep me on for stabilization work and to onboard some folks. Then they still kept me on and my projects all suffered. I was very vocal to management about my concerns. Finally, management recognized that my projects weren’t getting done so now I’m back on them. The thing is, now it’s probably too late and I’m pretty sure I’m going to fail to meet deadlines on all three (plus there’s scope creep of course). I want to just walk away from this hell hole, but I’ve made some promises to folks that helped me get the job that I wouldn’t be a job hopper (been here 4 years, and each year is worse than the last). I think I’m just going to do the best I can and see what happens - and try not to have a heart attack in the process.1
-
I think that "agile development" paradigm is really bad for programmers when it is directed by incapable people... I mean: "move fast and break things" is not a good philosophy, it is only an excuse for doing incomplete, buggy and "documentless" features that only helps the PM "visibility" (look at all the things that I did, I've been releasing 1 version per week, we have included 3 new features... we are burning 25 scrum points per capita per week)... we have to stand against this stupid way of doing things... Scrum makes that all the responsability is on us, as developers, and PMs can wash their hands freely...2
-
say you're thinking about starting a new project, you have the basics but not really expert in all the aspects required by the project and decided to open source it. how would you get the project more visibility which means more people involved ?4
-
One manager at the Client company tells us that unless we submit weekly timesheets we wont get paid.
We are not their employees, nor do we have an agreement with them for full time work.
" Whole thought process is to structure the engagement better ,so that we can implement better governance and provide better visibility."
Anyone understand what is being said above? Jargon.2 -
Top 12 C# Programming Tips & Tricks
Programming can be described as the process which leads a computing problem from its original formulation, to an executable computer program. This process involves activities such as developing understanding, analysis, generating algorithms, verification of essentials of algorithms - including their accuracy and resources utilization - and coding of algorithms in the proposed programming language. The source code can be written in one or more programming languages. The purpose of programming is to find a series of instructions that can automate solving of specific problems, or performing a particular task. Programming needs competence in various subjects including formal logic, understanding the application, and specialized algorithms.
1. Write Unit Test for Non-Public Methods
Many developers do not write unit test methods for non-public assemblies. This is because they are invisible to the test project. C# enables one to enhance visibility between the assembly internals and other assemblies. The trick is to include //Make the internals visible to the test assembly [assembly: InternalsVisibleTo("MyTestAssembly")] in the AssemblyInfo.cs file.
2. Tuples
Many developers build a POCO class in order to return multiple values from a method. Tuples are initiated in .NET Framework 4.0.
3. Do not bother with Temporary Collections, Use Yield instead
A temporary list that holds salvaged and returned items may be created when developers want to pick items from a collection.
In order to prevent the temporary collection from being used, developers can use yield. Yield gives out results according to the result set enumeration.
Developers also have the option of using LINQ.
4. Making a retirement announcement
Developers who own re-distributable components and probably want to detract a method in the near future, can embellish it with the outdated feature to connect it with the clients
[Obsolete("This method will be deprecated soon. You could use XYZ alternatively.")]
Upon compilation, a client gets a warning upon with the message. To fail a client build that is using the detracted method, pass the additional Boolean parameter as True.
[Obsolete("This method is deprecated. You could use XYZ alternatively.", true)]
5. Deferred Execution While Writing LINQ Queries
When a LINQ query is written in .NET, it can only perform the query when the LINQ result is approached. The occurrence of LINQ is known as deferred execution. Developers should understand that in every result set approach, the query gets executed over and over. In order to prevent a repetition of the execution, change the LINQ result to List after execution. Below is an example
public void MyComponentLegacyMethod(List<int> masterCollection)
6. Explicit keyword conversions for business entities
Utilize the explicit keyword to describe the alteration of one business entity to another. The alteration method is conjured once the alteration is applied in code
7. Absorbing the Exact Stack Trace
In the catch block of a C# program, if an exception is thrown as shown below and probably a fault has occurred in the method ConnectDatabase, the thrown exception stack trace only indicates the fault has happened in the method RunDataOperation
8. Enum Flags Attribute
Using flags attribute to decorate the enum in C# enables it as bit fields. This enables developers to collect the enum values. One can use the following C# code.
he output for this code will be “BlackMamba, CottonMouth, Wiper”. When the flags attribute is removed, the output will remain 14.
9. Implementing the Base Type for a Generic Type
When developers want to enforce the generic type provided in a generic class such that it will be able to inherit from a particular interface
10. Using Property as IEnumerable doesn’t make it Read-only
When an IEnumerable property gets exposed in a created class
This code modifies the list and gives it a new name. In order to avoid this, add AsReadOnly as opposed to AsEnumerable.
11. Data Type Conversion
More often than not, developers have to alter data types for different reasons. For example, converting a set value decimal variable to an int or Integer
Source: https://freelancer.com/community/...2 -
My first writeup on medium.
hope it helps you to build npm ready angular library components
“How to built npm ready component library with Angular” https://medium.com/@mohanramphp/...
Please give claps for visibility1 -
"Urban public space is a stage for viewing the field of graphic design in its diversity. A mix of voices, from advertising to activism, compete for visibility." - Ellen Lupton
-
One thing I love about agile and scum is that it easily points out who or what isn't carrying it's weight. The visibility and transparency is awesome, but of course this only applies to teams that implement it correctly!